Who needs to complete this flow
This full connected account onboarding flow applies to platforms using PIK’s Global Accounts product — where you create and manage financial accounts on behalf of your customers. If your business is onboarding as a PIK merchant to use Payment Links only, a separate merchant onboarding flow applies. Contact your PIK account manager for the merchant-specific onboarding path, which has different verification requirements.Overview
Step 1 — Create the connected account. Register the customer in PIK. This generates a connected account ID. Step 2 — Submit identity information. Provide KYC details for individuals or KYB details for businesses. Step 3 — Wait for verification. PIK’s compliance team reviews the submission. Step 4 — Activate capabilities. Once approved, enable inbound payments, FX conversion, or payouts. Step 5 — Issue a Virtual Account Number. Give the customer a dedicated BSB and account number for receiving AUD.Step 1 — Create the connected account
Call POST /api/v1/accounts with customer_type (individual or business), email, country, and your own internal reference_id. The response returns a connected_account_id. Store this — it is the x-on-behalf-of value for all future calls.Step 2 — Submit identity information
For individual customers (KYC)
Required data fields:- first_name and last_name — Legal name as it appears on the ID document.
- date_of_birth — Format YYYY-MM-DD.
- nationality — ISO 2-letter country code.
- id_type — The type of government-issued ID being provided.
- id_number — The document number.
- address — Full residential address: line1, city, state, postcode, country.
- passport — Recommended. Accepted for all nationalities.
- drivers_licence — Accepted for Australian licence holders.
- national_id — Accepted for nationalities where a national ID card is the primary government document.
connected: inline export/kyc/documents with the document image as a multipart upload. Supported formats: JPEG, PNG, PDF. Maximum file size: 10MB per document.
Liveness check: PIK requires a liveness verification for individual customers. After document upload, call POST /api/v1/accounts/connected-account-idconnected: inline export/kyc/liveness to initiate the liveness check session. The response returns a liveness_url — redirect the customer to this URL to complete a brief selfie verification in their browser or app. PIK uses this to confirm the person submitting the documents is the same person in the ID photo.
For business customers (KYB)
Required data fields:- legal_name — Full registered legal name of the business.
- registration_number — Company registration or ABN/ACN number.
- country_of_incorporation — ISO 2-letter country code.
- business_type — One of: company, partnership, sole_trader, trust.
- registered_address — Full address: line1, city, state, postcode, country.
- beneficial_owners — Array of individuals who own 25% or more of the business. Each entry requires the same fields as individual KYC above.
connected: inline export/kyb/documents. For trusts, upload the trust deed in addition to registration documents.
Step 3 — Check verification status
Poll GET /api/v1/accounts/connected-account-idconnected: inline export or set up a webhook on account.verification_status_updated.
Verification statuses:
- pending — Submission received, not yet in review.
- in_review — PIK compliance team is actively reviewing. Typical review time is 1 to 2 business days for individuals, 2 to 5 business days for businesses.
- approved — Verified. Capabilities can now be activated.
- rejected — Verification failed. The rejection_reason field explains why. Common reasons: expired document, document image unreadable, name mismatch, address mismatch.
- more_info_required — PIK needs additional information before review can continue.
Handling more_info_required
When status is more_info_required, check the required_info field in the account response. This field contains a list of specific items PIK needs, such as:- additional_document — A secondary ID or supporting document is needed.
- address_proof — A utility bill or bank statement confirming the residential address.
- beneficial_owner_info — Missing or incomplete information for a beneficial owner.
- document_quality — The submitted document image was unclear. A new upload is required.
connected: inline export/resubmit to notify PIK the additional information is ready for review.
Step 4 — Activate capabilities
Once verification_status is approved, call POST /api/v1/accounts/connected-account-idconnected: inline export/capabilities.
Available capabilities:
- inbound_payments — Customer can receive AUD via VAN and USDT/USDC via Solana address.
- fx_conversion — Customer can convert between supported currencies including on-ramp and off-ramp.
- outbound_payouts — Customer can send funds to external bank accounts or crypto wallets.
Step 5 — Issue a Virtual Account Number
Once inbound_payments is activated, call POST /api/v1/accounts/connected-account-idconnected: inline export/virtual-account. PIK returns the BSB and account number immediately. The customer can start receiving AUD bank transfers as soon as the VAN is issued.