Onboarding Joint Tenancy

Effortless onboarding with built-in KYC and underwriting.

Use the PCE APIs to onboard Joint Tenancy customers.

Joint Tenancy accounts offer shared ownership of a single consumer banking account, allowing two individuals to manage funds together. This setup brings flexibility and convenience to users who wish to handle their finances collaboratively — whether as partners, family members, or caregivers.

Each joint account holder has equal access to the account. Both individuals can deposit, withdraw, and oversee funds independently, while also sharing full legal rights and responsibilities tied to the account.

This feature is ideal for scenarios such as couples managing shared expenses, adult children assisting elderly parents, or parents guiding their children’s savings. With Joint Tenancy, account management becomes simpler, more transparent, and tailored to real-life needs.

  • Primary Owner: The individual who opens the joint account and receives all account-related communications.
  • Co-Owner: An additional account holder added by the primary owner, with equal access and shared legal responsibility.

Steps to Onboard Joint Tenancy customers

The details you provide during entity creation are used to verify the associated account holder.

Request Parameters

Parameter

Description

owners.externalId String Optional

External reference id. Supported maximum of 45 characters.

owners.firstName String Required

First name of the owner. Supported maximum of 45 characters including: A-Z a-z 0-9 _ , . & ( ) / \ " ' á é í ó ú ü ñ Ñ ü Ã Í Ö ö Š š

owners.lastName String Required

Last name of the owner. Supported maximum of 45 characters including: A-Z a-z 0-9 _ , . & ( ) / \ " ' á é í ó ú ü ñ Ñ ü Ã Í Ö ö Š š

owners.middleName String Optional

Middle name of the owner. Supported maximum of 20 characters including: A-Z a-z 0-9 _ , . & ( ) / \ " ' á é í ó ú ü ñ Ñ ü Ã Í Ö ö Š š

owners.isPrimary String Boolean

Whether user is the primary owner.

Possible Values: TRUE, FALSE

owners.ssn String Optional

Owner's Social Security Number in format XXX-XXX-XXXX. It is required for the customer’s background verification.

owners.taxIdentification Object Optional

Owner's Taxpayer Identification.

Possible values: ITIN

owners.dob String Optional

Owner's date of birth in dd/mm/yy format.

owners.mailingAddress String Optional

Owner's mailing address. Can be more than one and any one of these addresses can be set as a Payor Address.

owners.homePhone String Optional

Owner's home contact number in Numeric (XXX-XXX-XXXX) format.

owners.mobilePhone String Optional

Owner's mobile contact number in Numeric (XXX-XXX-XXXX) format.

owners.workPhone String Optional

Owner's work contact number in Numeric (XXX-XXX-XXXX) format.

owners.email String Optional

Owner's email address in [email protected] format.

owners.secondaryIdentification String Optional

Provide additional identification proof for the owner.

Possible Values: DRIVER_LICENSE, PASSPORT, ALIEN_REGISTRATION_CARD

Response Parameters

ParameterDescription
owners.verificationThe customer’s OFAC and CIP verification statuses, their reasons and date on which the status was updated.

Onboarding APIs Summary

Integration ComponentEndpoint / Feature
Submit user infoPOST /customer
Update user infoPOST /customer/id/{id}
Upload documentsPOST /customer/id/{id}/document
Status updatesGET /customers/{id} or Webhook
Track progressverification.status

Testing & Go Live

Use sandbox data to simulate both approval and rejection flows.

Kindly wait for approximately 5 minutes to view the results.

a. OFAC Verification

Use case 1: OFAC Verification Successful

As it is a successful verification scenario, you can add any names except block.

  • For a Joint Tenancy Customer, create a customer with any first & last names except block.

Test Data

Result

Create a Customer:

"type": "JOINT_TENANCY", "owners.firstName": "James",

Get Customer:

"owners.verification.ofacStatus": "VERIFIED", "owners.verification.ofacStatusReason": "Verified",

Use case 2: OFAC Verification Failed

Test Data

Result

Create a Customer:

"type": "JOINT_TENANCY", "owners.firstName": "block",

Get Customer:

"owners.verification.ofacStatus": "REJECTED", "owners.verification.ofacStatusReason": "Rejected",

b. CIP Verification Successful

Use case 1: CIP Verification Successful

As it is a successful verification scenario, you can add any names except block.

  • For an Joint Tenancy Customer, create a customer with any first & last names except block.

Test Data

Result

Create a Customer:

"type": "JOINT_TENANCY", "owners.firstName": "James",

Create an Account:

"isCustomerOwned": true

Get Customer:

"owners.verification.cipStatus": "VERIFIED", "owners.verification.cipStatusReason": "Verified"

Use case 2: CIP Verification Failed

Test Data

Result

Create a Customer:

"type": "JOINT_TENANCY", "owners.firstName": "block",

Create an Account:

"isCustomerOwned": true

Get Customer:

"owners.verification.cipStatus": "REJECTED", "owners.verification.cipStatusReason": "Rejected",

Next Steps

See Also


© 2025 Priority Technology Holdings LLC. All rights reserved.