Custom
Key | Format | CND | Description |
---|---|---|---|
Custom | ans..1024 | O | "Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in request. By this they are protected against manipulation by a consumer. The Custom-value is added to the response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose. Please find a samples here: Custom |
Sample with multiple custom key-value-pairs
action | request / response | Comments |
---|---|---|
request / Aufruf |
encrypted Request:
|
and is part of Blowfish-encrypted Data |
response / Antwort |
| You receive Len + Data as encrypted response Custom-value is now part of response in plain text and not encrypted and "|" has been replaced by "&" so you can receive multiple key-value-pairs. |
response / Antwort | mid=YourMerchantId&PayID=a0b2dh1234....&Custom1Key=Custom1Val&Custom2Key=Custom2Val&Custom3Key=Custom3Val | You receive -response unencrypted Custom-value added to response in plain text and "|" has been replaced by "&" so you can receive multiple key-value-pairs. |
Sample with multiple custom values
action | request / response | Comments |
---|---|---|
request |
encrypted Request:
|
and is part of Blowfish-encrypted Data |
response |
| You receive Len + Data as encrypted response Custom-value is now part of response in plain text and not encrypted and "|" has been replaced by "&" so you can receive multiple values. |
response | mid=YourMerchantId&PayID=a0b2dh1234....&Custom1Val&Custom2Val&Custom3Val | You receive -response unencrypted Custom-value added to response in plain text and "|" has been replaced by "&" so you can receive multiple values. |