Payments
Your Users can pay for Orders and Subscriptions. But they'll need a Payment Method.
When you want to pay, you need to use the Payment object. Together with a Payment Method, among other fields, you’ll be able to create and process payments, as well as list all available payments.
Payment Object
Attributes | Type | Description |
|
| The |
|
| Amount as a Float with decimal points. Example: 10.23 USD |
|
| Amount as a Float with decimal points. Example: 10.23 USD |
|
| Amount as a Float with decimal points. Example: 10.23 USD |
|
| 3 letter ISO currency code as defined by ISO 4217. |
|
| Human readable ID. 6 characters long. |
|
| Order or Subscription ID. |
|
| Current state of payment. Can be: |
| boolean | Default is |
|
| Date for scheduling payment, |
|
| ID of existing Payment Method. |
|
| The |
|
| Some additional description, if desired and supported by payment provider. |
|
| Additional information on the payment, if supported by payment provider. |
|
| If the payment fails, this will have some code from the chosen payment method backend. |
|
| If the payment fails, this will have text describing the reason. |
*Paths listed below with an asterisk are accessible to both User and Admin Roles.
Payment for Orders*
Pay for an Order or multiple Orders at once.
Arguments | Type | Description |
|
| List with |
|
| Selected |
Retrieve a Payment*
Argument | Type | Description |
|
| ID of the queried payment. |
List all Payments*
Query Parameters | Type | Description |
|
| Number of resources per page. Default is 10. |
|
| Defines which page to retrieve. Default is 0. |
|
| Start date, |
|
| End date, |
|
| Field used to sort results. |
|
| Status of the payment. |
Update Payment*
Only the below fields are editable in a payment.
Arguments | Type | Description |
|
| Default is |
|
| ID for payment method. |
|
| The Billing Address for they payment method. |
|
| Update payment date, |
Last updated