Carte Bancaire

Intro

Carte Bancaire (CB) is the local card scheme in France and by far the most commonly issued brand there. CB cards are always co-badged with Visa, MasterCard or (although not very often) Maestro. This allows French customers to use their CB card outside of France.

Following the introduction of EU regulations, you need to offer your French customers CB in addition to Visa / MasterCard / Maestro. This empowers your customers to choose between the different brands.

To comply with this regulation, we offer you the following options for the respective integration method:

Create Payment API: Offer your customers CB on your payment page and create the payment as a CB transaction by sending paymentProductId=130
HostedCheckout API: You have two possibilities
1. Offer your customers CB on your payment page and create the payment as a CB transaction by sending PaymentProductID=130
2. Do not send PaymentProductID at all. The customers can choose their preferred brand on our Hosted Payment Page

If you have an acquiring contract with a French acquirer, this brand will be available by default, provided it has been added in your account

Optimized for Desktop Tablet Mobile

Overview

Payment group:

Cards (debit & credit)

Payment product id:

130

Key benefits

Lower scheme and acquirers fees
Preferred payment method for French customers
Lower fraud rate compared to Visa / MasterCard
Card payments enable e-commerce with a real-time authorization approval/decline response supporting the faster delivery of goods and services to the consumer
Secure payments
Fast settlement cycle
International acceptance(as CB cards are co-badged with Visa / MasterCard)

Boarding

Please make sure that this payment method is activated in your Back Office in Configuration > Payment methods. If this is not the case, contact us.

Countries & currencies

Supported countries

France

Supported currencies

Euro (EUR)

Integration

We offer this payment methods for the following integration modes. Learn in our dedicated guides about their individual differences:

Find a high level overview in the "Process flows" chapter.

Depending on the integration mode, differences apply:

Hosted Checkout Page
Hosted Tokenization Page
Server-to-server/Mobile/Client Integration

Hosted Checkout Page

Add the following properties to a standard CreateHostedCheckout request:


{
	"HostedCheckoutSpecificInput": {
		"ReturnUrl": "https://yourReturnUrl.com"
	},
	"Order": {
		"AmountOfMoney": {
			"Amount": 100,
			"CurrencyCode": "EUR"
		}
	}
}

Properties	Remarks
hostedCheckoutSpecificInput.returnURL	The URL we redirect your customers to after the payment has been finalised
order.amountOfMoney amount currencyCode	amount: The gross amount you want to charge for this order currencyCode: The ISO 4217 currency code for this amount

Find detailed information about this object and its properties in our HostedCheckoutAPI

Hosted Tokenization Page

Add the following properties to a standard Create Payment request (including mandatory 3-D Secure properties) after you have tokenised the card:


{
	"CardPaymentMethodSpecificInput": {
		"Token": "tokenId",
		"ThreeDSecure": {
			"RedirectionData": {
				"ReturnUrl": "https://yourRedirectionUrl.com"
				}
			}
		},
		"Order": {
			"AmountOfMoney": {
				"Amount": 100,
				"CurrencyCode": "EUR"
			},
			"Customer": {
				"Device": {
                                "AcceptHeader": 
"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3",
				"Locale": "en_EN",
				"TimezoneOffsetUtcMinutes": -180,
				"UserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36",
				"Browserdata": {
					"ColorDepth": 24,
					"JavaScriptEnabled": false,
					"ScreenHeight": "1080",
					"ScreenWidth": "1920"
				}
			}
		}
	}
}

Properties	Remarks
cardPaymentMethodSpecificInput.token	Token: The tokenised credit card credentials you have received by tokenising the credentials/getting the token. Learn more in our dedicated Hosted Tokenization Page guide
cardPaymentMethodSpecificInput.threeDSecure redirectionData.returnURL skipAuthentication	returnURL: The URL we redirect your customers to after the payment has been finalised skipAuthentication: Indicate whether to roll out 3-D Secure for this order
order.amountOfMoney amount currencyCode	amount: The gross amount you want to charge for this order currencyCode: The ISO 4217 currency code for this amount
customer.device acceptHeader locale timezoneOffsetUtcMinutes userAgent browserdata colorDepth javaScriptEnabled screenHeight screenWidth	Minimum properties to comply with SCA for 3-D Secure authentication Check our dedicated guide to learn how to request 3-D Secure correctly and our API reference for more information about the properties.

Find detailed information about this object and its properties in our HostedTokenizationAPI/ CreatePaymentAPI

Server-to-server

Add the following properties to a standard CreatePayment request (including mandatory 3-D Secure properties):

{
	"CardPaymentMethodSpecificInput": {
		"PaymentProductId": XXX,
		"SkipAuthentication": false,
		"Card": {
			"CardholderName": "John Doe",
			"CardNumber": "0000000000000000",
			"Cvv": 123,
			"ExpiryDate": 1236
		},
		"ThreeDSecure": {
			"RedirectionData": {
				"ReturnUrl": "https://yourRedirectionUrl.com"
			}
		}
	},
	"Order": {
		"AmountOfMoney": {
			"Amount": 100,
			"CurrencyCode": "EUR"
		},
		"Customer": {
			"Device": {
				"AcceptHeader": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3",
				"Locale": "en_EN",
				"TimezoneOffsetUtcMinutes": -180,
				"UserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36",
				"Browserdata": {
					"ColorDepth": 24,
					"JavaScriptEnabled": false,
					"ScreenHeight": "1080",
					"ScreenWidth": "1920"
				}
			}
		}
	}
}

Properties	Remarks
cardPaymentMethodSpecificInput.paymentProductId cardPaymentMethodSpecificInput.card cardholderName cardNumber cvv expiryDate cardPaymentMethodSpecificInput.ThreeDSecure redirectionData.returnURL skipAuthentication	paymentProductId: The numeric identifier of the payment method on our platform. Find this id in the "Overview" chapter cardPaymentMethodSpecificInput.card: The credentials of the card used for the payment Make sure to fulfill the necessary PCI DSS requirements for sending sensitive data returnURL: The URL we redirect your customers to after the payment has been finalised skipAuthentication: Indicate whether to roll out 3-D Secure for this order
order.amountOfMoney amount currencyCode	amount: The gross amount you want to charge for this order currencyCode: The ISO 4217 currency code for this amount
customer.device acceptHeader locale timezoneOffsetUtcMinutes userAgent browserdata colorDepth javaScriptEnabled screenHeight screenWidth	Minimum properties to comply with SCA for 3-D Secure authentication Check our dedicated guide to learn how to request 3-D Secure correctly and our API reference for more information about the properties.

Properties

Remarks

cardPaymentMethodSpecificInput.paymentProductId

cardPaymentMethodSpecificInput.card
cardholderName
cardNumber
cvv
expiryDate

cardPaymentMethodSpecificInput.ThreeDSecure
redirectionData.returnURL
skipAuthentication

paymentProductId: The numeric identifier of the payment method on our platform. Find this id in the "Overview" chapter

cardPaymentMethodSpecificInput.card: The credentials of the card used for the payment
Make sure to fulfill the necessary PCI DSS requirements for sending sensitive data

returnURL: The URL we redirect your customers to after the payment has been finalised
skipAuthentication: Indicate whether to roll out 3-D Secure for this order

order.amountOfMoney
amount
currencyCode

amount: The gross amount you want to charge for this order
currencyCode: The ISO 4217 currency code for this amount

customer.device
acceptHeader
locale
timezoneOffsetUtcMinutes
userAgent
browserdata
  colorDepth
  javaScriptEnabled
  screenHeight
  screenWidth

Minimum properties to comply with SCA for 3-D Secure authentication

Check our dedicated guide to learn how to request 3-D Secure correctly and our API reference for more information about the properties.

Find detailed information about this object and its properties in our CreatePaymentAPI

Process flows

We offer this payment method for all our integration modes. Regardless of the mode you choose, the flow follows some basic steps as described below. Learn in our dedicated guides about the individual differences

Your customers finalise an order in your shop and select this payment method
You send a CreateHostedCheckout/CreatePayment request to our platform. Depending on your integration mode, differences apply. Check out the “Integration” chapter to find examples for each mode
Our platform sends you a response with instructions for the next steps of the flow
Your customers provide their credit card number and are redirected to their issuer for 3-D Secure authentication
Our system receives the 3-D authentication result from the issuer
We process the transaction and receive the result from the acquirer
We redirect your customer to your returnUrl
You request the transaction result from our platform via GetPayment or receive the result via webhooks
If the transaction was successful, you can deliver the goods / service

Testing

Refer to our Test cases for test data and detailed instructions

Make sure to use the right endpoint and switch back to the live URL as soon as you have finished your tests