Overview

The Canopy Galileo Integration allows Canopy to automatically wrap calls to the Galileo API when you use Canopy as normal.

When a borrower is onboarded; Canopy will automatically create their corresponding card in Galileo
When the borrower uses their card, Canopy will react and record the authorization request as a line item in its ledger
When transaction states change in Galileo, Canopy’s ledger will update those transaction states in sync.
When fees, interest or non-card related charges/payments are recorded in Canopy, Galileo’s balance will be automatically updated such that the available balance checks performed within Galileo are consistent with a borrower’s true available spend.

When onboarding borrowers, you can specify a few extra details (card art, shipping method) related to card creation in Galileo, or leave them default for the basic experience

You do not need to write any code to call Create Charge or update charge line items in Canopy; we will handle this by subscribing to Galileo’s events
Whenever an authorization request is processed by Canopy, our system creates the new line item and sets the Line Item Status as AUTHORIZED.
(To better understand line item statuses in Canopy, check out this document )
Updates to this authorization request are sent by Galileo and processed by Canopy, mapping the various transaction states in Galileo to internal Canopy line item statuses

Canopy automatically updates the transaction amount based on whatever was received from Galileo during settlement.
Canopy is also able to perform a CHARGE_REVERSAL whenever Galileo suggests the authorization needs to be reversed.
Canopy also allows Galileo to be used as a payment processor, involving a single additional API call performed to Canopy (configure payment processor) to enable features such as ACH and Auto-pay
Canopy automatically synchronizes account status (Active, Delinquency, Bankruptcy, etc.) with Galileo, such that changes are reflected and consistent in both systems.

Technical:

There is only one easy step to getting the issuer-processor integration set up:

To get started, retrieve your Galileo Keys from your Galileo Relationship Manager and store them in Canopy by passing a galileo_config to the PUT /organizations/issuer_processors endpoint in Canopy. Canopy is now equipped to communicate with Galileo on your behalf.

That’s it! - Your Galileo Integration is now running. You can use Canopy as normal.

Here’s what to expect now that your integration is set up:

In all Create Account API requests to Canopy, you should now expect to see an issuer_processor details and cards section in the response
In the Get requests to all accounts, you should now see issuer_processor details and card details in the response

In all line items created by the Galileo integration, you should see issuer_processor_details included in the Get request that includes transaction data.

You should see the accounts created via Canopy with their corresponding payment_reference_number (PRN)
Events will flow for these accounts resulting in transactions in Canopy or balance adjustments in Galileo