Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space ENWORK and version Documentation
Page properties
Logo


Info
Excerpt

CB2A REST

TypePayments by Credit Card


Include Page
Card processing - common introduction
Card processing - common introduction

Table of Contents



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.

Multiexcerpt include
SpaceWithExcerptEN
MultiExcerptNameRequest_Intro_Additional
PageWithExcerptReuse API

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
      ((info) a MerchantID can be setup on Paygate either to handle "authorization" or "pre-authorization")
AccVerify"payment": {"card": { "<accountVerification": "..." }}a3O

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

not used

a1

O

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

ContractID
n..8OFurther reference in order to retrieve to combination TerminalID / Contract partner number




Contact data/Address verification (AVS)
AddrStreet"billing": {"addressInfo": { "addressLine1": { "street": "..." }}}ans..20O

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..30OStreet number of the customer (for AVS)
AddrCity"billing": {"addressInfo": { "city": "..." }}ans..20OTown/city of the customer (for AVS)
AddrZip"billing": {"addressInfo": { "postalCode": "..." }}

n..9

OPostcode (for AVS)

Additional parameters for credit card payments


Multiexcerpt include
SpaceWithExcerptEN
MultiExcerptNameResponse_Intro_Additional
PageWithExcerptReuse API

"externalErrorCode": "..."

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
an2O

Error code of acquirer, if agreed with Computop Helpdesk

Approvalcode
an..6O

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

TerminalID
n..7O

TerminalId used for processing, if agreed with Computop Helpdesk

VUNr
n..7O

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


Include Page
Credit Card Form (paySSL) REST
Credit Card Form (paySSL) REST


Include Page
Server-2-Server Integration REST
Server-2-Server Integration REST


Include Page
Card processing - Capture / Credit / Reversal / PayNow / Batch REST
Card processing - Capture / Credit / Reversal / PayNow / Batch REST