Wallets & Balances

How PIK wallets work, which currencies support inbound, how to fund non-AUD balances, and how to retrieve and move funds.

Every PIK account has a multi-currency wallet. Each wallet can hold balances in multiple currencies at the same time. This page explains what you can do with each currency and how to manage balances.

Currency Capability Matrix

Currency	Receive Inbound	Hold Balance	FX Convert	On/Off Ramp	Payout
AUD	Yes — via VAN	Yes	Yes	Yes (off-ramp to crypto)	Yes
USDT	Yes — via Solana address	Yes	Yes	Yes (on-ramp to fiat)	Yes
USDC	Yes — via Solana address	Yes	Yes	Yes (on-ramp to fiat)	Yes
USD	No inbound	Yes	Yes	Yes	Yes
HKD	No inbound	Yes	Yes	No	Yes
SGD	No inbound	Yes	Yes	No	Yes

CNY is not supported. PIK is a non-China market platform.

USDT and USDC inbound is Solana network only. TRC-20, ERC-20, and BEP-20 are not supported and will not be credited.

How Wallets Work

A wallet holds balances across multiple currencies simultaneously. Each transaction type affects balances as follows:

• Inbound AUD bank transfer → credits AUD balance
• Inbound USDT on-chain → credits USDT balance
• Inbound USDC on-chain → credits USDC balance
• FX conversion → debits source currency, credits target currency
• Payout → debits the relevant currency balance

Funds never leave PIK custody until a payout is executed to an external bank account or crypto address.

How to Fund a USD, HKD, or SGD Balance

USD, HKD, and SGD have no inbound receiving mechanism. To get a balance in these currencies, use one of two paths:

Path 1 — Receive AUD then convert:

Receive AUD via VAN → FX convert AUD to USD / HKD / SGD

Path 2 — Receive crypto then convert:

Receive USDT or USDC via Solana address → FX convert to USD / HKD / SGD

See FX Conversion for instructions on converting between currencies.

On-Ramp and Off-Ramp

PIK supports crypto-to-fiat and fiat-to-crypto conversion via the FX Conversion engine.

Direction	What It Does	Example
On-ramp	Convert USDT or USDC to AUD or USD	Receive USDT from a customer, hold or pay out in AUD
Off-ramp	Convert AUD or USD to USDT or USDC	Receive AUD, convert to USDT for cross-border withdrawal

Both use the same FX Conversion API. See On-ramp and Off-ramp for a dedicated guide.

Third-Party Fund-In

Any third party can send funds to a connected account’s VAN or Solana address without needing a PIK account. This supports use cases where your customers receive payments from their own clients or employers. See Receiving Funds for details.

Retrieve Wallet Balances

GET /api/v1/accounts/{connected-account-id}/wallet/balances
Authorization: Bearer YOUR_PLATFORM_API_KEY
x-on-behalf-of: {connected-account-id}

Response fields per currency:

Field	Description
currency	Currency code, e.g. AUD, USDT, USDC
available	Funds available for conversion or payout right now
pending	Inbound funds received but not yet settled

Move Funds Between Wallets

POST /api/v1/transfers

Specify the source (from_account_id or “platform”), destination (to_account_id or “platform”), currency, amount, and optional reference.

Transfers cannot exceed the available balance of the source wallet. Attempting to transfer more than the available balance returns a 402 INSUFFICIENT_BALANCE error.

---

---

PAGE 5 — Receiving Funds

File: receiving-funds-1.mdx Action: REPLACE ALL

---

title: “Receiving Funds” description: “How connected accounts receive inbound AUD, USDT, and USDC — and how third-party senders can fund an account without a PIK account.”

---

Once a connected account is verified and the inbound_payments capability is activated, PIK issues it two types of receiving details: a Virtual Account Number for AUD and a Solana wallet address for USDT and USDC. Any third party can send to these details — no PIK account required.

USD, HKD, and SGD have no inbound receiving mechanism. To fund these balances, receive AUD or stablecoins and use FX Conversion to convert.

Receiving AUD via Virtual Account Number

PIK issues each connected account a unique Australian BSB and account number. Anyone with an Australian bank account can transfer AUD to it directly.

POST /api/v1/accounts/{connected-account-id}/virtual-account

PIK returns the BSB and account number immediately after the call.

Property	Detail
Unique per account?	Yes — no two accounts share the same number
Who can send?	Anyone with an Australian bank account — no PIK account required
Third-party senders?	Yes — fully supported
Settlement time	1 business day; NPP transfers may be faster

Best practice: Instruct senders to include a payment reference in their transfer description. PIK records this in the transaction data for reconciliation.

Receiving USDT and USDC via Solana Address

PIK assigns each connected account dedicated Solana wallet addresses for USDT and USDC.

GET /api/v1/accounts/{connected-account-id}/receiving-details

Property	Detail
Unique per account?	Yes — never shared between accounts
Who can send?	Any Solana-compatible wallet — no PIK account required
Third-party senders?	Yes — fully supported
Minimum inbound	1 USDT or 1 USDC
Settlement time	Minutes once on-chain transaction reaches finality

Solana network only. USDT and USDC sent on Tron (TRC-20), Ethereum (ERC-20), or BNB Chain (BEP-20) will NOT be credited and cannot be recovered. This must be communicated clearly to all senders before they transfer. Sending on the wrong network results in permanent loss of funds.

Third-Party Fund-In

PIK explicitly supports third-party fund-in. Connected account customers can share their VAN or Solana address with their own clients, employers, or counterparties and receive funds directly into their PIK wallet. The sender has no relationship with PIK.

Example use case: A freelancer on your platform shares their PIK-issued BSB and account number with their client. The client transfers AUD from their own bank. PIK credits the freelancer’s connected account automatically.

Settlement Timing Summary

Currency	Method	Typical Settlement Time
AUD	Virtual Account Number	1 business day; NPP may be faster
USDT	Solana address	Minutes after on-chain confirmation
USDC	Solana address	Minutes after on-chain confirmation