VR-ePayment Gateway interface
Definitions
Data formats
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) |
Abbreviations
Abbreviation | Description | Comment |
|---|---|---|
CND | condition | |
M | mandatory | If a parameter is mandatory, then it must be present |
O | optional | If a parameter is optional, then it can be present, but it is not required |
C | conditional | If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional |
Notice: Please note that the names of parameters can be returned in upper or lower case.
Deleting person-related data
Deleting person-related data according to GDPR
According to the European General Data Protection Regulation (GDPR) in force as of May 2018 VR-Payment is obligated to provide an interface for merchants where they can delete person-related data on demand of end customers. By calling the API interface privacy.aspx all data existing and relevant for reasons of data protection data can be deleted.
Deleting of person-related data based on PayID is possible via a Server-to-Server connection. In order to delete person-related data of a transaction, please use the following URL:
https://vr-epayment-gateway.de/privacy.aspx |
Notice: For security reasons, VR-ePayment Gateway 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:
Parameters for deleting person-related data via socket connections
The following table describes the result parameters with which the VR-ePayment Gateway 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. MerchantId, RefNr) should not be checked case-sentive
Response parameters for deleting person-related data via socket connections