insimbi

Docs · Agent protocols

Machine Payments Protocol (MPP)

Challenge, Credential and Receipt over HTTP 402, on the rail your rules choose.

Mm Fi Sc

Designed. Protocol support is designed. The flow follows the protocol's published specification, with insimbi on the merchant side. Every check and every settlement is written to the record.

Machine Payments Protocol (MPP) Designed. MPP's Challenge, Credential and Receipt over HTTP 402.
Machine Payments Protocol (MPP)Sequence diagram with 4 lanes (Client (agent), Merchant API, insimbi, Payment method (rail or regulated partner)) and 10 numbered steps. The same steps are listed in text below the diagram.Client(agent)Merchant APIinsimbiPayment method(rail or regulated partner)1Request a resource2Price it and pick thepayment methods yourrules allow3402 Payment RequiredwithWWW-Authenticate:Payment (theChallenge)4Pay with the method the Challenge names5Retry withAuthorization:Payment (theCredential)6Verify the Credentialis bound to theoriginal Challenge7Confirm the payment8Confirmed9Write the ledger entry and fee lines tothe record10200 with aPayment-Receiptheader

Steps in text

  1. Client (agent) to Merchant API: Request a resource
  2. Merchant API to insimbi: Price it and pick the payment methods your rules allow
  3. Merchant API to Client (agent): 402 Payment Required with WWW-Authenticate: Payment (the Challenge)
  4. Client (agent) to Payment method (rail or regulated partner): Pay with the method the Challenge names
  5. Client (agent) to Merchant API: Retry with Authorization: Payment (the Credential)
  6. Merchant API to insimbi: Verify the Credential is bound to the original Challenge
  7. insimbi to Payment method (rail or regulated partner): Confirm the payment
  8. Payment method (rail or regulated partner) to insimbi: Confirmed
  9. insimbi: Write the ledger entry and fee lines to the record
  10. Merchant API to Client (agent): 200 with a Payment-Receipt header

Request access

insimbi is in early access with design partners.