Onboarding Overview

This page is the starting point for partners integrating 1Money's business onboarding — covering the core concepts, the end-to-end flow, and both the programmatic and self-onboarding paths.

Definitions

• Partner: a business that integrates with 1Money's APIs to offer financial services to its own customers.
• Customer: the end user — individual or business — onboarded into 1Money through a partner's integration.
• Main-Account: the top-level 1Money account held by a partner, under which all sub-accounts are created and managed. Don't have a 1Money Main Account yet? Signup here.
• Sub-Account: a 1Money account created under a Main-Account to hold funds and transact on behalf of a customer.

Onboarding Flow

1. Terms of Service Acceptance — the customer being onboarded accepts 1Money's Terms of Service through one of the acceptance flows.
2. Business Account Initiation — the partner initiates the business sub-account via the Initiate Business Account API, passing either the signature_id or signed_at captured in step 1.
3. Document Upload — the partner uploads all required documents returned in step 2, using the Upload Company Document API for the business and the Upload Controller Document API for each controller.
4. Submission for Review — once all documents from step 3 are uploaded, the partner submits the business sub-account for review, using the Business Account Submission API.
5. Account Status Updates — throughout and after the onboarding flow, the partner listens to account webhooks for status changes including approval, rejection, and RFI issuance.
6. Request for Information (RFI) — if additional documents are required during screening or compliance review, 1Money notifies the partner via email and/or RFI webhooks. See RFI Handling for details.

Terms of Service Acceptance

Before sub-accounts can be initiated, the customer being onboarded must have accepted 1Money's Terms of Service (ToS). Acceptance can be captured through one of two flows:

1. 1Money-Hosted ToS Signature Page: 1Money hosts the Terms of Service page and captures customer acceptance. The partner generates the URL via the Create Terms of Service API, shares it with the customer, and references the resulting signature_id in terms[].signature_id with terms[].type = BUSINESS_ONBOARDING when calling the Initiate Business Account API.
2. Partner-Hosted ToS Signature Page: the partner displays 1Money's Terms of Service in their own UI and captures the acceptance timestamp directly from the customer, passing the signed_at timestamp with the applicable terms[].type when calling the Initiate Business Account API. Requires 1Money compliance approval.

Request for Information Handling (RFI)

During screening and compliance review, 1Money may request additional or updated information before the business sub-account can be approved. RFIs are handled through an automated API-driven flow:

1. Notification — when additional or updated information is required, 1Money automatically notifies the partner via email and/or the account.business.rfi webhook.
2. Response — depending on the nature of the RFI, the partner responds programmatically using the Update Business Account API for data corrections and/or the Document Upload APIs for additional documents.
3. Re-submission — once the amendments are complete, the partner re-submits the business sub-account for review via the Business Account Submission API.

Customer Self-Onboarding via 1Money-Hosted Journey

As an alternative to driving the onboarding flow via API, partners can let 1Money handle the onboarding UI end-to-end. In this approach, the partner's main integration steps are to generate a 1Money-hosted URL via the Create Self-Onboarding URL API, share it with the customer, and listen to account onboarding webhooks to track the sub-account's status. The customer completes the onboarding journey directly through 1Money — removing the need to build an onboarding UI or integrate with the underlying onboarding APIs.

Multi-Level Account Hierarchy

Sub-accounts are not limited to sitting directly under the Main-Account. An approved business sub-account can itself be the parent of further sub-accounts, letting partners model multi-level customer hierarchies. When creating a sub-account, the account it is created under is chosen via the account_id path parameter of the Initiate Business Account API — this may be the Main-Account or any approved business sub-account.