Verification Endpoint
GET/confirm
Verifies the status of a transaction or payment associated with the specified uniqid. This endpoint is typically invoked once the upstream payment provider completes its processing.
The response status indicates whether:
- The flow is considered clean and the transaction can be processed.
- The transaction has already been processed.
- The flow is not clean and should not be processed.
- The uniqid is invalid or missing.
- A server-side error occurred.
Verification sequence (verbal description):
- Client backend calls GET /confirm with uniqid as a query parameter.
- Shield Verification API returns a status such as OK, PROCESSED, NOT-OK, INVALID UNIQID, ERROR or Missing UNIQID.
- Client backend uses this status, together with gateway data, to make a final decision on fulfilment.
Request
Responses
- 200
- 401
- 403
- default
Verification status response.
Response Headers
Total time taken to process the request, generated by the MCP Shield backend.
Server identifier returned by the API.
Access denied due to invalid or missing credentials or IP restrictions.
Response Headers
Total time taken to process the request, generated by the MCP Shield backend.
Server identifier returned by the API.
Access to the Verification endpoint is forbidden.
Response Headers
Total time taken to process the request, generated by the MCP Shield backend.
Server identifier returned by the API.
Unexpected error.
Response Headers
Total time taken to process the request, generated by the MCP Shield backend.
Server identifier returned by the API.