ACS Client Validation
Changed onThis API provides 3DS authentication validation for APATA. It forwards the request to the ACS to inform the validation response.
Request
- Base URLhttps://api.uat.paymentology.com/ppws/api
- URLhttps://api.uat.paymentology.com/ppws/api/pws/pws_apata_validation/
- Authnone declared
Request body
Unique txn ID generated by ACS for every transaction.
Unique number that must be passed at each API request. Identifier to make each API request unique
Performed authentication method: <ul><li>If OTP Sent, values would be [OTP Sent]</li><li>If Client Authentication, values would be [biometric]</li></ul>
Unique identifier for the client which Paymentology will provide at outset
Result description
Result code to indicate whether transaction was success or failed • 00-Success • 01-Failure
Unique card token received in the request
User Id of the Customer who triggered the API request.
Remarks for API request
Unique authentication reference received in the request
Example request
{
"acsTranId": "0fdf0f56-053b-457f-bae1-e77e966f66ca",
"api_call_unique_identifier": "438574845790657485",
"authenticationPerformed": "biometric",
"client_id": 760131,
"description": "success",
"responseCode": "00",
"token": 3965473689,
"rid": 6547396547389
}Response
Successful Response
Example response
{
"header": {
"error_desc": "success"
}
}Changes
- info
endpoint added
- info