Skip to content
Menu

Cartes Bancaires

Cartes Bancaires (CB) is the domestic card scheme in France, widely used by French banks and often issued as co-branded cards with Visa or Mastercard.
SIBS Gateway supports the processing of Cartes Bancaires transactions, allowing merchants to route eligible card payments through the CB network instead of the standard card scheme.


Cartes Bancaires can be integrated using:

When the Cartes Bancaires service is available, the payment interface may present the option for the customer to select Cartes Bancaires as the preferred payment routing before completing the payment.
If this option is not selected, the transaction will proceed through the standard payment flow, being processed by the default card scheme (such as Visa or Mastercard).


The following sections describe the steps required to process payment using Cartes Bancaires through the SIBS Gateway.

1. Create the order using CRTB as payment method

The first step is to create the order using the standard card integration flow.
When the payment can be processed through the Cartes Bancaires network, the response may include CRTB in the list of available payment methods.
CRTB is the identifier used by the SIBS Gateway to represent the Cartes Bancaires payment routing.

This request follows the same structure used for regular card payments. For more information about the request structure, please refer to the Integration page.
Below is an example of how to create the order.

After the order is successfully created, the response may indicate that the Cartes Bancaires service is available for the transaction.

To confirm that the transaction can proceed using Cartes Bancaires, you should check the following fields in the response:

</> JSON

{
  "paymentMethodList": [
    "CARD",
    "CRTB"
  ],
  "cartesBancaires": {
    "cartesBancairesService": "true"
  }
}
  • CRTB in paymentMethodList indicates that Cartes Bancaires is available as a payment routing option for the transaction;
  • cartesBancairesService: true confirms that the transaction can be processed through the Cartes Bancaires network.

This response indicates that the transaction can proceed using the Cartes Bancaires service.

2. Perform the Purchase Request

After the order has been successfully created (Step 1), the next stage is to perform the payment request for the transaction. At this stage, the card details required to process the payment are provided and the transaction is submitted for authorization.

Notification

Important: How the card details are sent depends on the type of integration:

 

  • Server-to-Server integration: The merchant system sends the card details directly in the request to the Card Purchase API.
  • Payment Form integration: The card details are collected securely by the Payment Form and sent directly to the Card API, minimizing the handling of sensitive data by the merchant.

Below is an example of a one-time purchase transaction request using Cartes Bancaires (CRTB). The table lists all required and optional parameters for the request.

Request Parameters
FieldTypeConditionDescriptionExample
cardInfoobjectMandatoryObject that defines the payment operation request fields.
cardInfo.PANstring ≤ 40OptionalThe Primary Account Number (credit card number).497010******0154
cardInfo.secureCodestring ≤ 40OptionalThe security code (CVV/CVC) associated with the credit card.123
cardInfo.validationDateISODateTimeMandatoryThe expiration date of the credit card.(2028-12-01T00:00:00.000Z)
cardInfo.cardholderNamestringMandatoryThe name of the cardholder as it appears on the credit card.John Doe
cardInfo.createTokenbooleanMandatoryIndicates whether a token should be created for future use.false
cardInfo.cardBrandRoutingTypestring Exact4TextMandatoryDefines the routing network used to process the card transaction. For Cartes Bancaires transactions this value must be CRTB.CRTB

After performing the payment, a response will be received containing a paymentStatus in the message.
This field informs whether the transaction was:

  • Accepted
  • Declined
  • Still pending a final result
  • Requiring additional action (3DS challenge, DCC, etc).

NOTE: To enable Cartes Bancaires, the integrator must include the following in the request:

</> JSON
{
  "cardInfo": {
    "cardBrandRoutingType": "CRTB"
  }
}

The response above indicates that the transaction has been acknowledged and that the service is enabled, allowing the gateway to proceed with the transaction using Cartes Bancaires.

3. Get the Payment Status

Once the payment has been processed, you can check the status of your transaction by performing a GET request.
This request allows you to retrieve the result of the payment, including whether it was accepted, declined, pending, or if any additional action is required.

You can test this GET request in Postman to see the live response and confirm the paymentoutcome.

After executing the request, you can inspect the response returned by the API.
The following fields indicate the final result of the transaction:

</> JSON
{
  "transactionID": "ScHR4JHgQXd4vrFQw1n9",
  "amount": {
    "currency": "EUR",
    "value": "50.50"
  },
  "paymentStatus": "Success",
  "returnStatus": {
    "statusCode": "000",
    "statusMsg": "Success"
  }
}
  • paymentStatus indicates the current state of the payment (for example: Success, Declined, Pending).
  • returnStatus.statusCode provides the technical result of the request.
  • transactionID identifies the transaction being queried.
Notification

Tip: You can explore the complete response in Postman to see all available fields.

Przegląd prywatności

Ta strona korzysta z ciasteczek, aby zapewnić Ci najlepszą możliwą obsługę. Informacje o ciasteczkach są przechowywane w przeglądarce i wykonują funkcje takie jak rozpoznawanie Cię po powrocie na naszą stronę internetową i pomaganie naszemu zespołowi w zrozumieniu, które sekcje witryny są dla Ciebie najbardziej interesujące i przydatne.

Ściśle niezbędne ciasteczka

Niezbędne ciasteczka powinny być zawsze włączone, abyśmy mogli zapisać twoje preferencje dotyczące ustawień ciasteczek.