Directly debit the amount from a Wallet that is linked to a Customer’s account. If the status in the response is CHARGED, then the payment is immediatley successful. If the status in the response is PENDING, then the user wallet doesn’t have sufficient balance for the payment and the topup URL is returned in the response.
Note: This is an authenticated call unlike other transaction APIs. This API must be invoked from your server directly. DO NOT send the API Key to client.
For WALLET transactions, the payment_method attribute must be one from this table: wwww (click to open table)
Ola Money wallet
The response for the Wallet Direct Debit API is a Payment Status Object (click to open table)
Unique Identifier for the order.
Transaction ID for the payment attempt.
Status of the transaction. See Appendix below for status mapping. PENDING_VBV indicates that the transaction requires authentication to complete.
URL to which the user has to be taken to for completing the authentication
Present only when the method is POST. This a mapping via a list of key:value pairs that must be sent along with the URL for authentication. Do not hardcode the params in your client * Never assume that you will receive param “x” or param “y”. This is completely dynamic and will vary on a case by case basis.
APPENDIX - Payment status codes and meaning:
Newly created order
Authentication is in progress
User did not complete authentication
User completed authentication, but bank refused the transaction
User input is not accepted by the underlying PG
Transaction status is pending from bank
The request consists of Payment Method Details and a direct_wallet_token, which is a Juspay wallet token for linked wallets (see List Wallets API). Parameters are listed below:
Click Try It! to start a request and see the response here!