Cards

Creates a request for physical card to be sent to a customer.

The search for cards is driven by an index and eventually consistent. That means that an update to a card may take a short while before it is reflected in search results.

A Virtual Card allows for a Charging Token to be generated without the need for a physical charging card or token. Virtual Cards are most useful to control remote sessions across the roaming network e.g. in mobile app implementations, orif there already is an existing physical card that needs to be included within our platform.

Updates card fields. Note that userId and billingPlanId are required on every request, even when updating a single field such as nameOnCard. nameOnCard is stored on the card and does not follow the user record: updating a user's email or name leaves it unchanged, so it must be updated through this endpoint. A card cannot be moved to a different account; its account is always derived from the assigned user.

Upon calling, the card will be disabled and the token will be blocked. An update to the roaming network will be dispatched immediately and the cardholder will not be able to charge.

Upon calling, the card will be enabled and the token will be unblocked. An update to the roaming network will be dispatched immediately and the cardholder will be able to charge. A cancelled card cannot be enabled.