Create a call to the payment page

The payment page hosted by Axepta BNP Paribas is used when a merchant wants to offer a complete and customized payment experience to their customers. This method is ideal for e-commerce sites that want to integrate a secure payment solution compliant with current standards.

This integration requires minimal development effort, supports multiple payment methods under a single implementation, and ensures that customer sensitive data remains entirely within Axepta BNP Paribas systems. By outsourcing payment processing, your business significantly reduces responsibilities and costs related to PCI-DSS compliance.

Summary

1. Key Advantages

• Optimized User Experience: Provide your customers with an intuitive, secure, and responsive payment interface

• Minimal Development Effort: Offer multiple payment methods under a single implementation

• Compliance with Standards: Comply with current regulations through Axepta BNP Paribas's management of customer sensitive data, significantly reducing your PCI-DSS compliance responsibilities and costs

2. Payment Flow

 Customer proceeds to checkout on your online store.

1. Your frontend requests the payment page to the backend.

2. Your backend makes a Create checkout session call to Axepta BNP Paribas.

3. Axepta BNP Paribas responds with the redirect URL to your backend.
4. Your backend orchestrates the browser to redirect the User Interface to the redirect URL.
5. Customer is redirected to Hosted payment page hosted by Axepta BNP Paribas.
6. Customer selects its preferred payment method and completes payment.
7. Upon completion, customer is redirected to the return URL that was submitted by you during Create checkout session call (urls.return) with payId in the query parameters.
8. Browser fetches the return URL hosted by your backend.
9. Backend makes a GET Payment details call with payId to retrieve the response code of the payment.
10. Axepta BNP Paribas responds with the responseCode of the payment along with other parameters.
11. Backend returns a success or a failure page based on the response code of the payment.

3. Create checkout session (pas à pas)

(Documentation swagger de l'api /payment/session: Create checkout session )

Connection technical data

Technical connection data must be passed in the HTTP headers of the REST request:

• Content-Type

The payload type: data must be passed in a JSON payload.

Content-Type: application/json

• Authorization data received during the OAuth-v2 authentication step

This includes the token type and JSON Web Token (JWT). They must be specified in the 'Authorization' header. Authorization:

• Idempotency ID

Essential for detecting possible HTTP repetitions.

Use the 'Idempotency-Key' header and generate a uuid-v4 as the value

Idempotency-Key: "8f35cb16-2f05-4aa1-85cf-b1e41ee7aec9"

Minimal Data

To initiate payment, the minimum required data includes:

• Merchant-side transaction identifier: 'transId'

• The amount and currency of the transaction: 'amount' object

  • Composed of 'currency' and 'value' data
  • The amount must always be expressed in the smallest unit of the transaction currency (e.g., EUR cents)

• Customer identification: 'customerInfo' object

  • At minimum, the customer's email: 'email'
  • It is highgly recommended to provide customer identification on the merchant website: 'merchantCustomerId'

This data is essential for the 'One-Click' functionality

• Order data: 'order' object

  • At least one of the following: order number 'merchantReference' or invoice number 'invoiceId' generated on the merchant website
  • It is recommended to provide both

• Return URLs: 'urls' object

  • Mandatory addresses for 3 return URLs: return, cancel, webhook

Response and redirect to the payment page

You should receive an HTTP 202 response message indicating that transaction processing has been initiated and that a payment context has been created on the server.

The response body contains the link to the payment page hosted on the Axepta BNP Paribas Online platform.

You must redirect the customer's browser to this link.

4. Recommendations

We recommend transmitting at least the following data:

• Identifiant de la transaction  : L'identifiant unique du paiement
• Montant du Paiement : Le montant à payer par le client.
• Devise : La devise utilisée pour le paiement.
• Identifiant du Client : L'identifiant unique du client
• email : L'email du client
• Identifiant de la commande (order.merchantReference) : L'identifiant de la commande
• Identifiant de la facture (order.invoiceId) : L'identifiant de la facture associé à ce paiement

Our complete guidelines are available here: Integration recommendations - Documentation Axepta BNP Paribas - Axepta

5. Available payment methods

We offer the following payment methods tailored to your specific needs as well as those of your customers:

• Cards
  • American Express (AMEX)
  • Cartes Bancaires
  • Union Pay International (UPI)
  • Diners
  • Discover
  • JCB
  • MasterCard
  • Visa
• Bancontact
• Wallets
  • Apple Pay
  • Google Pay
  • Paypal
• Paiements fractionnés
  • Floa
• Offres de crédit
  • PF Connect
• Virement instantané (Instanéa)
• Wero

6. Related features

• Automatic Generation of End-to-End Reference (RefNr): Each transaction is assigned a unique automatically generated reference.
• Duplication Control: Detect and manage duplicate payment attempts to prevent errors - Enabled during your store configuration or via a support request
• Confirmation Email: Axepta BNP Paribas can send a confirmation email to the customer for successful or failed payments - Enabled during your store configuration or via a support request