🚧
Idempotency Key (Optional Best Practice)
While Pockyt already prevents duplicate processing internally, using idempotency key ensures clients always receive the original transaction response - especially critical during network failures, browser refreshes, or mobile app retries where the initial response might be lost. Without the key, users won't know if their transaction succeeded; with it, they'll reliably get the original outcome.

The idempotency key must be sent in the Pockyt-Request-ID header.

New to idempotency? See our implementation guide: Idempotency key in Pockyt

📘
Side notes

To explore the full list of available payment methods, please check this link Available Payment Methods - PayOuts

Transaction Status Codes

The subsequent table outlines the definitions for various status codes that could be returned in the status parameter following a transaction API request. This table is crucial for interpreting the state of a transaction processed through the API, providing clarity on the outcome and indicating any necessary follow-up actions or confirmations.

Value	Description
pending	The payout request has been successfully received by the system. It is currently in the queue for processing. You should monitor the transaction status, as it will update once the processing is complete.
success	The transaction has been processed without any issues, and the funds have been credited to the recipient's account. No further action is required unless you have post-payment processes in place.
failed	The payout request was not completed, and the funds were not deducted from the sender's account. This could be due to various reasons such as insufficient funds, incorrect payment details, or a system error. Review the provided error details, rectify any issues, and attempt the payout again if appropriate.
returned	The payout request was cancelled after it was initiated. This could occur if the recipient's account rejects the funds or if there's an issue with the payment method. Ensure the account and payment details are correct and contact support if you need clarification on the cancellation.