Verification Profile
Reference for verification profile statuses, criteria arrays, and required fields for business customer onboarding.
Introduction
A verification profile is a record of the requirements SpherePay needs to approve a business customer for transfers. It is returned as part of the verificationProfiles array when you call Get Customer.
Most integrations will see a single profile in the verificationProfiles array. A business customer is ready to transfer when that profile's status reaches approved. Additional profiles may appear if your integration requires extended capabilities — if you see unexpected profile names, contact your SpherePay representative.
Multiple verification profiles
Different profiles unlock different transfer capabilities. Contact your SpherePay representative to understand which profile applies to your integration.
Verification Status
The status field on a verification profile has four possible values:
| Status | Description | Can Initiate Transfers? |
|---|---|---|
incomplete | The verification profile is incomplete. The business customer has not yet completed all the verification requirements. This is the initial state of a verification profile. | No |
pending | The verification profile is pending. The business customer has completed all the verification requirements and is waiting for approval. This is the state when the verification profile is being reviewed by SpherePay. | No |
approved | The verification profile is approved. The business customer has completed all the verification requirements and is approved. This is the state when the verification profile is approved by SpherePay. | Yes |
rejected | The verification profile is rejected. The business customer has not completed all the verification requirements and is rejected. This is the state when the verification profile is rejected by SpherePay. | No |
Status Lifecycle
A verification profile moves through states in the following order:
incomplete → pending → approved
↘
rejected- A business customer starts as
incomplete. Thecriteria.requiredarray lists all outstanding requirements. - Once all requirements are fulfilled and
submit-verificationis called, the profile moves topending. - SpherePay completes the review and transitions the profile to either
approvedorrejected.
Verification Criteria
Each verification profile contains a criteria object with four arrays that describe the current state of each requirement:
| Criteria Array | Description |
|---|---|
complete | Requirements that have been fulfilled. No further action needed. |
pending | Requirements currently being processed by SpherePay. The customer must wait. |
required | Requirements that must be completed before the profile can be approved. The customer must act on these items. |
errors | Requirements with validation errors. The customer must correct these before resubmitting. |
To submit for approval, all items in required must be resolved. Once only identity_verification and kyb_a_approval remain in required (these are fulfilled by SpherePay after submission), the customer can call the Submit Verification endpoint.
Verification Profile Fields
Here's a brief explanation on each of the items in the verification profile.
| Item | Action required |
|---|---|
| terms_of_service | Customer is required to accept the terms of service by clicking the link provided in the response of Generate TOS Link Endpoint |
| master_service_agreement | Customer is required to accept the master service agreement by clicking the link provided in the response of Generate MSA Link Endpoint |
| email_address | Customer is required to provide an email address upon customer creation or update. |
| phone_number | Customer is required to provide a phone number upon customer creation or update. |
| operating_address | Customer is required to provide an operating address upon customer creation or update. |
| registered_address | Customer is required to provide a registered address upon customer creation or update. |
| legal_name | Customer is required to provide a legal name upon customer creation or update. |
| trade_name | Customer is required to provide a trade name upon customer creation or update. |
| entity_type | Customer is required to provide an entity type upon customer creation or update. |
| entity_type_description | Customer is required to provide an entity type description upon customer creation or update. |
| description | Customer is required to provide a description upon customer creation or update. |
| naics_code | Customer is required to provide a NAICS code upon customer creation or update. |
| website | Customer is required to provide a website upon customer creation or update. |
| incorporated_on | Customer is required to provide the date of incorporation upon customer creation or update. |
| identification_number | Customer is required to provide an identification number upon customer creation or update. For the complete list of accepted identification numbers, please refer to the Business Identification Types by Country guide. |
| estimated_annual_revenue | Customer is required to provide an estimated annual revenue upon customer creation or update. |
| expected_monthly_payments | Customer is required to provide an expected monthly payments upon customer creation or update. |
| account_purpose | Customer is required to provide an account purpose upon customer creation or update. |
| account_purpose_description | Customer is required to provide an account purpose description upon customer creation or update. |
| source_of_funds | Customer is required to provide a source of funds upon customer creation or update. |
| source_of_funds_description | Customer is required to provide a source of funds description upon customer creation or update. |
| is_dao | Customer is required to provide information if the customer is dealing with DAOs upon customer creation or update. |
| regulated_activities | Customer is required to provide information if the customer is involved in regulated activities upon customer creation or update. |
| regulated_activities_description | Customer is required to provide regulated activities description upon customer creation or update. |
| participates_in_regulated_financial_activity | Customer is required to provide information if the customer is participating in regulated financial activity upon customer creation or update. |
| regulated_financial_activity_description | Customer is required to provide regulated financial activity description upon customer creation or update. |
| money_services_description | Customer is required to provide money services description upon customer creation or update. |
| compliance_screening_explanation | Customer is required to provide compliance screening explanation upon customer creation or update. |
| operates_in_prohibited_countries | Customer is required to provide information if the customer is operating in prohibited countries upon customer creation or update. |
| business_representatives | Customer is required to register and verify all business representatives (UBOs) before the business customer can be submitted for verification. |
| incorporation_cert_document | Customer is required to upload an incorporation certificate document for verification via Upload Document Endpoint |
| shareholder_registry_document | Customer is required to upload a shareholder registry document for verification via Upload Document Endpoint |
| directors_registry_document | Customer is required to upload a directors registry document for verification via Upload Document Endpoint |
| proof_of_address_document | Customer is required to upload a proof of address document for verification via Upload Document Endpoint |
Handling Rejected Customers
A rejected status means the verification could not be approved based on the submitted information. Business customers with a rejected profile cannot initiate or receive transfers.
If a business customer is incorrectly rejected or requires re-review, contact support@spherepay.co with the customer_id.
Last updated on