The payment path

The payment path A sequence diagram generated by Archify. commits to buy POST /v1/payment-intents (order inline) 201 · pi_… · CREATED POST /v1/payment-intents/pi_…/confirm Gate decides · router picks a connection · trace stored 200 · PROCESSING · next_action act on next_action (redirect · client confirm · QR) dispatch job (Postgres queue) call the provider with the tenant's key signed provider webhook inbox job payment.intent.succeeded.v1 (Ed25519-signed) POST /v1/fulfillment-events when you deliver Create and confirm Dispatch and outcome Deliver Buyer · browser · Sequence participant Buyer browser Your server · checkout · Sequence participant Your server checkout Pehmen API · the authority · Sequence participant Pehmen API the authority Pehmen workers · connectors · core · Sequence participant Pehmen workers connectors · core Provider · Stripe · HitPay · Airwallex · Sequence participant Provider Stripe · HitPay · Airwallex Legend request return security async trace default message

Your side

  • • Create when the buyer commits, confirm, act on next_action
  • • Learn the outcome from a signed webhook, never a polling loop
  • • Send fulfilment evidence when you actually deliver

Pehmen's side

  • • One transaction records the decision, the trace, the job and the outbox event
  • • A worker calls the provider with your own credential
  • • The provider's webhook advances the payment; you get a signed event