Purchases
Overview
The Purchase object represents a one-time payment of money from a Buyer to your organization.
Methods
POST
/purchase
Create a new purchase.
Body Parameters
ID of buyer making the purchase.
Array of items in the purchase, each containing a name
, description
, amount_in_cents
, and quantity
info.
If true
, the purchase is eligible to be automatically refunded if a later fraud alert is detected on the payment card, minimizing the risk of chargebacks. A common use case is to set this to true
if you are selling digital goods. Contact Manifest to configure your fraud refund window (default is 72 hours).
The Purchase status will be updated to refunded
and you will receive a purchase.update
webhook after the refund is processed.
User defined data that can be attached to the object. See the User Data page for details.
Example
POST
/purchase
Create a new purchase.
Body Parameters
ID of buyer making the purchase.
Array of items in the purchase, each containing a name
, description
, amount_in_cents
, and quantity
info.
If true
, the purchase is eligible to be automatically refunded if a later fraud alert is detected on the payment card, minimizing the risk of chargebacks. A common use case is to set this to true
if you are selling digital goods. Contact Manifest to configure your fraud refund window (default is 72 hours).
The Purchase status will be updated to refunded
and you will receive a purchase.update
webhook after the refund is processed.
User defined data that can be attached to the object. See the User Data page for details.
Example
POST
/purchase/:id/commit
Execute purchase. Throws an error if the purchase is not in the created
state.
Path Parameters
The ID of the purchase to execute.
Body Parameters
An optional unique identifier for this request. If a second request is made with the same idempotency_id
, the response will return an error.
Example
GET
/purchase/:id
Get details of one of your purchases.
Path Parameters
The ID of the purchase to retrieve.
Example
PUT
/purchase/:id
Update data associated with one of your enterprise’s purchases. Since a checkout page may be rendered anytime after purchase creation, we do not let you update purchase fields that might materially change the nature of transaction.
Path Parameters
The ID of the purchase to update.
Body Parameters
The status of the purchase. Status can only be updated to canceled
, completed
, or refunded
.
If true
, the purchase is eligible to be automatically refunded if a later fraud alert is detected on the payment card, minimizing the risk of chargebacks. A common use case is to set this to true
if you are selling digital goods. Contact Manifest to configure your fraud refund window (default is 72 hours).
The Purchase status will be updated to refunded
and you will receive a purchase.update
webhook after the refund is processed.
User defined data that can be attached to the object. See the User Data page for details.
Example
GET
/purchase
List all purchases from your enterprise.
Query Parameters
The page number to return. Default is 1.
The number of items to return per page. Default is 10.
Example
GET
/buyer/:id/purchase
List all purchases from your enterprise for a specific buyer.
Path Parameters
The ID of the buyer to list purchases for.
Query Parameters
The page number to return. Default is 1.
The number of items to return per page. Default is 10.
Example
Properties
Identifier for this purchase.
ID of buyer making the purchase.
Status of purchase. One of:
Status | Description |
---|---|
created | Purchase has been created. |
pending | Payment was successful, and money is being collected from the buyer. |
settling | Payment is being settled to your operating account. |
completed | Purchase has finished processing, and payment has been received in your operating account. |
error | Purchase has encountered an error. |
canceled | Purchase has been canceled. |
refunded | Purchase has been refunded, and will be updated to reversed once the refund has been processed. If your attempt to refund a purchase fails, the payment will not be able to be reversed without a chargeback being processed. |
reversed | Purchase has been reversed. This can happen if a refund is issued, or a chargeback is processed. |
Array of items in the purchase, each containing a description
, amount_in_cents
, and meta
data. You are responsible for adding items
for tax and shipping, if applicable.
Total amount of the purchase in cents.
Fee amount of the purchase in cents.
Net total amount of the purchase in cents. This amount will be deposited into your operating account.
URL to the receipt PDF for the purchase, once paid.
Brand of the payment card used for the purchase, if available.
Last 4 digits of the payment card used for the purchase, if available.
Array of activity log entries for the purchase, each containing an entry and date.
If true
, the purchase is eligible to be automatically refunded if a later fraud alert is detected on the payment card, minimizing the risk of chargebacks. A common use case is to set this to true
if you are selling digital goods. Contact Manifest to configure your fraud refund window (default is 72 hours).
The Purchase status will be updated to refunded
and you will receive a purchase.update
webhook after the refund is processed.
User defined data associated with the purchase.
Date and time when the purchase was created.
Date and time when the purchase was last updated.