Learn more!
See what the deposit flow looks like with pawaPay and for your customers.
- This API call is idempotent, which means it is safe to submit a request with the same
depositIdmultiple times. - Duplicate requests with the same
depositIdwill be ignored with theDUPLICATE_IGNOREDstatus in the response. - Since the request can rejected, you must check the
statuscode in the response for each submitted request. TherejectionReasonin the response will contain information about the reason of the rejection.
| Status | Description | |
|---|---|---|
ACCEPTED | Yes | The deposit request has been accepted by pawaPay for processing. |
REJECTED | No | The deposit request has been rejected. See rejectionReason for details. |
DUPLICATE_IGNORED | No | The deposit request has been ignored as a duplicate of an already accepted deposit request. Duplication logic relies upon depositId. |
How to find out the final status of this deposit?
As the pawaPay Merchant API is an asynchronous API, you can find out the final status of theACCEPTED deposit by either:
Waiting for a callback
If you have configured callbacks, just wait for it.
Checking the status
Or poll the Check Deposit Status endpoint.
Headers related to signatures must only be included if you have enabled “Only accept signed requests”. Read more about it from the pawaPay Dashboard documentation.
Authorizations
Headers
Body
application/json
Required string length:
36Example:
Required string length:
1 - 23Example:
Example:
Example:
Example:
Required string length:
4 - 22Example:
Example:
Required string length:
1 - 36Example:

