Setup for Single-Use Virtual Card

This guide describes your responsibilities to set up a single-use virtual card, part of Galileo’s Buy Now, Pay Later product.

Set up a credit program

Single-use virtual cards are treated as a credit product at Galileo. When you set up a credit product, you are adding a new program and a new BIN. You will need approval for the new BIN from both your bank partner and Mastercard. You can ask your Galileo representative to help you with your conversation with the network to avoid misunderstandings. Refer to the Setup Galileo Secured Credit for details on credit at Galileo.

Obtain a bank partner

Before you can use Galileo’s Buy Now Pay Later service, you must acquire a bank partner to sponsor your program. Your issuing bank may not support credit products. If this is the case, you will need to use a separate sponsor bank.

PCI compliance

You may need to be PCI compliant if you plan to display virtual card information, like the PAN, to customers in the application and/or in their mobile wallet.

Merchant credits and refunds

You are responsible for determining how to handle merchant credits and refunds. You may decide to pay merchant credits and refunds to the cardholder, apply them to the next installment loan, or some other solution.


You are responsible for setting up your own internal process to handle disputes. You may decide to integrate with Galileo’s disputes partner.

Galileo setup

These internal parameters are set at Galileo according to your use case.

SUVCProductRequired to specify a single-use virtual card program for BNPL.
SUVCTProductThe dollar amount threshold above which will be considered a consumer initiated transaction on a single use virtual card. Consumer initiated transactions below this threshold will be considered a preauthorization hold that will be followed by a second, larger transaction.
SUMTAProductOptional. The dollar amount threshold below which a transaction will be declined. Defaults to $50.
SUVCMProductOptional. Configures the transaction-matching method based on value. Values are:
  • TERMINAL — Requires that the terminal ID of any subsequent transaction matches the terminal_id (DE41) of the first transaction on file or the subsequent transaction will be declined.
  • MERCHANT — Requires that the merchant ID of any subsequent transaction matches the merchant_id (DE42) of the first transaction on file or the subsequent transaction will be declined.
  • TERMINAL, MERCHANT — Recommended. Requires both the terminal ID and merchant ID of any subsequent transaction to match the ones stored on file or the subsequent transaction will be declined.
  • NONE — No merchant data is checked on subsequent transactions. Subsequent transactions will be approved, assuming there are sufficient funds.