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, SpherePay automatically processes the verification and moves the profile to
pending. - 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 by the integrator or customer. Once all actionable requirements are complete, SpherePay processes the verification automatically — no submit call is needed.
Verification Profile Fields
Here's a brief explanation on each of the items in the verification profile.
| Item | Action required |
|---|---|
| email_address | Provide an email address when creating or updating the customer. |
| phone_number | Provide a phone number when creating or updating the customer. |
| operating_address | Provide an operating address when creating or updating the customer. |
| registered_address | Provide a registered address when creating or updating the customer. |
| legal_name | Provide a legal name when creating or updating the customer. |
| trade_name | Provide a trade name when creating or updating the customer. |
| entity_type | Provide an entity type when creating or updating the customer. |
| entity_type_description | Provide an entity type description when creating or updating the customer. |
| description | Provide a business description when creating or updating the customer. |
| naics_code | Provide a NAICS code when creating or updating the customer. |
| website | Provide a website when creating or updating the customer. |
| incorporated_on | Provide the date of incorporation when creating or updating the customer. |
| identification_number | Provide an identification number when creating or updating the customer. See Business Identification Types by Country for accepted types. |
| estimated_annual_revenue | Provide an estimated annual revenue when creating or updating the customer. |
| expected_monthly_payments | Provide expected monthly payments when creating or updating the customer. |
| account_purpose | Provide an account purpose when creating or updating the customer. |
| account_purpose_description | Provide an account purpose description when creating or updating the customer. |
| source_of_funds | Provide a source of funds when creating or updating the customer. |
| source_of_funds_description | Provide a source of funds description when creating or updating the customer. |
| is_dao | Indicate whether the business is dealing with DAOs when creating or updating the customer. |
| regulated_activities | Indicate whether the business is involved in regulated activities when creating or updating the customer. |
| regulated_activities_description | Provide a regulated activities description when creating or updating the customer. |
| participates_in_regulated_financial_activity | Indicate whether the business participates in regulated financial activity when creating or updating the customer. |
| regulated_financial_activity_description | Provide a regulated financial activity description when creating or updating the customer. |
| money_services_description | Provide a money services description when creating or updating the customer. |
| compliance_screening_explanation | Provide a compliance screening explanation when creating or updating the customer. |
| operates_in_prohibited_countries | Indicate whether the business operates in prohibited countries when creating or updating the customer. |
| business_representatives | Register and verify all business representatives (UBOs) via Register Business Representative before the business can be submitted for verification. |
| incorporation_cert_document | Upload an incorporation certificate document via Upload Document. |
| shareholder_registry_document | Upload a shareholder registry document via Upload Document. |
| proof_of_address_document | Upload a proof of address document via Upload Document. |
| terms_of_service | Accept the terms of service via the link returned by Generate TOS Link. Enhanced requirement — only required for some integrations. |
| master_service_agreement | Sign the merchant service agreement via the hosted form presented after TOS acceptance. Enhanced requirement — only required for some integrations. |
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 customerId.
Last updated on