Multi-app Cards

Offer a physical card that works as both Credit and Prepaid.

Scope:

For now, this product is only available for Visa 🇧🇷Brazil.

Introduction:

Multi-app is a solution that allows the combination of BINs on a single physical card, providing flexibility for you and your customers.

Key features of our multi-app cards:

• We emboss two cards onto a single plastic.
• It only applies to physical cards.
• Cards can be named (personalized) or innominated.
• Multi-app batches of unnamed cards are limited to 500 plastics (1000 logical cards).
• The allowed BIN combination is “Credit + Prepaid” in any order.
• You can define whether multi-app cards will have synchronized or independent statuses.
• Multi-app cards share the same expiration date.

Primary BIN

When configuring the BIN, you’ll be able to define which one is the primary. This means that if the POS does not explicitly indicate which BIN type to use (Credit, Debit, or Prepaid), the primary BIN will be used by default. It is also the one visually personalized on the card.

How it works:

1. Your customer approaches the checkout.
2. The cashier asks which type of card they want to use (Credit or Prepaid?).
3. Your customer responds or selects it on the POS.
4. The POS reads the appropriate BIN information from the card.
5. The transaction proceeds as usual.

Experience in the Dashboard:

You can always identify if a user has a multi-app card by the label shown on the card image:

Requesting a batch shipment of unnamed multi-app cards

1. Go to the “Batch Shipments” section.
2. Click on “Create Batch”.
3. Select the Affinity Group for the Primary BIN.
4. Then, select the Affinity Group for the Secondary BIN.
5. Enter the number of cards to issue. If you enter 500, 1000 logical cards will be created (500 for each BIN), embossed on 500 plastics.

Implementation:

Below are the APIs involved in implementing multi-app functionality:

Basic Issuing endpoints with multi-app specific behaviors:

• Single shipments (only applies to unnamed cards): you must include the two affinity groups involved.
• Card query: if the card is multi-app, the response will include specific multi-app attributes.

Multi-app-specific endpoints:

• Create multi-app: used to issue named multi-app cards, requiring the two involved Affinity Groups.
• Create MultiCard batch: used to create batches, also requiring the two Affinity Groups and the number of cards.