b.connect
b.connect is a highly convenient authentication service, as it separates the authentication step from the actual payment: your customers identify themselves when connecting to your webshop.
b.connect is a coalition of French banking groups that bases the authentication mechanism on
- The cardholder’s identity.
- Their device used for making payments.
During the checkout process, b.connect sends a token to your server that you must send to our platform. By matching the token’s data with the cardholder data at the issuer’s side (i.e., the technical data of the device used, cardholder name, e-mail address), b.connect ensures the legitimate use of the card.
By integrating b.connect into the 3-D Secure ecosystem, the authentication process becomes a background process and thereby
- Smooths out your customers’ checkout process.
- Improves your conversion rate.
- Make sure to contact us before using this feature, as you need to enrol for this service.
- b.connect is available for Cartes Bancaires via integration methods Hosted Checkout Page/Server-to-server.
Process flows
This is a high-level payment flow that covers only the mandatory steps. Read the dedicated chapter in our Server-to-server/Hosted Checkout Page guide for detailed information, code samples and optional steps in the flow. For specific information about the 3-D Secure authentication flow, read the dedicated chapter in our 3-D Secure and SCA guide.
- Your customers enrol for b.connect via their banking app, linking their device's technical data to their bank profile.
- You add the b.connect button on your checkout page according to the b.connect documentation.
- Your customers finalise an order in your shop and click on the b.connect button.
- b.connect retrieves the authentication data from your customers' issuer. It authenticates your customers' identity either via a frictionless or challenge authentication flow.
- The b.connect platform returns a CICO (check-in, check-out) token to your server, confirming the successful authentication.
- Your customers provide their card details on your checkout page (for Server-to-server) or the Hosted Checkout Page.
- You send this CreateHostedCheckout/CreatePayment request to our platform, including the CICO token (order.customer.account.data) and some additional b.connect-specific properties.
- We send the token and the payment data to the 3-D Secure network.
- The 3-D Secure network matches the token/payment data with the data on the issuer's side.
- We receive the 3-D Secure authentication result.
- We process the transaction and receive the result from the acquirer.
- You request the transaction result from our platform via GetPaymentDetails/GetHostedCheckout or receive the result via webhooks.
Integration
Make sure to add a b.connect button to your checkout page as described in the b.connect documentation.
Add the following properties to a standard CreateHostedCheckout/CreatePayment request:
Properties | Description |
---|---|
cardPaymentMethodSpecificInput.paymentProduct130SpecificInput.threeDSecure.usecase |
Cartes Bancaires-specific 3-D Secure mandatory properties. Refer to our 3-D Secure implementation guide to learn more. |
order.customer.account |
data: The CICO token you have received in step 5 of the payment flow. method: Indicates the authentication method for this transaction. Fixed value "cico-b-connect-token". timestamp: The timestamp of the b.connect authentication (Format YYYYMMDDhhmm). |
Depending on the integration method, differences apply. Find an example for all in the "Testing" chapter.
Testing
Add the following properties to a standard CreateHostedCheckout/CreatePayment request:
Use one of the Cartes Bancaires test cards producing a 3-D Secure frictionless flow from our test cases.
CreateHostedCheckout | CreatePayment |
---|---|
|
|