Deposits
Request deposit
POST
Deposits operation allows you to initiate a deposit for asynchronous processing.
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
depositId
multiple times. - Duplicate requests with the same
depositId
will be ignored with theDUPLICATE_IGNORED
status in the response. - Since the request can rejected, you must check the
status
code in the response for each submitted request. TherejectionReason
in the response will contain information about the reason of the rejection.
Each request can get one of the statuses on initiation:
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 the ACCEPTED
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
See Authentication.
Headers
SHA-256 or SHA-512 hash of the request body.
Body
application/json
Response
200
application/json
Request has been accepted for processing by pawaPay
The response is of type object
.