KYC callback
Description
This is a callback to notify partners BE-BE about the KYC process completion. The endpoint is to be implemented by the partner where we can send the callback as per the contract mentioned.
Host
To be provided by partner
Endpoint
/v1/callback/partner
Method
PUT
Headers
| Header Key | Description | Example |
|---|---|---|
| Authorization | Linking token received after login step | |
| Content-Type | Standard HTTP content-type header | application/json |
Request payload
{
"submissionId": "submission-uuid",
"partnerSessionId": "<submission.partnerSessionId>",
"status": "COMPLETED",
"result": "VALID",
"reasonCode": null
}| Field | Description | Example |
|---|---|---|
| submissionId | If multiple submissions are made for the same partnerSessionId, this field uniquely identifies a submission. Currently, the use case suggested is for debugging purposes only. | |
| partnerSessionId | request-id from the start of the Gopay ID process | |
| status | Identifies whether the KYC process successfully completed or met a technical error | COMPLETED|ERROR |
| result | Identifies whether the KYC is approved, rejected | VALID|INVALID |
| reasonCode | For the following combinations, this field identifies the cause of the same.
|
Updated 8 days ago
Did this page help you?