Logo | |
Info | PPROCC |
Type |
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 PPROCC
Besides the general parameters described above for the credit card connection, PPRO 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 | Format | CND | Description |
|---|---|---|---|
RefNr | ns..30 | MC | Not with 3-D Secure: 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. Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...). |
OrderDesc | ans..768 | M | Description of purchased goods, unit prices etc. |
UserData | ans..1024 | OC | Not with 3-D Secure: If specified at request, Paygate forwards the parameter with the payment result to the shop. |
CreditCardHolder | ans..60 | MC | Not with 3-D Secure: Name of the card holder in the format: <First name><space character><Last name> |
CustomerID | ans..64 | O | Customer number. Format must be mutually agreed beforehand with Computop Helpdesk! |
ans..50 | O | Selling point | |
ans..50 | O | products or service sold | |
ans..64 | O | Configuration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system. | |
AddrCountryCode | a2 | M | Country code according to ISO-3166-1, alphanumeric 2 chars |
RTF | a1 | O | for repeat payments (subscriptions): I = Initial payment of a new subscription, R = Routine payment (Recurring) |
ChDesc | ans..256 | O | Text printed on the customer’s credit card bill alongside the payee |
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 | Format | CND | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
RefNr | ns..30 | MC | Not with 3-D Secure: 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. Only ASCII characters allowed, special characters ("Umlaute", diacritics) are not allowed and must be replaced by their ASCII-representation (e.g. ü → ue, é → e, ...). | ||||||||
UserData | ans..1024 | OC | Not with 3-D Secure: If specified at request, Paygate forwards the parameter with the payment result to the shop. | ||||||||
ans..26 | O | Purpose of payment | |||||||||
a..12 | C |
Notice: This parameter is only returned if the Status=OK. | |||||||||
ans..128 | C | Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk. | |||||||||
CCBIN | n6 | O | first six digits of the credit card number | ||||||||
Status | a..50 | M | OK or AUTHORIZED as well as FAILED. For PPRO there is also AUTHORIZE_REQUEST. |
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.