Issuers

Prerequisites

• Rhyza/ILP
• Webhooks
  • card authorization requested - Talks directly to the Issuer API, not the FSP’s integration server. 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.issuer.v1
• “gRPC: schemas define functions and how they look, some aren’t HSM-related. Have function, need to document objects to be implemented.”
• As an Issuer you must find a manufacturer in your region: here’s how to order cards, here’s the data that needs to be sent, etc. Card issuance is specific to provider, provide doc for tooling on how to extract info

FSP vs Issuer API responsibilities

• FSP responsible for comms w/ HSM, delivering personalization data to card manufacturer, baseline account-servicing role (providing accounts/wallet addresses, moving funds/creating outgoing payments/funding [depositing liquidity]/approval/settlement)

Issuer Rhyza (auth + backend) —> Issuer API —> Issuer HSM Adapter —> Issuer HSM —> Issuer FSP

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

FSP/issuer binds customer wallet address to the card, FSP/issuer sends customer plastic