Understand the outcome.
An HTTP response describes the request. The payment state describes the movement of funds. Check both before taking the next step.
HTTP responses#
200Request accepted
Read the response body. A successful creation does not mean the payment has completed.
400Request needs attention
Inspect the endpoint’s validation error. Correct the request or confirm the merchant’s enabled methods and limits.
401Authentication failed
Check the Bearer token, signature, merchant ID and account activation.
500Outcome may be uncertain
Do not blindly repeat a creation request. Reconcile the status first; contact the integration team if you cannot identify the created payment.
Recover with the status API#
Use the payment or payout UUID returned by creation for status checks. If an uncertain response did not return an ID, ask the team to reconcile the order before retrying.
Endpoint-specific errors#
Each endpoint includes its documented failure codes, lifecycle states and creation guarantees. Refer to those details when implementing recovery logic.