Program ID

Description of the Bond Program UUID and its relationship to the relevant accounts.

The program_id UUID represents a partnership between you and a bank. You may partner with multiple banks to offer a range of financial products to customers where each of these combinations is represented within the Bond platform by a unique program_id.

The following chart illustrates the processes that require the program_id to be passed as a body parameter in a request.


Bond provides infrastructure for clients to offer banking services to their customers. Within the Bond platform, the program_id represents the financial institution and configuration for an account object.

If your company has partnerships with multiple banks, you can allow your customers to have cards from more than one card program. Both the customer_id and the program_id are required parameters for the API request to POST /accounts.

Card configurations

A card can be virtual, physical, or dual. This configuration is determined and included with the program_id that is provided by Bond based on your requirements.


A virtual card can be used in exactly the same way as a physical card, with the exception of POS terminals. As soon as you create this card, your customer can use it for purchases.


A physical card is issued as inactive and is automatically shipped to the customer on issue. You need to activate it before it can be used.


A dual card configuration results in both a virtual and a physical card being issued at the same time, each with the same card number but different CVV numbers and expiration dates.

When you create a dual card, its virtual card is active but the physical card is inactive until you activate it.

Once you activate the physical card, the card number, expiry, and CVV combination of the virtual card will no longer be valid. However, if the card has been added to a mobile wallet, the tokenized card information in the mobile wallet card will be updated to match the physical card details automatically without user intervention, and the BondCards SDK will automatically start showing the card information of the physical card. The cardholder experience will be that once they activate their physical card in your app, they’ll be able to continue using their card in their mobile wallet as expected.

In physical and dual card configurations, the physical card is shipped to the customer as soon as you create the card.

Financial regulations

Financial regulations compel banks to ensure that their customers' personal details have been verified, so the Bond KYC process must be executed for every program_id where a customer has an account. Both the customer_id and the program_id are required parameters for KYC verification requests because the combination indicates that Bond is executing verification of a particular customer on behalf of a particular bank.