-
Notifications
You must be signed in to change notification settings - Fork 67
Card data for OneClick Payment
This extension returns to the merchant an information related to the OneClick payment Template in addition to the payment/status
or oneclick/echo
response. In case the payment transaction used to set up the OneClick payment Template was successfully authorised, this extension returns masked card number and expiration.
This extension is not available in the basic setup. Please contact akceptacekaret@csob.cz for activation of the extension for your merchant account.
Newly added parameter is extensions
, contains a list of all activated extensions for a given operation. Extension maskClnRP
will be returned only in payment/status
or oneclick/echo
response in case the payment transaction used to set up the OneClick payment Template was successfully authorised.
Parameters in bold will always be returned
Item | Type | Description |
---|---|---|
extension | String | Extension ID (assigned by the gateway). It is always maskClnRP for this particular extension. |
dttm | String | Date and Time of the response (format YYYYMMDDHHMMSS ). |
maskedCln | String | Short masked card number ****XXXX , where XXXX are the last four digits of the card number. |
expiration | String | Card expiration date (MM/YY ). |
longMaskedCln | String | Long masked card number PPPPPP****XXXX , where PPPPPP are the first six digits and XXXX are the last four digits of the card number. |
signature | String | Extension signature, BASE64 encoded. |
Example of a response to payment/status
call with the maskClnRP
extension
{
"dttm": "20220125131601",
"payId": "1112dd54b133@HA",
"resultCode": 0,
"resultMessage": "OK",
"paymentStatus": 7,
"authCode": "453708",
"signature": "base64-encoded-response-signature",
"extensions": [
{
"extension": "maskClnRP",
"dttm": "20220125131601",
"maskedCln": "****0209",
"expiration": "11/16",
"longMaskedCln": "415461****0209",
"signature": "base64-encoded-extension-signature"
}
]
}
Example of a response to oneclick/echo
call with the maskClnRP
extension
{
"origPayId":"0e92dd54b133@HA",
"dttm":"20220125131601",
"resultCode": 0,
"resultMessage":"OK",
"signature":"base64-encoded-response-signature",
"extensions": [
{
"extension": "maskClnRP",
"dttm": "20220125131601",
"maskedCln": "****0209",
"expiration": "11/16",
"longMaskedCln": "415461****0209",
"signature": "base64-encoded-extension-signature"
}
]
}
Cryptographic signature calculation is based on the string of parameters in exactly the same order as listed in the specification (see above).
maskClnRP|20220125131601|****0209|11/16|415461****0209
Note: Signature of the core parameters remains unchanged. The extensions
item does not affect the calculation of the payment/status
response. Each extension has its own signature.
Extension signature and its validation uses the same algorithm SHA1withRSA (for API 1.7 and older) or SHA256withRSA (for API 1.8 and newer).
- Payment lifecycle
- Integration and API security
- Activation of the production environment
- Test cards and credentials
- API Sunset
- Payment Authentication
- Basic Payment
- OneClick Payment
- Custom Payment
- Apple Pay
- Google Pay
- Collecting partial card payment
- ČSOB Payment Button
- Payment Skip Pay
- API Integration
- Request Signing and Response Signature Validation
- API Methods Overview
- Basic Methods
- Methods for OneClick Payment
- Methods for Apple Pay
- Methods for Google Pay
- Methods for ČSOB Payment Button
- Methods for Skip Pay
- Purchase metadata