Nerdla productLaunching soon

Building Permint's Access Commerce Platform

Engineering a platform where businesses sell limited-capacity passes and validate them by QR code — with exactly-once fulfillment and passes that can't be forged.

Reserve → pay → fulfil exactly once → redeem onceArchitecture
  1. Entry point: CustomerOffer page or embed
  2. Safeguard: ReservationRow lock · server price
  3. External system: Stripe CheckoutMerchant’s connected account
  4. Safeguard: Signed webhookEvent ledger · one transaction
  5. Core system: Signed passQR · email outbox
  6. State / data: Atomic redemptionExactly once · merchant-scoped

Fulfillment happens only from verified webhooks; passes are signed and redeemed atomically.

Permint organizer dashboard with live offerings, purchases, revenue and passes to redeem (demo data)
A Permint access pass with QR code on a phone (demo data)

Challenge

Studios, organizers and service businesses sell limited capacity — classes, events, multi-visit passes — and want to be paid directly. Every pass has to be impossible to forge and redeemable exactly once, at the door, on a phone, even when many people buy the last spots at the same moment.

Approach

  • Merchants get paid directly. Stripe Connect charges go to each merchant's own account, and an offering can't be published until that account can accept payments.
  • Reserve before you charge. Inventory is reserved under row locks before checkout begins, the server sets the price, and the checkout session expires with the reservation.
  • Fulfil only from verified webhooks. Signed webhooks are processed exactly once through an event ledger in a single transaction, and a reconciliation job recovers anything missed.
  • Passes are cryptographically signed. Each pass is a signed entitlement; redemption is atomic, idempotent and scoped to the merchant. Refunds revoke passes, and disputes suspend them until resolved.

Implementation

  • Checkout, purchase-lifecycle and reconciliation services, plus a transactional email outbox with retries.
  • Strict per-merchant data isolation, CSRF/CSP/HSTS protections, rate limits and production secret enforcement.
  • A dependency-free embeddable widget so merchants can sell from their own websites.
  • A SwiftUI iOS app for organizers: dashboard, offerings, sales and QR validation that verifies pass signatures.

Outcome

In documented concurrency tests, twelve simultaneous checkouts against a capacity of three produced exactly three sales, ten simultaneous redemptions of one pass produced exactly one, and duplicate webhooks fulfilled exactly once. Permint is preparing for public launch.

Technical perspective

Almost every hard problem here is about concurrency and retries: reservations, webhook duplication and ordering, simultaneous redemptions. The same guarantees then have to hold across the web dashboard, the embedded widget and the mobile app.

Facing something similar?

Tell us about your systems and what needs to change. We’ll tell you honestly whether we can help.

Start a Project

More work

Financial services

Engineering Reliable Payment & Fulfillment Workflows

A regional consumer financial-services platform

  1. Cardholder
  2. 3D Secure 2
  3. Server-to-server response
  4. Verification
  5. Atomic state change
  6. Fulfillment guard

Replayed, forged and concurrent completions cannot produce a payment or a fulfillment, and gift card issuance can be frozen without stopping checkout.

Read the case study

Distribution

Connecting Legacy Accounting to Modern Commerce

A regional distributor of truck and industrial parts

  1. QuickBooks Desktop
  2. Web Connector
  3. Integration service
  4. AI categorizer
  5. Catalog + vectors
  6. Storefront

Thousands of accounting-only items became a categorized, typo-tolerant storefront, and web orders now reach QuickBooks Desktop without re-keying.

Read the case study

Commerce

Adding a Multi-Vendor Marketplace to an Existing Platform

A regional consumer financial-services platform

  1. Buyers & sellers
  2. Platform
  3. Stock-sync queue
  4. Sync worker
  5. Commerce engine

Sellers can be onboarded, moderated and paid inside the existing platform, and stock reconciles even when the commerce engine is briefly unavailable.

Read the case study