Prerequisites

The prerequisites to call this endpoint are:

• Client Authentication.
• Offer partner code.
• Cardholder existence.
• Account existence.

Diagram & status for a virtual card

Order a virtual card: sequence diagram for all environment

Virtual card order process

sequenceDiagram
Title Virtual card order process 
autoNumber
Participant Partner
Participant XPO
Participant BPCE

Partner ->> XPO : Order a virtual card <br/> POST api/v3.0/cards/virtual
XPO ->> Partner :return OK (201)
XPO -->> Partner : Send CardCreatedOrUpdated (status:Sent)

❗️

The virtual card has to be activated to be used.

States diagram for virtual cards

stateDiagram
state fork_state3 <<fork>>
state fork_state4 <<fork>>

  Inactive --> fork_state3
  fork_state3 --> Activated
  Activated --> fork_state4

  fork_state3 --> Canceled
  fork_state3 --> Opposed
  fork_state3 --> Expired

  fork_state4 --> Canceled
  fork_state4 --> Opposed
  fork_state4 --> Expired 

  Expired --> [*]
  Canceled --> [*]
  Opposed --> [*]

Configuration when creating the environment

Card validity period

The card's validity period is fixed and is set when the environment is created.

Card offers and visual codes

{
  "cardId": "my_card_reference",
  "cardholderId": "145644-060820-USER-8550478",
  "accountId": "145644-060820-ACCOUNT-8550478",
  "offerPartnerCode": "DemoClassicPhysicalDebitVISA",
  "visualCode": "NOCP"
}

The card offer allows you to find out the type of card you want (classic, premier, etc.) and its characteristics. This information is an input for card creation.

For each offer, you can have several visuals. All these visuals are validated with BPCE PS and VISA and then configured at Xpollens.

Pan ranges

They are chosen by Xpollens.

API, Callback & technical items

Card order

🔗Virtual Card order

Callbacks

🔗Card Order status