Card Bureau and Fulfilment

CLOWD9 supports Virtual and Physical Cards in addition to other payment devices such as wearables (rings, bracelets etc).

All payment products are created on the CLOWD9 platform via APIs such as Create Card and Onboard Card. Previously created Virtual Cards can be converted to Physical Cards (either same day or at a later stage).

For the production and preparation of Physical Cards CLOWD9 has interfaces with several Card Personalization Bureau:

These bureaus handle the processes necessary to customize cards for your card programme.

Should there be a requirement to integrate with a Card Personalization Bureau not in the list above, then this can be accommodated as part of the implementation of your project.

The Card Personalization Bureau supports:

  • Data Encoding: Embedding customer-specific information on the card's magnetic stripe or chip, such as account numbers and encryption keys.
    Card Printing:
  • Printing/Embossing: personalized details such as the cardholder's name, card number, expiration date, and sometimes even photos or logos on the card.
  • Secure Chip Initialization: Personalizing the EMV chip by encoding it with unique keys and data for secure transactions.
  • PIN Generation and Delivery: Where your programme requires a pronted PN Mailer, the Card Bureau will prnt them and securely distribute them to cardholders.
  • Packaging and Distribution: Packaging the personalized cards, including user manuals or activation instructions, and dispatching them to card holders or distribution points.
  • Compliance and Security: Adhering to strict security standards set by regulatory bodies like PCI DSS (Payment Card Industry Data Security Standard) to protect sensitive data and prevent fraud.

Following successful onboarding requests, CLOWD9 will generate a production file in line with your configuration set up. The card file will contain all records created since the last production file was generated (unless this is the first production file).

The Card Card Personalization Bureau may provide CLOWD9 with response files and dispatch files subject to the agreements and services provided:

Response file: This will confirm the file name, date received and the number of records received from CLOWD9. This file may or not contain rejected records

Rejection file: This may be a separate file to the response file depending on the CM. The file will contain the number of records and provided details for any which have not been able to be produced

Dispatch file: This file will contain details of how the card was dispatched and where couriers / special delivery has been used, provide information that can be passed onto the end customer to track their card. Where a card has been sent by 1st or 2nd class post, the delivery of the card cannot be tracked


What’s Next