-
Notifications
You must be signed in to change notification settings - Fork 67
Card data for Basic Payment
This extension returns to the merchant new information related to the authorized payment in addition to the payment/status
response. In case the payment transaction 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 maskCln
will be returned only in payment/status
response in case the payment transaction was successfully authorised.
Parameters in bold will always be returned
Item | Type | Description |
---|---|---|
extension | String | Extension ID (assigned by the gateway). It is always maskCln 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 maskCln
extension
{
"dttm": "20220125131601",
"payId": "ff41e84b7e33@HA",
"resultCode": 0,
"resultMessage": "OK",
"paymentStatus": 7,
"authCode": "453708",
"signature": "base64-encoded-response-signature",
"extensions": [
{
"extension": "maskCln",
"dttm": "20220125131601",
"maskedCln": "****0209",
"expiration": "11/23",
"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).
maskCln|20220125131601|****0209|11/23|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