Skip to main content

October 18, 2026 — actual card-account deposit credit

  • Enter any whole-dollar nominal from 10 USD (10, 11, 12 and so on). The quote shows the actual amount credited after the issuer’s 1% deduction.
  • The total customer fee remains 1.5% of the credit and includes the issuer deduction: nominal 10 USD credits 9.90 USD and costs 10.05 USDT plus TRX; nominal 100 USD credits 99 USD and costs 100.49 USDT plus TRX.
  • New invoices use nominal_150. Existing invoices retain their amounts, pricing, wallet binding and payment references. Card issuance and subsequent card top-up pricing are unchanged.

October 17, 2026 - separate funding minimums

  • Subsequent card top-ups start at 5 USD with no additional fee. Product responses expose this as topupMin.
  • The initial balance at card issuance remains at least 10 USD (min), and card-account deposits remain at least 10 USD plus the 1.5% account fee and separate TRX network costs.

October 17, 2026 - card issuance price

  • New card issuance costs 2 USD. The minimum initial balance remains 10 USD, so an issuance with 10 USD credited costs 12 USD. Card funding still has no additional percentage fee. Existing operations retain their original price.

October 17, 2026 - reduced funding fees

  • New card-account deposits add a 1.5% fee: 100 USD credit requires 101.50 USDT, plus network fees in TRX. Existing invoices retain their frozen pricing.
  • Remove percentage fees from initial and subsequent card funding. Issuance remains 3 USD; a card funded with 10 USD costs 13 USD, and a subsequent 10 USD top-up costs 10 USD.

October 16, 2026 — card-account funding and Live API

  • New card-account deposits credit the requested amount and add a 3% fee: 100 USD credit requires 103 USDT, plus network costs paid separately in TRX. Existing invoices keep their original pricing.
  • Bind new invoices to an active Plane wallet. API-created invoices require walletId; payment is confirmed from that wallet in the signed-in console.
  • Individual verification allows up to 100 card issuances per UTC calendar month, including pending requests.
  • API keys can be created and used only in Live after approved verification. Previously issued Sandbox keys are rejected. The Sandbox console remains available for test cards and wallets.

September 24, 2026 — development console

  • Create a Nile test wallet automatically for Sandbox workspaces, without verification. Live wallet access still requires approved verification and separate activation.
  • Replace the browser-only wallet onboarding with a Plane account wallet. Plane stores encrypted keys server-side, so this wallet is custodial. Existing local wallets remain accessible separately in the browser where they were created.

September 21, 2026

  • Require approved verification for every API key, including sandbox keys. Unverified users retain sandbox console access.
  • Add individual verification (500 card issuances per UTC calendar month) and corporate verification (no monthly issuance quota).
  • Introduce direct USDT/TRON card-account invoices: a 1.5% fee is deducted from the deposit. Retire the old TON funding-address endpoint.
  • Card issuance costs 3 USD plus initial funding of at least 10 USD. Each card funding carries a separate 0.2% fee.
  • Add card payment history and dated card-account statements with opening, closing and running balances.
  • Add the original browser-local wallet with an encrypted recovery backup controlled by the user (retained as a legacy option in the development console).

September 20, 2026

  • Published the Plane Business documentation and OpenAPI reference.
  • Added step-by-step card issuance, top-up, card-control, and funding guides.
  • Documented webhook signing, deduplication, and delivery retries.
  • Added error handling, pagination, verification, and go-live guidance.
Live card and funding activation remains restricted. Documentation updates do not enable a capability or change your company’s approval state.

API compatibility

The public path prefix is /api/v1. No automatic migration to a new major API version is implied. Pin your integration to the documented fields and handle additional response fields without failing. There is no published official SDK yet; the examples use HTTP directly.