Overview

The Buyer object represents a customer that pays money to your organization.

Methods

POST  /buyer
Create a new buyer under your enterprise.

Body Parameters

first_name
string
Legal first name from your records.
last_name
string
Legal last name from your records.
external_id
string
Optional user identifier from your system. If set, Manifest will enforce uniqueness, e.g. attempts to create a second buyer for the same user will fail.This should be a stable value like a User ID, not something that might change like an email address or phone number. This value should not contain any sensitive information.
email
string
Email address from your records.
payment_instrument_id
string
ID of the payment instrument to associate with the buyer, if you have one. Primary usage is migrating existing customers to Manifest.
user_data
object
User defined data that can be attached to the object. See the User Data page for details.

Example

// POST /buyer
{
    "first_name": "Paul",
    "last_name": "McCartney",
    "email": "paul@thebeatles.com",
}

Properties

id
string
Identifier for this buyer.
first_name
string
Legal first name from your records.
last_name
string
Legal last name from your records.
external_id
string
Optional user identifier from your system. If set, Manifest will enforce uniqueness, e.g. attempts to create a second buyer for the same user will fail.This should be a stable value like a User ID, not something that might change like an email address or phone number. This value should not contain any sensitive information.
email
string
Email address from your records.
user_data
object
User defined data that can be attached to the object. See the User Data page for details.
payment_method_embed_url
string (read-only)
Embeddable form that allows your buyers to securely manage their payment method. You should not store this URL, as it may change over time. See Payment Methods for details.
card
object
The buyer’s stored payment card details. If null, the buyer has no stored card.