Payment Status
Last updated
Last updated
© All rights reserved to papaya global 2024
With Papaya Global REST API, you can gain transparency and efficiency in tracking payment status. Our dedicated endpoints allow you to retrieve real-time payment status information, making it effortless to process transactions, verify payment outcomes, or reconcile accounts.
Payment Cycle
As you initiate a payment, it goes through various statuses, with each step associated with a particular status and following a looped pattern.
PENDING
The payment is currently awaiting execution until it is approved or the execution date is reached.
PROCESSING
Once the transaction is executed, it enters the processing phase, marking an intermediate state before proceeding to any final states.
PROCESSED
Payment instructions have been forwarded to the partnered bank/service for completion. The transaction is either in progress at the bank or awaiting confirmation of its final status (SUCCESS/FAILURE).
COMPLETED (Final State)
The partnered bank successfully completed the transaction, and the amount has been transferred to the customer's account.
FAILED (Final State)
The payment could not be completed because of an error or decline. Keep in mind that this issue may arise due to reasons like insufficient funds, incorrect account or beneficiary information, and more. To prevent such occurrences, consider utilizing the Low Balance Alert Webhook and Verification APIs for better transaction management.
PARTIAL
Split payments (such as Yen > 1M) mark a partial completion of the multiple transactions within the payment.
CANCELLED (Final State)
The user or system has canceled or deleted the payment prior to processing. This transition occurs only when the payout is in a PENDING state.
Error Handling: Should there be any issues retrieving the payment status, our API will return appropriate error codes and messages, enabling you to handle exceptions in your application accordingly.
Please ensure your systems handle all payment statuses for a smooth user experience. Subsequent sections of this documentation provide detailed information on each status type, webhook configuration, and error codes.
