• DeutschEnglish

CB2A - AXEPTA BNP Crossborder and French Domestic

Logo

Info

CB2A - AXEPTA BNP Crossborder and French Domestic

Type

Payments by Credit Card

Introduction

For more information about acquirers and connection, integration with Computop Paygate and Implementation of 3-D Secure (2.x), see chapter Card processing - common introduction.

Specific parameters for CB2A: AXEPTA BNP Crossborder and French Domestic

For credit card connection CB2A: AXEPTA BNP besides the general parameters described above CB2A requires the following additional parameters. An authorisation with 3-D Secure is possible.

Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the additional encrypted payment request parameters described below for "interface via form" and "interface via Server-to-Server" :

Key

REST

Format

CND

Description

RefNr

"referenceNumber": "..."

an12

C

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

Notes:

  • CB2A requires

    • fixed length of 12 characters, Paygate automatically align value to the right and add "0" (zero) to the left

    • only characters (A..Z, a..z) and digits (0..9) are allowed, no characters like underscore, minus, ...

    • RefNr is mandatory in case of "pre-authorization" by CB2A ( a MerchantID can be setup on Paygate either to handle "authorization" or "pre-authorization")

AccVerify

"payment": {"card": { "<accountVerification": "..." }}

a3

O

If AccVerify=Yes the card will be checked at the acquirer according to the acquirer’s interface description. The merchant has to submit only this parameter, the parameter "Amount" is optional. If "Amount" is used we replace the amount according to acquirer’s interface description. At payment always Amount=0 is stored.

Allowed value: yes

RTF

---

a1

O

for repeat payments (subscriptions): I = Initial payment of a new subscription, R = Routine payment (Recurring)

ContractID

n..8

O

Further reference in order to retrieve to combination TerminalID / Contract partner number

Contact data/Address verification (AVS)

AddrStreet

"billing": {"addressInfo": { "addressLine1":{ "street": "..." }}}

ans..20

O

Street name, e.g. Bergstraße

Note: AddrStreet, AddrStreetNr and AddrCity are concated and truncated at 40 characters. Special characters (diacritics) will be converted (e.g. "ü" → "ue", "é" → "e")

AddrStreetNr

"billing": {"addressInfo": { "addressLine1":{ "streetNumber": "..." }}}

ans..30

O

Street number of the customer (for AVS)

AddrCity

"billing": {"addressInfo": { "city": "..." }}

ans..20

O

Town/city of the customer (for AVS)

AddrZip

"billing": {"addressInfo": { "postalCode": "..." }}

n..9

O

Postcode (for AVS)

Additional parameters for credit card payments

The following table describes the result parameters with which the Computop Paygate responds to your system.

these result parameters are additional to the standard parameters for "interface via form" and "interface via Server-to-Server" described below

pls. be prepared to receive additional parameters at any time and do not check the order of parameters

the key (e.g. MerchantId, RefNr) should not be checked case-sentive

Key

REST

Format

CND

Description

RefNr

"referenceNumber": "..."

an12

M

Merchant’s unique reference number, which serves as payout reference in the acquirer EPA file. Please note, without the own shop reference delivery you cannot read out the EPA transaction and regarding the additional Computop settlement file (CTSF) we cannot add the additional payment data.

CodeExt

"externalErrorCode": ...

an2

O

Error code of acquirer, if agreed with Computop Helpdesk

Approvalcode

an..6

O

Approval code / authorization code of acquirer, if agreed with Computop Helpdesk

TerminalID

n..7

O

TerminalId used for processing, if agreed with Computop Helpdesk

VUNr

n..7

O

Acquirer contract number of acquirer, if agreed with Computop Helpdesk

Match

a1

O

Total result of an address verification, if agreed with Computop Helpdesk. For possible values see A3 AVS match parameters

PAR

an..32

O

Scheme Payment Account Reference (PAR) in response. PAR-value is not provided by all schemes already. To enable pls. contact Computop Helpdesk.

Additional response parameters for credit card payments

Card processing - Credit Card Form

For more information about credit card processing via forms, please see chapter Credit Card Form (paySSL).

Card processing - Server-2-Server integration

For more information about credit card processing via server-to-server communication, please see chapter Server-2-Server Integration.

Capture / Credit / Reversal

For more information about capture, credit, reversal and credit card payment via POS terminals, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

PayNow

For more information about PayNow, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Batch processing via the interface

For more information about batch processing, please see chapter Card processing - Capture / Credit / Reversal / PayNow / Batch.

Paygate

Documentation (EN)

Dokumentation (DE)

Paygate Status