Merchants

Prerequisites

• Rhyza/ILP
• Webhooks
  • card authorization requested - Talks directly to the Issuer API, not the FSP’s integration server, not the merchant. For card-enabled integrations only, so Rhyza doc won’t have much about this webhook. The details should be here in the Offline Payments docs.
  • grant revoked - This will be a generic webhook in Rhyza for all grants, not just card-related ones. The details should go in the Rhyza docs. In the card docs, we can point this webhook out to the FSP in this same page where we describe the whole flow.
• Open Payments
• HSM adapter proto implementation
  • https://github.com/interledger/hsm-adapter
  • https://buf.build/interledger/hsm-adapter
  • https://buf.build/interledger/hsm-adapter/docs/main%3Ainterledger.hsm.adapter.merchant.v1
• “gRPC: schemas define functions and how they look, some aren’t HSM-related. Have function, need to document objects to be implemented.”

FSP vs Merchant API responsibilities

• FSP responsible for comms w/ HSM, baseline account-servicing role (providing accounts/wallet addresses; authorizing ILP card transactions [receives EMV transaction data, validates cryptogram via HSM, triggers ILP payment in Rhyza]), provide POS terminal (terminal manufacturer has already integrated the device with OP/ILP)
• API to act as OP client

Wallet address for the actual merchant must be bound to the terminal

Practical integration guides, example uses cases, end-to-end flows. Include sample requests, sequences, and recommended practices. Key workflows such as merchant onboarding, terminal provisioning, and lifecycle management.