Approve Payment Requests

post

https://api-sandbox.paymentlabs.io/payment-requests/received/approve

Approves payment requests, and nothing else: no batch, no ledger account, no payment.

The requests come to rest at APPROVED, and their payments can be raised afterwards with
Approve and Pay — which accepts an already-approved request for exactly that reason. Use this
when the decision and the payment are separate steps for you.

A 200 does not mean every request was approved. Read results: approvedCount and
failedCount can both be non-zero on the same response, and each refused row carries its own
errorCode. A 4xx means the call itself was unusable and nothing at all was written.

Errors

400 INVALID_REQUEST_IDS: requestIds is missing, empty, over 50, or holds duplicates
423 NOT_EDITABLE: a request named is in a state no decision can be made from

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

Bearer

JWT

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The decision was recorded. Read results for what became of each request

401Unauthorized response, when the user is not authenticated or the authentication token is missing in the header.

403 Forbidden response, when the user is authenticated but does not have the necessary permissions.

423 The record is in an state that cannot be edited, check the message and code for more information on why the record cannot be edited. e.g,: When a payment has already been paid, it's value cannot be changed.