Discover the additional features of Axepta BNP Paribas Online designed to optimize your payment processes. These innovative tools enhance security and enable you to offer a seamless and secure payment experience.


 Automatic End-to-End Reference (RefNr) Generation

Each transaction benefits from a unique automatically generated reference, ensuring complete traceability and clear identification of each operation.

Benefits

  • Optimal Traceability: Track each transaction throughout its lifecycle.
  • Compliance with Standards: The 'an12' format (12 alphanumeric characters) ensures smooth and compliant processing.
  • Guaranteed Uniqueness: Axepta BNP Paribas Online ensures that each reference is unique, avoiding conflicts and errors.

Best Practices

  • Automatic Generation: The reference is automatically generated by Axepta BNP Paribas Online to guarantee its uniqueness.
  • Optional Customization: You can also provide your own reference, provided it complies with the format and ensures its uniqueness.


Duplication Check: Avoid Redundant Payments

Duplication Check in Axepta BNP Paribas Online is designed to detect and manage duplicate payment attempts, ensuring that users and merchants do not accidentally trigger multiple payments with identical parameters.

Benefits

  • Avoid Errors: Reduce the risk of duplicate payments due to user interaction errors or merchant-side logic issues.
  • Improve Customer Experience: Provide a smooth and error-free payment experience.
  • Optimize Transaction Management: Simplify payment management and reduce costs associated with redundant transactions.

Features

  • Operation

    • Duplicate checks are triggered before displaying the payment page and between payment pages.
    • If a duplicate is detected, the user is redirected to the failure URL.
    • No payment is submitted if the request matches an existing or ongoing transaction.
  • Data

    • Duplicate control is based on the following data : amount, currency, merchantReference, and/or invoiceId
      • merchantReference: This data must be used to identify the order; it is defined by the merchant.
      • invoiceId: The invoice identifier associated with this payment; it is defined by the merchant.
      • The amount of the invoice associated with this payment, defined by the merchant.
    • Historical Depth: 1 hour to 4 days (in hours)
    • Scope: 1 or more MIDs
  • Implementation

    • Option 1: Payment made via the Hosted Payment Page (HPP) or the card payment form (payssl)
    • Option 2: Duplicate Verification via API


  • No labels