Onboarding Overview

This page is the starting point for partners integrating 1Money's individual account onboarding — covering It covers the core concepts, account lifecycle, document upload, review states, webhooks, and transaction limits.

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 individual customer accounts are created and managed. Don't have a 1Money Main Account yet? Signup here.
• Individual Sub-Account: a natural person account created for one individual customer. The account tracks onboarding status, documents, issues, and transaction limits after approval.

Onboarding Flow

1. Terms of Service Acceptance — the individual being onboarded accepts 1Money's Terms of Service through a hosted or partner-hosted flow.
2. Individual Account Initiation — the partner initiates the individual account via Initiate Individual Account, passing either the signature_id or signed_at captured in step 1.
3. Document Upload — the partner uploads each required document listed in the account's documents array using Upload Individual Document.
4. Submission for Review — once all required data and documents are complete, the partner submits the individual account through Submit Individual Account.
5. Account Status Updates — throughout and after the onboarding flow, the partner listens to individual 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.
7. Account Transaction Limits — after approval, partners can call Get Individual Account Limits to retrieve the account's transaction limits.

Terms of Service Acceptance

Before an individual account can be submitted, the customer must accept 1Money's Terms of Service. Acceptance can be captured through one of two flows:

1. 1Money-hosted TOS flow: create a hosted signature with Create Terms of Service URL, using type=INDIVIDUAL_ONBOARDING. Redirect the customer to the returned URL, then pass the returned signature_id in terms[].signature_id when creating the individual.
2. Partner-hosted TOS flow: partners approved by 1Money may display the Terms of Service in their own UI and pass terms[].signed_at with terms[].type=INDIVIDUAL_ONBOARDING. This flow requires 1Money compliance approval.

Request for Information Handling (RFI)

During screening and compliance review, 1Money may request additional or updated information before the individual 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.individual.rfi webhook.
2. Response — depending on the nature of the RFI, the partner responds programmatically using the Update Individual Account API for data corrections and/or the Individual Document Upload API for additional documents.
3. Re-submission — once the amendments are complete, the partner re-submits the business sub-account for review via the Individual Account Submission API.

Country Controls

Country fields must use supported ISO 3166-1 alpha-2 country codes. Unsupported regions or blocked jurisdictions may be rejected synchronously or routed into manual review depending on the field and compliance rule in effect.

For US-located inputs, state fields must use valid 2-letter US state codes. State support may differ by account type and compliance coverage.

Document Requirements

Use the documents array from Initiate Individual Account or Get Individual Account as the upload checklist. Required uploads depend on the customer's identity document and compliance review path.

Upload files with Upload Individual Document. The endpoint accepts binary file contents and requires Content-Type and Content-Disposition headers.

Status Values

Individual onboarding status is tracked in the account's status field:

Document status is tracked per item in the documents array:

State and Allowed Actions

Use this table to decide the next API call from the current status.

Account Limits Review

Approved individual accounts receive pre-established transaction limits. Partners can call Review Individual Account Limits to request a limits increase for an approved account.

The eligibility criteria and required inputs are documented on the Review Individual Account Limits endpoint page. Limits review requires manual approval by 1Money. When the request is approved and the account's limits are updated, 1Money sends the account.individual.reviewed webhook.

Use Get Individual Account Limits to retrieve the account's current limits at any time.

Webhooks

Individual onboarding is asynchronous. Subscribe to account.individual.* webhook events and use data.account_id to correlate events back to the individual account.

See Individual Onboarding Webhooks for the event catalog, payload shape, deduplication keys, and action-required routing.

Sandbox Testing

In Sandbox, use Simulate Account Review to test approval, rejection, manual review, and action-required flows.

Idempotency

Initiate Individual Account requires an Idempotency-Key. Reuse the same key only for safe retries of the same logical create request.

Other mutating endpoints document their idempotency behavior on the endpoint page. Use unique keys for distinct logical operations.

Multi-Level Sub-Accounts

Individual sub-accounts are not limited to sitting directly under the Main-Account. An approved business sub-account can itself be the parent of further individual sub-accounts. When creating a sub-account, the account it is created under is chosen via the account_id path parameter of the Initiate Individual Account API — this may be the Main-Account or any approved business sub-account.