POST /transaction/charge_authorization
Servers
- https://api.paystack.co
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 |
|---|---|---|---|
split_code |
String | No |
The split code of the transaction split |
transaction_charge |
Integer | No |
A flat fee to charge the subaccount for a transaction. This overrides the split percentage set when the subaccount was created |
email |
String | Yes |
Customer's email address used during the first transaction |
amount |
Integer | Yes |
Amount should be in kobo if currency is NGN, pesewas, if currency is GHS, and cents, if currency is ZAR |
metadata |
Object | No |
Stringified JSON object of custom data |
subaccount |
String | No |
The code for the subaccount that owns the payment |
queue |
Boolean | No |
If you are making a scheduled charge call, it is a good idea to queue them so the processing system does not get overloaded causing transaction processing errors. |
reference |
String | No |
Unique transaction reference. Only -, ., = and alphanumeric characters allowed. |
authorization_code |
String | Yes |
Valid authorization code to charge |
currency |
String | No |
The transaction currency Possible values:
|
bearer |
String | No |
The bearer of the transaction charge Possible values:
|
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.