key updates:

🆕 Update 1: Individual Onboarding documentation is now available

We added a dedicated Individual Onboarding Overview for partners integrating individual KYC flows through the API.

The new guide explains the full lifecycle for individual customers:

Terms of Service acceptance
Application creation
Required profile data
Document upload requirements
KYC2 submission
Action-required recovery
Optional Tier3 / EDD upgrade
Webhook-driven status tracking

Start here:

Individual Onboarding Overview

🆕 Update 2: Individual KYC webhook documentation is now more complete

We expanded the Individual Onboarding Webhooks reference with a full event catalog and detailed payload examples for all individual KYC events.

The documented events now include:

kyc.submitted
kyc.action_required
kyc.under_review
kyc.approved
kyc.rejected
kyc.upgrade_started
kyc.upgrade_action_required
kyc.upgrade_under_review
kyc.upgrade_approved
kyc.upgrade_rejected

The webhook guide also clarifies:

The shared webhook envelope
resource.idempotency_key vs. data.client_idempotency_key
Receiver-side deduplication
Out-of-order delivery handling
KYC2 action-required vs. EDD action-required routing

See:

Individual Onboarding Webhooks

🆕 Update 3: Individual onboarding request structure is clearer

The individual application payload is now organized around clearer business sections:

terms
contact
person
residential_address
document
due_diligence

Notable naming updates:

reference_id is now documented as external_customer_id
Email and phone are grouped under contact
Address fields are grouped under residential_address
Tax information is captured as person.tin and person.tax_residence_country

This structure is intended to make partner integrations easier to understand and keep personally identifiable data grouped by purpose.

🆕 Update 4: Individual TIN handling is simplified

Partners no longer need to send country-specific tax ID type labels such as SSN, CPF, RFC, or PESEL.

Instead, send:

person.tin
person.tax_residence_country

1Money stores the value as the customer's tax ID and uses tax_residence_country for downstream verification and vendor routing.

At this stage, TIN validation is intentionally lightweight:

Must be present where required by the API schema
Must not be a masked placeholder
Must be no more than 64 characters

Country-specific format validation may be tightened in a later version.

🆕 Update 5: Individual onboarding country controls are documented

For individual onboarding, the following fields are independently checked against the supported operating country list:

residential_address.country
document.country
person.tax_residence_country

These fields do not need to match each other, and they do not need to match person.nationality.

Supported operating countries in this release:

US, BR, MX, CO, AR, UY, PY, CL, BO, PE, EC, IE, CN, AE, BE, CY, EG, ES, FR, HK, LV, PH, PL, TH, TW, VN

Unsupported operating countries return 403 customer_region_not_supported.

🆕 Update 6: Individual Tier3 / EDD flow is documented

We added clearer guidance for Tier3 / EDD upgrades.

To request a Tier3 upgrade for an approved Tier2 individual customer:

PATCH the required due_diligence fields.
Upload POA using the document upload endpoint.
Call POST /upgrade.
Wait for the EDD webhook outcome.

Possible EDD outcomes include:

kyc.upgrade_approved
kyc.upgrade_rejected
kyc.upgrade_under_review
kyc.upgrade_action_required

If KYC2 risk requires EDD before access, the platform sends kyc.upgrade_action_required with:

kyc_status=ACTION_REQUIRED
edd_status=REQUIRED

Partners should then provide EDD data, upload POA, and call POST /upgrade.

✅ Update 7: POA upload behavior is clarified

Proof of Address (POA) upload is now documented with explicit state rules.

POA upload is accepted when:

EDD is already required
The customer is Tier2-approved and the partner wants to start Tier3
The application is still in DRAFT, where POA is stored for later EDD use

POA upload is rejected while KYC2 is processing or action-required unless EDD is already required.

Each uploaded document must decode to 4 MB or less.

🆕 Update 8: New occupation value added

We added a new occupation enum value:

unemp_no_work_5y

This represents:

Unemployed, with no work experience in the last 5 years or earlier or never worked

This occupation is treated as high risk in the KYC risk model.

Improved

Individual onboarding endpoint descriptions are shorter and point to the new overview guide for full workflow details.
The general webhook overview now links to individual onboarding webhook semantics.
Individual application responses are documented as metadata-only responses and do not echo raw PII.
State transition and allowed-action guidance is consolidated in the Individual Onboarding Overview.

Migration Notes

Partners integrating individual onboarding should review:

The updated create/update payload structure
The new person.tin and person.tax_residence_country fields
The supported operating country list
The documented KYC2 and EDD webhook events
The Tier3 / EDD upgrade sequence

Business onboarding, payments, deposits, withdrawals, and conversion APIs are not materially changed by this release.

Changelog