Skip to Content
GuidesMarketplaceUpdate User

Update User KYB/KYC

In this guide, you’ll learn how to update a marketplace user’s KYB/KYC. Checkbook’s marketplace is an embedded product, which allows customers to facilitate transactions to, or on behalf of users and customers. You can create your own user interface to collect this information and forward it directly to us. All information is encrypted both in transit and at rest.

Why does Checkbook need this information?

Checkbook needs this information to comply with federal and state regulations, requirements from our partner banks, and maintaining relevant licensure. As we grow, these requirements may change and become more robust as our product offering becomes more complex.

Customer Identification Program (CIP) — Section 326, USA PATRIOT Act

  • Checkbook customers must have written procedures (a CIP) designed to verify the identity of each user opening an account.
  • The CIP must require, at minimum, collecting from the user:
    • Full legal name
    • Date of birth (for individuals)
    • Address
    • An identification number (such as Social Security Number, Passport Number, etc.)
  • Record keeping: retain identifying information, documentation used for verification, results of any discrepancy resolution. Checkbook must keep records for five years after the account is closed (or after verification record is made) depending on type.
  • FinCEN frequently issues guidance / FAQs clarifying thresholds, beneficial ownership requirements, definitions, how to handle changes, etc.

Checkbook’s Minimum Required Fields for KYB/KYC

Individual Senders

  • First and Last Name
  • Social Security Number or Passport Number
  • Date of Birth
  • Address

Individual Recipients

  • Phone number

Business Senders

  • Tax id
  • Business name
  • Website (or catalog)
  • Business address
  • Business phone number
  • Beneficial Owner (>25% or an officer of the company):
    • First and Last Name
    • Social Security Number or Passport Number
    • Date of Birth
    • Address

Business Recipients

  • Phone number or tax id

Sample Payloads

Business sender example payload:

curl --request PUT \
  --url https://sandbox.checkbook.io/v3/user \
  --header 'Authorization: USER-PUBLISHABLE-KEY:USER-SECRET-KEY' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user": {
    "business_name": "Checkbook Inc.",
    "dob": "2025-07-31",
    "first_name": "John",
    "last_name": "Smith",
    "phone": "1234567890",
    "ssn": "987654321"
  },
  "merchant": {
    "legal_firstname": "John",
    "legal_lastname": "Smith",
    "address": {
      "city": "San Mateo",
      "country": "US",
      "line_1": "1850 Gateway Drive",
      "line_2": "UNIT 125",
      "state": "CA",
      "zip": "94404"
    },
    "tax_id": "999999999",
    "website": "https://websitehere.com/",
    "principal_address": {
      "city": "San Mateo",
      "country": "US",
      "line_1": "1 John Smith Drive",
      "line_2": "APT 11",
      "state": "CA",
      "zip": "94404"
    }
  }
}'

Individual sender example payload:

curl --request POST \
  --url https://sandbox.checkbook.io/v3/user \
  --header 'Authorization: USER-PUBLISHABLE-KEY:USER-SECRET-KEY' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user": {
    "dob": "2025-07-31",
    "first_name": "John",
    "last_name": "Smith",
    "phone": "1234567890",
    "ssn": "987654321"
  },
  "merchant": {
    "principal_address": {
      "city": "San Mateo",
      "country": "US",
      "line_1": "1850 Gateway Drive",
      "line_2": "UNIT 125",
      "state": "CA",
      "zip": "94404"
    }
  }
}'

For recipients, we only need a phone number or tax id.

curl --request POST \
  --url https://sandbox.checkbook.io/v3/user \
  --header 'Authorization: USER-PUBLISHABLE-KEY:USER-SECRET-KEY' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user": {
    "phone": "1234567890"
  },
  "merchant": {
    "tax_id": "999999999"
  }
}'

In the scenarios where the information provided doesn’t adhere to our requirements (such as phone number doesn’t fit), please contact the support team for the best way to handle your use case.

Last updated on