POST /payment_initiation/consent/payment/execute
The /payment_initiation/consent/payment/execute
endpoint can be used to execute payments using payment consent.
Servers
- https://production.plaid.com
- https://sandbox.plaid.com
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
processing_mode |
String | No |
Decides the mode under which the payment processing should be performed, using
Possible values:
|
client_id |
String | No |
Your Plaid API |
amount |
Object | Yes |
The amount and currency of a payment |
amount.value |
Number | Yes |
The amount of the payment. Must contain at most two digits of precision e.g. |
amount.currency |
String | Yes |
The ISO-4217 currency code of the payment. For standing orders and payment consents, Possible values:
|
scope |
String | No |
Deprecated, payments will be executed within the type of the consent. A scope of the payment. Must be one of the scopes mentioned in the consent. Optional if the appropriate consent has only one scope defined, required otherwise. Possible values:
|
consent_id |
String | Yes |
The consent ID. |
reference |
String | No |
A reference for the payment. This must be an alphanumeric string with at most 18 characters and must not contain any special characters (since not all institutions support them).
If not provided, Plaid will automatically fall back to the reference from consent. In order to track settlement via Payment Confirmation, each payment must have a unique reference. If the reference provided through the API is not unique, Plaid will adjust it.
Some institutions may limit the reference to less than 18 characters. If necessary, Plaid will adjust the reference by truncating it to fit the institution's requirements.
Both the originally provided and automatically adjusted references (if any) can be found in the |
secret |
String | No |
Your Plaid API |
idempotency_key |
String | Yes |
A random key provided by the client, per unique consent payment. Maximum of 128 characters. The API supports idempotency for safely retrying requests without accidentally performing the same operation twice. If a request to execute a consent payment fails due to a network connection error, you can retry the request with the same idempotency key to guarantee that only a single payment is created. If the request was successfully processed, it will prevent any payment that uses the same idempotency key, and was received within 48 hours of the first request, from being processed. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.