Move your organisation to the new personal USD flow.
Rollout is phased by organisation. Agree your enablement date, initial request volume, monitoring period, and support contacts with Graph. Existing accounts and historical pending requests are not automatically migrated.
1. Prepare and test
Keep the existing API URL, authentication, person IDs, and POST /bank_account endpoint. Graph enables the flow for your organisation; there is no provider parameter or dashboard switch to select it.
Deploy support for:
- Pending accounts until
account.createdoraccount.issuance.failedconfirms the outcome. - Standard RFIs, hosted actions, and expired-link refresh.
- Shared person inquiries with
account_id: null. - Duplicate, delayed, or missed events, reconciled through fetch/list APIs.
Follow Issuing a USD Account and RFI handling. Keep support for existing accounts; not every pending account has an RFI.
Complete the sandbox checks for rfi_success, rfi_rejected, and rfi_expired_link. Verify uncertain submissions through response history and uncertain account creation through account listing. Sandbox success does not establish live eligibility or validate deposit processing.
2. Enable your organisation
Share the test results with Graph and confirm the integration is deployed. After Graph confirms enablement, send eligible new personal USD requests using your live key. Omit sandbox_scenario and sandbox_options.
Reuse eligible person records. Start with the agreed volume and review initial outcomes before increasing it. Show only the bank details and rails returned for active accounts, and confirm live funding readiness with Graph before inviting deposits.
Existing and pending accounts
| Account/request | After enablement |
|---|---|
| Existing active account | Keeps its current arrangements and bank details. |
| Already pending | Keeps its existing route and account ID. |
| Eligible new live personal USD request | Uses the new flow and may need RFIs. |
| Request already in the new flow | Keeps that route even if new routing is paused. |
| Business, other-currency, or ordinary test request | Keeps its existing route. |
Do not close or recreate accounts to force migration. Active or pending USD accounts can prevent another request for the holder; contact Graph about unresolved cases. Historical account replacement requires a separate agreed process.
3. Monitor and handle issues
Track pending-account age, outstanding RFIs, final outcomes, and webhook errors during the agreed monitoring period.
If RFI or webhook handling fails, pause new requests and contact Graph. Keep existing-account support and webhook processing running: a pause does not cancel pending work or undo issued accounts.
Include account/inquiry IDs, event IDs where available, environment, timestamps with timezone, and HTTP status/error in an escalation. A timeout or prolonged pending state is not a final rejection. Reconcile outstanding work with Graph before resuming or increasing request volume.