Add Customer Profile

Create a new customer profile in the vault.

Response — 201 Created

{
  "code": 201,
  "status": "OK",
  "vault_customer_id": 100864
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`201`)
`status`	string	`OK` on success
`vault_customer_id`	integer	Unique identifier for the newly created customer profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "data must have required property 'customer_name'"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer profile created
`FAILED`	Validation error	Required field `customer_name` is missing from the request

Add Payment Profile

Add a card payment profile to an existing customer vault record.

Response — 201 Created

{
  "code": 201,
  "status": "OK",
  "payment_id": 97555
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`201`)
`status`	string	`OK` on success
`payment_id`	integer	Unique identifier for the newly created payment profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "Customer not exist"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profile created
`FAILED`	Validation error	Customer ID does not exist in the vault

Add ACH Profile

Add a bank account (ACH) profile to an existing customer vault record.

Response — 200 OK

{
  "code": 200,
  "status": "SUCCESS",
  "ach_profile_id": 2290
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`SUCCESS` on success
`ach_profile_id`	integer	Unique identifier for the newly created ACH profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": "Missing required field(s): account_number"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	string	Error message describing the missing or invalid field

Note: Unlike most endpoints where errors is an array, this endpoint returns errors as a plain string.

Error code reference

`status`	Meaning	Typical cause
`SUCCESS`	Success	ACH profile created
`FAILED`	Validation error	Required field `account_number` is missing from the request

Add Payment Profile Using Token

Add a card payment profile to a customer vault record using an existing card token instead of raw card details.

Response — 201 Created

{
  "code": 201,
  "status": "OK",
  "payment_id": 97555
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`201`)
`status`	string	`OK` on success
`payment_id`	integer	Unique identifier for the newly created payment profile

Response — 400 (Validation Error)

{
  "status": "FAILED",
  "errors": [
    "Invalid Token"
  ]
}

Response fields

Field	Type	Description
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Note: This error response does not include a code field.

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profile created from token
`FAILED`	Validation error	Token is invalid, expired, or not found

Edit Customer Profile

Update the details of an existing customer vault profile.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "vault_customer_id": 100864
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`vault_customer_id`	integer	Identifier of the updated customer profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "data/customer_phone Enter a valid Phone Number"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer profile updated
`FAILED`	Validation error	`customer_phone` is not a valid phone number format

Fetch Transaction With Date Range

Retrieve a paginated list of transactions linked to a vault customer profile, filtered by date range.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "SUCCESS",
  "data": [
    {
      "txn_id": 10176309,
      "epi_id": "2319916062",
      "txn_type": "SALE",
      "total_amount": 103,
      "base_amount": 100,
      "batch_no": "185",
      "card_holder_name": "Sheila Mitch",
      "card_scheme": "Visa",
      "city_tax_amount": 0,
      "custom_fee_amount": 0,
      "epi": "2319916062",
      "food_amount": 0,
      "masked_card_no": "4111 XXXX XXXX 1111",
      "reduced_tax_amount": 0,
      "request_date": "03/25/2026",
      "request_time": "02:22:37",
      "rrn": "608406501192",
      "state_tax_amount": 3,
      "surcharge_fee_amount": 0,
      "surcharge_label": "Adjustment",
      "invoicenumber": "",
      "orderdescription": "",
      "phone": "6129160161",
      "email": "[email protected]",
      "subscription_id": "",
      "company_name": "",
      "tran_no": 1,
      "stan_no": "689251",
      "card_type": "DEBIT",
      "approval_code": "TAS318",
      "response_code": "00",
      "switch_response_code": "00",
      "display_message": "",
      "tip_adjusted_count": 0,
      "is_voided": 0,
      "is_reversed": 0,
      "is_auth_completed": 0,
      "is_settled": 0,
      "settled_at": "2026-03-25T06:22:37.000Z",
      "is_offline_approved": 0,
      "is_partial_approved": 0,
      "addtl_data_label1": "Clerk ID",
      "addtl_data_value1": "",
      "addtl_data_label2": "",
      "addtl_data_value2": "",
      "timezone": "EST",
      "refunded_count": 0,
      "processor_name": "TSYS Sierra",
      "transactions_status": "Approved"
    }
  ],
  "total_count": 1,
  "limit": 25,
  "offset": 0
}

Response fields — top level

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`SUCCESS` on success
`data`	array	Array of transaction objects
`total_count`	integer	Total number of matching transactions
`limit`	integer	Maximum number of records returned per page
`offset`	integer	Pagination offset (starting record index)

`data` — transaction object fields

Field	Type	Description
`txn_id`	integer	Unique transaction identifier
`epi_id`	string	Terminal / EPI identifier
`txn_type`	string	Transaction type (e.g. `SALE`, `REFUND`, `VOID`)
`total_amount`	number	Total charged amount in cents
`base_amount`	number	Base transaction amount in cents (excluding fees and taxes)
`batch_no`	string	Settlement batch number
`card_holder_name`	string	Name on the card
`card_scheme`	string	Card network (e.g. `Visa`, `Mastercard`)
`city_tax_amount`	number	City tax amount in cents
`custom_fee_amount`	number	Custom fee amount in cents
`epi`	string	Merchant terminal / EPI identifier
`food_amount`	number	Food amount in cents, if applicable
`masked_card_no`	string	Masked card number (e.g. `4111 XXXX XXXX 1111`)
`reduced_tax_amount`	number	Reduced tax amount in cents, if applicable
`request_date`	string	Transaction date in `MM/DD/YYYY` format
`request_time`	string	Transaction time in `HH:MM:SS` format
`rrn`	string	Retrieval reference number
`state_tax_amount`	number	State tax amount in cents
`surcharge_fee_amount`	number	Surcharge fee amount in cents
`surcharge_label`	string	Display label for the surcharge
`invoicenumber`	string	Merchant-supplied invoice reference, if provided
`orderdescription`	string	Order or item description, if provided
`phone`	string	Cardholder phone number, if provided
`email`	string	Cardholder email address, if provided
`subscription_id`	string	Subscription identifier, if this transaction is part of a subscription
`company_name`	string	Company name, if provided
`tran_no`	integer	Sequential transaction number within the batch
`stan_no`	string	System trace audit number
`card_type`	string	Card type (e.g. `DEBIT`, `CREDIT`)
`approval_code`	string	Issuer-returned authorization code
`response_code`	string	Gateway response code. `00` = approved
`switch_response_code`	string	Switch-level response code
`display_message`	string	Display message from the processor, if any
`tip_adjusted_count`	integer	Number of tip adjustments made on this transaction
`is_voided`	integer	`1` if voided; `0` otherwise
`is_reversed`	integer	`1` if reversed; `0` otherwise
`is_auth_completed`	integer	`1` if auth has been captured; `0` otherwise
`is_settled`	integer	`1` if settled; `0` if pending settlement
`settled_at`	string	Settlement timestamp (ISO 8601)
`is_offline_approved`	integer	`1` if approved offline; `0` otherwise
`is_partial_approved`	integer	`1` if partially approved; `0` for full approval
`addtl_data_label1`	string	Additional data label 1
`addtl_data_value1`	string	Additional data value 1
`addtl_data_label2`	string	Additional data label 2
`addtl_data_value2`	string	Additional data value 2
`timezone`	string	Timezone of the terminal (e.g. `EST`)
`refunded_count`	integer	Number of refunds issued against this transaction
`processor_name`	string	Name of the payment processor (e.g. `TSYS Sierra`)
`transactions_status`	string	Transaction status (e.g. `Approved`, `Declined`)

Response — 400 (Validation Error)

{
  "status": "FAILED",
  "errors": [
    "Vault customer ID does not exist."
  ]
}

Response fields

Field	Type	Description
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Transaction records returned
`FAILED`	Validation error	Vault customer ID not found

Update Payment Profile

Update the card details of an existing payment profile in the vault.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "payment_id": 97555
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`payment_id`	integer	Identifier of the updated payment profile

Response — 400 (Validation Error)

{
  "status": "FAILED",
  "errors": [
    "Please provide a valid payment profile ID."
  ]
}

Response fields

Field	Type	Description
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profile updated
`FAILED`	Validation error	Payment profile ID is invalid or not found

Map Transaction to Customer Profile

Link an existing transaction to a vault customer profile by creating a payment profile from the transaction's card data.

Response — 201 Created

{
  "code": 201,
  "status": "OK",
  "payment_id": 97558
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`201`)
`status`	string	`OK` on success
`payment_id`	integer	Unique identifier for the payment profile created from the mapped transaction

Response — 400 (Validation Error)

{
  "status": "FAILED",
  "errors": [
    "Reference transaction ID missing"
  ]
}

Response fields

Field	Type	Description
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Transaction mapped and payment profile created
`FAILED`	Validation error	Reference transaction ID was not provided in the request

Update ACH Profile

Update the bank account details of an existing ACH profile in the vault.

Response — 200 OK

{
  "code": 200,
  "status": "SUCCESS",
  "ach_profile_id": "2290"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`SUCCESS` on success
`ach_profile_id`	string	Identifier of the updated ACH profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": "No changes detected. ACH profile already contains the same information"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	string	Error message describing the reason for failure

Note: errors is returned as a plain string for this endpoint, not an array.

Error code reference

`status`	Meaning	Typical cause
`SUCCESS`	Success	ACH profile updated
`FAILED`	Validation error	The submitted data is identical to the existing ACH profile — no changes to apply

Edit Payment Profile

Update the status or metadata of an existing payment profile.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success

Response — 400 (Validation Error)

{
  "status": "FAILED",
  "errors": [
    "data must have required property 'status'"
  ]
}

Response fields

Field	Type	Description
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profile updated
`FAILED`	Validation error	Required field `status` is missing from the request

View Customer Profile

Retrieve the full profile details for a single vault customer, including address information.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success",
  "data": {
    "id": 100867,
    "customer_name": "Melvin",
    "email": "[email protected]",
    "phone": "6129160161",
    "company": "Home Centers",
    "total_card_count": 0,
    "address_details": [
      {
        "address_id": 154246,
        "address_label": "Home",
        "billing_customer_name": "Catherine P. Elliott",
        "billing_street_no": "2629",
        "billing_street_name": "Rocket Drive",
        "billing_unit": "56",
        "billing_zip": "55427",
        "billing_city": "Golden Valley",
        "billing_state": "MN",
        "shipping_customer_name": "Carolina M. Morris",
        "shipping_street_no": "1650",
        "shipping_street_name": "Chicago Avenue",
        "shipping_unit": "56",
        "shipping_zip": "93721",
        "shipping_city": "Fresno",
        "shipping_state": "CA"
      }
    ]
  }
}

Response fields — top level

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success
`data`	object	Customer profile object

`data` — customer profile fields

Field	Type	Description
`id`	integer	Unique vault customer ID
`customer_name`	string	Customer's full name
`email`	string	Customer email address
`phone`	string	Customer phone number
`company`	string	Company name, if provided
`total_card_count`	integer	Number of payment profiles linked to this customer
`address_details`	array	List of saved address records (see below)

`address_details` — address object fields

Field	Type	Description
`address_id`	integer	Unique identifier for this address record
`address_label`	string	Label for the address (e.g. `Home`, `Work`)
`billing_customer_name`	string	Name on the billing address
`billing_street_no`	string	Billing street number
`billing_street_name`	string	Billing street name
`billing_unit`	string	Billing unit or apartment number, if applicable
`billing_zip`	string	Billing ZIP code
`billing_city`	string	Billing city
`billing_state`	string	Billing state (2-letter code)
`shipping_customer_name`	string	Name on the shipping address
`shipping_street_no`	string	Shipping street number
`shipping_street_name`	string	Shipping street name
`shipping_unit`	string	Shipping unit or apartment number, if applicable
`shipping_zip`	string	Shipping ZIP code
`shipping_city`	string	Shipping city
`shipping_state`	string	Shipping state (2-letter code)

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "Customer not exist"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer profile returned
`FAILED`	Validation error	Customer ID does not exist in the vault

Get Payment Profile

Retrieve all card payment profiles linked to a vault customer.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success",
  "data": [
    {
      "payment_id": 97555,
      "masked_pan": "XXXX1111",
      "token": "416B4ED27B1700DFC5769D3B70C36DF3A0C5FFB6",
      "card_type": "D",
      "card_brand": "Visa",
      "cardholder_name": "Sheila Mitch",
      "status": "active"
    }
  ]
}

Response fields — top level

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success
`data`	array	Array of payment profile objects

`data` — payment profile object fields

Field	Type	Description
`payment_id`	integer	Unique identifier for this payment profile
`masked_pan`	string	Masked card number — last 4 digits shown (e.g. `XXXX1111`)
`token`	string	Card token associated with this profile
`card_type`	string	Card type — `D` = Debit, `C` = Credit
`card_brand`	string	Card network (e.g. `Visa`, `Mastercard`)
`cardholder_name`	string	Name on the card
`status`	string	Profile status (e.g. `active`, `inactive`)

Response — 400 (Validation Error)

{
  "status": false,
  "code": "400",
  "message": "Not a valid APP ID or APP Key."
}

Response fields

Field	Type	Description
`status`	boolean	`false` when authentication fails
`code`	string	HTTP status code as a string (`"400"`)
`message`	string	Error message

Note: This error response uses a different shape — status is a boolean false and code is a string rather than an integer. This indicates an authentication error rather than a data validation error.

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profiles returned
`false`	Authentication error	App ID or App Key is invalid

Get ACH Profile

Retrieve all ACH (bank account) profiles linked to a vault customer.

Response — 200 OK

{
  "code": 200,
  "status": "SUCCESS",
  "data": [
    {
      "ach_profile_id": 2290,
      "account_number": "XXXX0510",
      "routing_number": "XXXX0021",
      "payee_name": "John",
      "account_type": "C",
      "entry_class": "Business"
    }
  ]
}

Response fields — top level

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`SUCCESS` on success
`data`	array	Array of ACH profile objects

`data` — ACH profile object fields

Field	Type	Description
`ach_profile_id`	integer	Unique identifier for this ACH profile
`account_number`	string	Masked bank account number — last 4 digits shown (e.g. `XXXX0510`)
`routing_number`	string	Masked bank routing number — last 4 digits shown (e.g. `XXXX0021`)
`payee_name`	string	Name of the account holder
`account_type`	string	Account type — `C` = Checking, `S` = Savings
`entry_class`	string	ACH entry class (e.g. `Business`, `Personal`)

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": "Customer not exist"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	string	Error message describing the reason for failure

Note: errors is returned as a plain string for this endpoint, not an array.

Error code reference

`status`	Meaning	Typical cause
`SUCCESS`	Success	ACH profiles returned
`FAILED`	Validation error	Customer ID does not exist in the vault

Get Customer List

Retrieve a paginated list of vault customer profiles.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success",
  "data": {
    "customers": [
      {
        "vault_id": 100867,
        "customer_name": "Melvin",
        "email": "[email protected]",
        "phone": "6129160161",
        "company": "Home Centers",
        "total_card_count": 0,
        "total_recursive_billing": 0,
        "transaction_count": 0,
        "last_txn_date": null
      }
    ]
  },
  "number_of_records": 1,
  "page_number": 1,
  "total_pages": 61,
  "total_count": 61,
  "page_size": 1
}

Response fields — top level

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success
`data`	object	Contains the `customers` array
`number_of_records`	integer	Number of customer records returned on this page
`page_number`	integer	Current page number
`total_pages`	integer	Total number of pages available
`total_count`	integer	Total number of vault customers
`page_size`	integer	Number of records per page

`data.customers` — customer object fields

Field	Type	Description
`vault_id`	integer	Unique vault customer identifier
`customer_name`	string	Customer's full name
`email`	string	Customer email address
`phone`	string	Customer phone number
`company`	string	Company name, if provided
`total_card_count`	integer	Number of card payment profiles linked to this customer
`total_recursive_billing`	integer	Number of active recurring billing schedules linked to this customer
`transaction_count`	integer	Total number of transactions associated with this customer
`last_txn_date`	string \| null	Date of the most recent transaction; `null` if no transactions on record

Response — 400 (Authentication Error)

{
  "status": false,
  "code": "400",
  "message": "Please provide a valid APP ID or APP Key."
}

Response fields

Field	Type	Description
`status`	boolean	`false` when authentication fails
`code`	string	HTTP status code as a string (`"400"`)
`message`	string	Error message

Note: This error response uses a different shape — status is a boolean false and code is a string. This indicates an authentication error rather than a data validation error.

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer list returned
`false`	Authentication error	App ID or App Key is invalid or not provided

Delete ACH Profile

Remove an ACH profile from a customer vault record.

Response — 200 OK

{
  "code": 200,
  "status": "SUCCESS",
  "ach_profile_id": "2290"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`SUCCESS` on success
`ach_profile_id`	string	Identifier of the deleted ACH profile

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": "ACH profile ID does not exist"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	string	Error message describing the reason for failure

Note: errors is returned as a plain string for this endpoint, not an array.

Error code reference

`status`	Meaning	Typical cause
`SUCCESS`	Success	ACH profile deleted
`FAILED`	Validation error	ACH profile ID not found

Delete Customer Address

Remove a saved address from a customer vault profile.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "Unable to delete the address."
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer address deleted
`FAILED`	Validation error	Address ID not found or address cannot be deleted

Delete Customer Profile

Permanently remove a customer profile and all associated data from the vault.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "Customer not exist"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Customer profile deleted
`FAILED`	Validation error	Customer ID does not exist in the vault

Delete Payment Profile

Remove a card payment profile from a customer vault record.

Response — 200 OK

{
  "code": 200,
  "status": "OK",
  "message": "Success"
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`200`)
`status`	string	`OK` on success
`message`	string	`Success` on success

Response — 400 (Validation Error)

{
  "code": 400,
  "status": "FAILED",
  "errors": [
    "Unable to delete the payment profile"
  ]
}

Response fields

Field	Type	Description
`code`	integer	HTTP status code (`400`)
`status`	string	`FAILED` when the request cannot be processed
`errors`	array	List of validation error messages

Error code reference

`status`	Meaning	Typical cause
`OK`	Success	Payment profile deleted
`FAILED`	Validation error	Payment profile ID not found or cannot be deleted

Add Customer Profile

Response — 201 Created

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Add Payment Profile

Response — 201 Created

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Add ACH Profile

Response — 200 OK

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Add Payment Profile Using Token

Response — 201 Created

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Edit Customer Profile

Response — 200 OK

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Fetch Transaction With Date Range

Response — 200 OK

Response fields — top level

data — transaction object fields

Response — 400 (Validation Error)

Response fields

Error code reference

Update Payment Profile

Response — 200 OK

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Map Transaction to Customer Profile

Response — 201 Created

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Update ACH Profile

Response — 200 OK

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

Edit Payment Profile

Response — 200 OK

Response fields

Response — 400 (Validation Error)

Response fields

Error code reference

View Customer Profile

Response — 200 OK

Response fields — top level

data — customer profile fields

address_details — address object fields

Response — 400 (Validation Error)

Response fields

Error code reference

Get Payment Profile

Response — 200 OK

Response fields — top level

data — payment profile object fields

Response — 400 (Validation Error)

Response fields

Error code reference

Get ACH Profile

Response — 200 OK

Response fields — top level

data — ACH profile object fields

`data` — transaction object fields

`data` — customer profile fields

`address_details` — address object fields

`data` — payment profile object fields

`data` — ACH profile object fields

`data.customers` — customer object fields