Issuer Processor

Card-based programs in Canopy require a third party issuer processor to power card issuing and management for accounts.


Card-based programs using Canopy will need a mechanism for issuing cards to borrowers. Whenever those cards are used by borrowers, the issuer-processor needs to be able to authorize the transactions, and Canopy needs to know about the transactions in its ledger.

This entire process can be set up with no-code and just a few configurations using one of our issuer-processor integrations. This is our recommended approach.

Alternatively, the steps to build your own custom issuer-processor integration with Canopy are not overly complex; this is a better option for partners who may use unsupported issuer-processors or need some other level of control over the issuance-processing pipeline.

No-Code Integration (Recommended)

Setting up the Issuer Processor for your organization

Canopy currently supports a no-code setup when using Lithic or Galileo as your Issuer Processors. To use one of these processors, simply configuring your Canopy API keys through our Issuer Processor endpoint.

Setting up each borrower to use the integration

  • Whenever a borrower is onboarded, in the same API call simply pass some additional data about the card you want to issue them. Parameters to pass vary slightly depending on which integration you are using, but are all very standard.
  • Optionally, you may issue additional cards for an existing customer
  • Optionally, you may update customer cards -- for instance, if they lose their card, and you need to invalidate it.

All transaction activity pipes into Canopy automatically

  • Whenever a borrower uses their card, Canopy automatically knows about it and handles the charge.
  • Canopy handles authorization, declining unauthorized transactions.
  • Canopy processes transactions as they are settled.

Custom Integration

Alternatively, you may replicate the flow of our issuer-processor integrations for your own system.

  • You can issue cards outside of Canopy completely.
  • Whenever a borrower makes a transaction, your system can either maintain a shadow ledger for authorizations or check the borrower's available credit in Canopy before responding to authorization requests.
  • You should let Canopy know of Authorizations via our Create Charge endpoint, and later update the status of those charges via our Update Line Item endpoint once the transactions settle.

Related Articles