insimbi

Docs · Agent protocols

Agent Payments Protocol (AP2)

A person present, an agent shopping, insimbi as the merchant's payment processor.

Mm Fi

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.

Agent Payments Protocol (AP2) Designed. AP2 human-present journey, with insimbi as the merchant's payment processor.
Agent Payments Protocol (AP2)Sequence diagram with 5 lanes (User (trusted surface), Shopping agent, Merchant, insimbi, Credentials provider and network) and 13 numbered steps. The same steps are listed in text below the diagram.User(trusted surface)Shopping agentMerchantinsimbiCredentials providerand network1Give the agent ashopping task2Build a cart3Cart, signed by themerchant4Ask for an applicable payment method5Show the cart andpayment method6Approve: a signedCheckout Mandate7Submit the order withthe Checkout Mandateand Payment Mandate8Authorize the payment9Check the mandates against your rules,choose the rail10Authorization, withagent presencesignals11Approved (or achallenge such as 3-DSecure)12Result, written tothe record13Order confirmed

Steps in text

  1. User (trusted surface) to Shopping agent: Give the agent a shopping task
  2. Shopping agent to Merchant: Build a cart
  3. Merchant to Shopping agent: Cart, signed by the merchant
  4. Shopping agent to Credentials provider and network: Ask for an applicable payment method
  5. Shopping agent to User (trusted surface): Show the cart and payment method
  6. User (trusted surface) to Shopping agent: Approve: a signed Checkout Mandate
  7. Shopping agent to Merchant: Submit the order with the Checkout Mandate and Payment Mandate
  8. Merchant to insimbi: Authorize the payment
  9. insimbi: Check the mandates against your rules, choose the rail
  10. insimbi to Credentials provider and network: Authorization, with agent presence signals
  11. Credentials provider and network to insimbi: Approved (or a challenge such as 3-D Secure)
  12. insimbi to Merchant: Result, written to the record
  13. Merchant to User (trusted surface): Order confirmed

Request access

insimbi is in early access with design partners.