Buy Now, Pay Later: Pre-Purchase Workflows

The page describes the endpoints and workflows creating and managing pre-purchase Galileo Buy Now, Pay Later.

Endpoints related to Buy Now, Pay Later: Pre-Purchase

This table lists the actions for creating and managing Galileo Buy Now, Pay Later, and related Loan API and Program API endpoints.

How it works

This section contains workflows that illustrate the processes for creating and managing a Buy Now, Pay Later service.

Virtual card creation and initial purchase

1. Your customer in the Galileo system requests to make a purchase using your BNPL service.
2. You perform the underwriting to determine the credit limit you want to extend to the customer.
3. You present the BNPL offer to your customer.
4. Customer accepts the offer and terms of the loan.
5. You use the Create Single-Use Virtual Card endpoint to create a single-use virtual card and the associated credit account.
6. You call Create Provisioning Request endpoint to push provision the virtual card into the customer’s mobile wallet. For further information on push provisioning, see Push provisioning in the Setup for Mobile Wallets guide.
7. The customer makes a purchase with the provisioned virtual card at a retail or online merchant.
8. The card network sends an authorization request.
9. Galileo verifies that this is first purchase on this card and applies any MCC rules configured for the issuer’s program.
10. Galileo notifies you of the purchase by sending the BAUT: auth event.
11. The provisioned virtual card is removed from the customer’s mobile wallet.

Loan creation and first payment

1. Galileo receives the settlement data from Mastercard and updates transactions on the credit account from pending to posted.
2. Galileo notifies you of settled transactions via the SETL: setl event.
3. You create the loan based on the full settlement amount, which is the balance of the credit account, by using the following calls:
   1. For consumers - Send Create Loan endpoint
   2. For businesses - Send Create SMB Loan endpoint
4. You receive notification that the loan has been created loan_creation_event . If the loan fails to be created, you assess the errors provided in the loan_creation_failure_event .
5. Upon receiving the Create Loan response, you call Create Loan Payment endpoint to make the first payment on the loan.
6. Galileo sends the Create Loan Payment response in confirmation of a successful payment.

Galileo authorizes or declines further transactions based on Mastercard Installments program guidance for card tokens. Any merchant initiated transactions will be approved as long as the card is active. Galileo notifies you of the approved or declined transactions via the Transactions Events API.

Subsequent payments and loan charge off

As a reminder, you are responsible for recording the installment loans issued and paying off the outstanding credit balance.

1. You use the Daily Loan Status and Daily Transaction file to notify the customer the next payment is due.
2. The customer receives the notification and initiates the payment.
3. You use the Create Loan Payment endpoint to execute on the next payment.
4. Repeat steps 1–3 for the remaining installments.
5. On the last payment, you receive notification from Galileo that the loan is paid off (loan_payoff_event).
6. You notify the customer that the loan is paid off and closed.

60 days after settlements, if there are no disputes, you are responsible for closing the single-use virtual card account using the Modify Status endpoint.