Paygate interface
Format Description a alphabetical as alphabetical with special characters n numeric an alphanumeric ans alphanumeric with special characters ns numeric with special characters bool boolean expression (true or false) 3 fixed length with 3 digits/characters ..3 variable length with maximum 3 digits/characters enum enumeration of allowed values dttm ISODateTime (YYYY-MM-DDThh:mm:ss) Abbreviation Description CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Generation of PBAN or PCNr
Some non-PCI DSS-compliant merchants need to store IBAN or CCNr in advance (without making a payment) for future payments.
As a solution a endpoint, which receives IBAN/CCNr and returns PBAN/PCNr (using CT tokenization function), was introduced.
Requirements
- New endpoint getToken.aspx was introduced.
- Basic IBAN check and CCNr check (validation of check sum) should be performed at generating token (PBAN or PCNr).
- The Blacklist is not checked at token generation. Blacklist will be checked when a merchant sends a payment request using the token.
Authentication
Blowfish encryption and HMAC verification as for standard credit card interfaces in Paygate.
Calling the interface
In order to generate a PBAN or PCNr from submitted data, please use the following URL:
https://www.computop-paygate.com/getToken.aspx |
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 encrypted payment request parameters:
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. |
| Key | Format | CND | Description |
|---|---|---|---|
| TransID | ans..64 | M | TransactionID provided by you which should be unique for each payment |
Key | Format | CND | Description |
|---|---|---|---|
AccountNumber | ans..64 | M | IBAN or CCNr (based on parameter AccountType) |
AccountType | a4 | O | Possible values: "IBAN", "CCNr" Default value: "IBAN" |
The following table describes the result parameters with which the Computop Paygate responds to your system
pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. mid, RefNr) should not be checked case-sentive
| Key | Format | CND | Description |
|---|---|---|---|
ans..30 | M | MerchantID, assigned by Computop |
| Key | Format | CND | Description |
|---|---|---|---|
| PayID | an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. |
Key | Format | CND | Description |
|---|---|---|---|
| Status | a..20 | M | Status of the request. Possible values: "OK", "FAILED" |
| Description | ans..1024 | M | Further details in the event that the request is not successful |
| Key | Format | CND | Description |
|---|---|---|---|
| Code | an8 | M | Error code according to Paygate Response Codes (A4 Error codes) |
Key | Format | CND | Description |
|---|---|---|---|
| PseudoAccountNumber | ans..64 | M | PBAN or PCNr |
| AccountType | a4 | M | Possible values: "PBAN", "PCNr" |