Your Response to DelegateSCANotification

Expected acknowledgement

Upon receipt of a DelegateSCANotification request, your system should return a 200 HTTP response code. If the notification is not acknowledged successfully, the notification may not be resent.

Authorization Header Example

The delegated SCA notification may include a bearer token in the request header. Your system can validate this token according to the security controls agreed for the integration.

Authorization: Bearer <access_token>

DelegateSCAValidation Request

When the Biometric / In-App authentication is complete, your system sends the authentication result back to Payblr. Payblr then returns the validation result to the processor.

{
  "NotificationId": "f88458df-20ea-49b7-b890-119c2f5e8c6e",
  "PubToken": "123456789",
  "DelegateScaId": "bcd507g1-7ec8-43b4-8a07-6c5e17078967",
  "PmReferenceId": "refId",
  "Status": "SUCCESS",
  "Error": null
}

Validation timeout

The authentication session times out if the DelegateSCAValidation result is not received before the ChallengeExpiry time provided in the original DelegateSCANotification.

Successful DelegateSCAValidation Response

{
  "PubToken": "206187551",
  "DelegateScaId": "ddab0431-a615-42d7-81ab-5a6683bb5c3e",
  "PmReferenceId": "refId",
  "Status": "SUCCESS",
  "Error": {
    "ReferenceNumber": "",
    "Description": "",
    "Message": ""
  }
}