Changelog

What's new — Sweep of doc corrections to align the published reference with actual API behavior. No API behavior changed; only the documentation. Highlights:

What's new — A second virtual-account product, usa-virtual-accounts-act, is now generally available alongside usa-virtual-accounts (Portage). ACT requires no government-ID photos at user creation; instead it requires SSN + employment fields for individuals, or EIN + associated_persons for businesses.

What's new — Recipient-level email, phone, and address are no longer required when creating a SWIFT recipient.

What's new — POST /v1/virtual-accounts accepts four new request fields:

What's new — /v1/quotations accepts USDC and USDT as base_currency, in addition to USD. You can now quote against stablecoin-funded flows directly.

What's new — GET /v1/virtual-accounts/{id} now exposes bank-account fields at the response root, in addition to the nested source_deposit_instructions. Newly available at the root: account_holder_name, account_number, routing_number, bank_name, bank_address, account_holder_address, swift_bic, methods, and a markup echo.

What's new — POST /v1/users accepts verification_mode: "verification_link" for a hosted-link KYC/KYB flow. Send a minimal payload and Kira returns a verification_link URL where the end user completes verification themselves.

What's new — doc_type and doc_number are no longer required when creating ACH or WIRE recipients.

What's new — GET /v1/quotations/{quoteId} has been removed from the API reference. The endpoint was previously documented but not implemented; calling it returned 404.

What's new — POST /v1/virtual-accounts/{id}/payout accepts a new request shape, mode: "CRYPTO", that replaces the legacy payment_instructions envelope for crypto-funded payouts. The deposit address returned is the VA's permanent inbound address (no expires_at); recipient_id and supporting_documents become optional.