Private
impersonatingCreate a payment Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
Create a payment transaction Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
ID of the payment.
Required fields: Type, DateExecuted
Delete a payment Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
ID of the payment.
Delete a payment transaction Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
ID of the payment.
ID of the transaction.
Retrieve a payment Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
ID of the payment.
List payments Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
Optional
filters?: FiltersAn object or dictionary representing key/value pairs to apply as filters. Valid keys are top-level properties of the returned model or 'xp.???'
Optional
page?: numberPage of results to return. When paginating through many items (> page 30), we recommend the "Last ID" method, as outlined in the Advanced Querying documentation.
Optional
pageNumber of results to return per page.
Optional
search?: stringWord or phrase to search for.
Optional
searchComma-delimited list of fields to search on.
Optional
sortComma-delimited list of fields to sort by.
Partially update a payment PUT is not a supported method for payments due to the implications associated with modifying certain properties. Patch is only permitted on certain properties that vary depending on order status Check out the docs for more info
Direction of the order, from the current user's perspective.
ID of the order.
ID of the payment.
Generated using TypeDoc
Description
enables impersonation by calling the subsequent method with the stored impersonation token
Example