Card Management

A Card in our system represents the cardholder’s physical or virtual card. These cards utilize funds provided by the linked Balance Account. It’s important to note that multiple Card resources can be created per Balance Account.

During the onboarding process for new clients, the organization must first onboard and upload information about its beneficial owner and control person, as described in the previous sections. This prerequisite ensures that necessary background checks and verifications are completed before cardholders, cards, and associated balance accounts can be created.

This structured approach helps maintain regulatory compliance and ensures that all necessary parties and accounts are properly established before card issuance. If you have any questions or need assistance with card management processes, our team is available to provide guidance and support. We’re committed to facilitating a smooth and compliant card management experience for your organization.

For detailed technical information, please refer to the “Create card” API documentation.

Cards are issued based on the associated Legal Entity of the cardholder applicant. The residential address country of the cardholder applicant will determine the available card products. The legal entity’s official name will determine the card name displayed on the card.

These cards can be physical and/or virtual. Virtual cards have the option to be converted to physical cards at a later stage through the Convert Cards process.

Upon creation, newly issued cards will have a status of NEW, which will automatically transition to ORDERED. This process triggers two events:

If a manual activation flow is configured, the card must be activated (through the Activate Cards process) before it can be used for payments.

This structured approach ensures that cards are issued accurately and in alignment with regulatory requirements, providing a frictionless experience for cardholders. Should you have any questions or need assistance with card creation processes, our team is available to provide support and guidance. We’re dedicated to facilitating a smooth and efficient card issuance process for your organization.

For detailed technical information, please refer to the “Activate a card” API documentation.

There are several available activation flows for cards:

Please consult with your implementation manager to configure the appropriate card activation flow based on your specific requirements.

Upon activation, a card.updated event is triggered to indicate the change in status.

This flexibility in activation flows allows you to tailor the card activation process to best suit your organization’s needs and security preferences. If you have any questions or need assistance with configuring the card activation flow, our team is available to provide guidance and support. We’re dedicated to ensuring a smooth and secure card activation process for your organization.

For detailed technical information, please refer to the below documentation:

Cards can be blocked either by us or by you, the client. Once blocked, a card can be subsequently unblocked.

We reserve the right to block cards according to our Terms and Conditions, which may include instances of fraud attempts or other suspicious activities.

You, as the client, have the authority to block cards based on your Terms and Conditions or in response to cardholder requests.

When a card is blocked, a card.updated event is triggered to reflect the change in status.

This capability to block and unblock cards provides flexibility in managing card security and addressing potential risks. If you have any questions or need assistance with blocking or unblocking cards, our team is available to provide guidance and support. We’re committed to ensuring the security and integrity of your card management processes.

For detailed technical information, please refer to the “Cancel a card” API documentation.

Cards can be canceled either by us or by you, the client. Once canceled, a card cannot be activated again.

We reserve the right to cancel cards according to our Terms and Conditions, which may include situations such as cardholder requests, loss, or theft.

You, as the client, also have the authority to cancel cards based on your Terms and Conditions or in response to cardholder requests, such as instances of lost or stolen cards.

Upon cancellation, a card can no longer be used or activated. This action ensures the security of the cardholder’s account and prevents unauthorized use of the card.

If you have any questions or need assistance with canceling cards, our team is available to provide guidance and support. We’re committed to ensuring the security and integrity of your card management processes.

For detailed technical information, please refer to the “Update the cards authentication details” API documentation.

When changing authentication details, it’s important to note that updating the authentication phone number will also update the phone number used for 3DS (3-D Secure) authentication.

This ensures that the authentication process remains accurate and up-to-date, providing enhanced security for card transactions. If you have any questions or need assistance with changing authentication details, our team is available to provide support and guidance. We’re committed to ensuring the security and integrity of your authentication processes.

For detailed technical information, please refer to the “Update the cards features” API documentation.

The following card features are implemented:

These features provide flexibility in controlling card usage and enhancing security based on specific requirements and preferences. If you have any questions or need assistance with configuring card features, our team is available to provide support and guidance. We’re committed to ensuring the security and integrity of your card management processes.

Limits are configured based on BIN (Bank Identification Number) requirements and your specific needs. If you require custom limits for your cards by default, please consult your implementation manager.

Limit configurations can be divided using the following criteria:

For each limit configuration, the following limits can be defined:

Both normal limits and rolling limits can be configured with the following parameters:

Rolling limits also define the window size. For example, a daily rolling limit with a window size of four will consider the sum of transactions over the last four days, including the present day.

This comprehensive approach to limit configuration allows for precise control over card usage and spending, ensuring compliance with regulatory requirements and alignment with your organization’s specific needs. If you have any questions or require assistance with configuring card limits, our team is available to provide support and guidance. We’re committed to ensuring the security and integrity of your card management processes.

For detailed technical information, please refer to the “Update the cards type” API documentation.

Virtual cards can be converted to physical cards. This conversion process is facilitated using the request object, as physical cards require a mandatory delivery address and support the usage of a PIN.

Upon card conversion, a new Card resource is created. The virtual and physical cards will share the same card number and have different CVV and expiry dates if the conversion occurs in a different month than the virtual card creation. If the conversion occurs in the same month, the CVV and expiry dates will be identical.

Both the virtual and physical cards will be active and usable by the cardholder with their unique details (CVV and expiry date). Once the physical card is activated, the virtual card will be automatically canceled.

It’s important to note the following:

The conversion process triggers the following events:

This conversion functionality provides flexibility for cardholders to transition from virtual to physical cards as needed, while also ensuring seamless management of card resources. If you have any questions or require assistance with card conversion processes, our team is available to provide support and guidance. We’re committed to ensuring a smooth and efficient card management experience for your organization.

We do not host card images ourselves. Please consult your implementation manager regarding the image file to use and host on your system.

To display the card image along with the card data we provide, an endpoint is available for fetching the image. This fetch operation should be initiated directly from the cardholder’s device. The data must not be routed through your system unless you are PCI DSS certified.

The fetch operation is unauthenticated and must be initiated from a trusted environment.

Our recommended flow is as follows:

It’s important to note that card visualizations cannot be created for physical cards configured with a manual activation flow using card details (such as the last four digits) if they have not been activated yet.

By following this flow, you can provide cardholders with a seamless and secure experience when viewing their card details. If you have any questions or need further assistance with card image visualization, our team is available to provide support and guidance. We’re committed to ensuring a smooth and secure experience for both you and your cardholders.