Each 'Create' request sent to PaymentsOS creates a resource (e.g. 'Create Payment' creates a Payment resource and 'Create Authorization' creates an Authorize resource and so on). The Payment Search in the Control Center is resource-based. This means that if a resource was not created for any given reason, it will not be displayed in the Payment Search.
If you are unable to see a specific Authorize attempt in the Payment Search it means that something went wrong during the creation of the specific resource.
You can see the reason for the failure in the response of the specific API request.
- 503 - Service Unavailable, The provider's server is currently unavailable; Resend the request. (Re-sending the request is allowed. Use the same
idempotency-key, to avoid creating multiple resources.)
- 400 - Bad Request, The request failed due to a syntax error, or is missing a required parameter; Review and resend the request.
Read more about Responses.
If you are still unable to conclude why the resource was not created, or why it isn't displayed in the Payment Search, contact ZOOZ support at firstname.lastname@example.org.