Logo |
|
Info | RBI |
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 RBI
Besides the general parameters described below for the credit card connection, RBI 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 |
TransID | ans..20 | M | TransactionID which should be unique for each payment |
RefNr | ans..20 | O | 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. The format pattern is: [A-Za-z0-9.] Special characters like Space, Comma or Colon are removed, only the Point is possible as for example "A1234567890B", "A.1234567890B", "Abcdefg1234", "1234Abcdefg". |
OrderDesc | ans..512 | M | Description of purchased goods, unit prices etc. |
CountryCode | a3 | O | On the basis of CountryCode the respective account information like RBI MerchantID and TerminalID can be retrieved at Computop |
RTF | a1 | O | for recurring payments (subscriptions): I = Initial payment of a new subscriptionR = Routine payment (Recurring) |
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 |
TransID | ans..20 | M | TransactionID which should be unique for each payment |
RefNr | ans..20 | O | 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. |
ErrorText | ans..128 | O | Detailed RBI error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with 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.