Compliance

LamportPay Compliance

Non-custodial by design. Clear responsibilities for wallet authorization, verification and bank payouts. This page describes the current model; it is not a certification, regulatory approval or legal advice.

Last updated 15 October 2026.

SANDBOX · SANDBOX

SANDBOX: test-network assets and the payout partner's test environment. Real bank payouts and production identity verification are DISABLED pending production approval.

What LamportPay does not do

Hold customer funds, private keys or balances. Our ledger is a record only.
Collect identity documents. Verification happens on the payout partner's hosted page.
Convert currency or send bank payouts itself.
Offer mobile-wallet, card or cash payouts, or accept unsupported assets and networks.
Ask for a seed phrase or private key. Wallet sign-in is a message signature, never a transaction.
Claim a licence or regulatory approval of its own.

What LamportPay does

Provides the software: quote, checkout, wallet signing request and payment tracking.
Discloses one LamportPay fee, separate payout partner costs, and applicable swap, price-impact and network costs before approval.
Supports a bank-payout design for a verified sender's own account or a beneficiary's account. Current payouts are sandbox demonstrations only.
Follows the payout partner's transfer status. The partner's record is authoritative.
Keeps an append-only audit log of admin actions.
Uses USDC on Solana as the enabled settlement currency; eligible SOL routing uses Jupiter quotes without mainnet execution in the sandbox build.

Official bank guidance

Bank restrictions & availability.

Stables documentation

No verified payout blacklist

The official documentation reviewed does not provide a complete list of unsupported payout banks. A bank logo here does not guarantee eligibility; Stables checks the destination and bank details for each payment.

Australian deposit warnings

Stables names ANZ, NAB and CBA as examples where deposits into virtual accounts may be delayed, reviewed or returned. This concerns incoming deposits—not a ban on payouts to those banks.

Not a permanent bank block

Stables says these outcomes vary by customer and account, and a delayed or returned transfer is not necessarily a permanent block. LamportPay currently has fiat payouts DISABLED.

Official documentation reviewed 14 October 2026. This guidance does not expand LamportPay’s enabled destinations.

Who does what

Wallet funds and authorization: You control your wallet. In the production design, you send USDC directly to the single-use deposit address Stables issues for the payment. LamportPay holds no funds. The sandbox build moves no payment funds.
Identity verification (KYC): Stables, on its hosted page. LamportPay collects the name and contact email needed for customer setup, keeps a verification link and status, and does not collect identity documents. Production KYC is DISABLED.
AML and sanctions screening: Stables' compliance process governs transfer acceptance and any holds. Sandbox responses do not establish production screening approval.
Travel Rule: Stables determines requirements for the transfer. LamportPay records and surfaces required Travel Rule information as a payment requirement, not a separate payment status.
Bank details check, currency conversion and payout: Stables validates bank fields, quotes local-currency payout and reports transfer outcomes. Real bank payouts remain DISABLED.
Crypto conversion route: Jupiter supplies eligible Solana-to-USDC routing. LIVE · read-only market quotes are available; mainnet swap execution is DISABLED in the sandbox build.
Quote, fee disclosure, checkout and status tracking: LamportPay.
Approving the transaction: You, in your own wallet. Sign-in uses a plain-text message; sandbox Pay Now uses a real test-network memo transaction that moves no funds.

Verification and recipient safeguards

Quotes can be shown before verification. Bank details are checked with Stables, and the sender must be verified before a transfer is created. Verification runs on Stables' hosted verification page; LamportPay does not build its own document-verification flow.

Own bank account · default: The account-holder name comes from the verified Stables customer record and is not editable in checkout.
Beneficiary bank account: The verified sender supplies the beneficiary's name, individual or business type, and a payment purpose other than transfer to own account. Provider validation and compliance rules still apply.

Stables may reject or hold a transfer. Connecting a wallet or signing in is not identity verification or payout approval.

Costs and payment records

LamportPay fee: One fee, taken out of the total you send—not an extra conversion fee plus a swap fee. The app shows the fee amount before approval.
Payout partner fee: Stables costs are quoted separately. They are not included in LamportPay’s fee.
Swap & network costs: Any Jupiter swap costs, price impact and Solana network fees are separate. The sandbox build does not execute mainnet swaps or move payment funds.

Stables is authoritative for transfer status. Signed webhooks, live status reads and reconciliation update the record. Wallet approval alone is not evidence of a completed payout, and a sandbox receipt is not proof that real money reached a bank.

Security controls and operational review

Wallet sign-in checks the message origin, age and signature, with one-time signature use. No seed phrase or private key is requested.
Provider writes use idempotency keys; webhook signatures are verified and transfer progress is synchronized without moving backwards.
Admin actions require server-side role checks and are audit logged. The payout queue only refreshes status; it does not create transfers or simulate deposits.
Rate limits and emergency payment controls restrict payment actions. Refunds, compliance and manual reviews are operations cases, not invented payout statuses.

These safeguards are not a guarantee against loss or a completed security certification. Core security controls are in place. Our next roadmap phase is dedicated to security: an independent external audit, penetration testing, hardening, and monitoring with incident response. That phase, end-to-end validation and operational readiness must be completed before production availability.

Infrastructure and regulatory context

LamportPay's payout partner is Stables, used here in sandbox mode. Its external listing in the official Circle Alliance Directory is not a LamportPay partnership, endorsement or production approval.

Circle's licenses cover Circle's own regulated activities. They do not automatically license, authorize, endorse or extend regulatory coverage to Stables, LamportPay or any other company that uses Circle's products. LamportPay does not claim to be licensed by Circle. Stables' own licensing and regulatory information is published on its legal page.

Non-custodial software does not automatically qualify for a regulatory exemption. Real-money availability requires applicable legal review, Stables production onboarding, validated payout coverage and production safeguards. No direct Circle or Tether partnership is confirmed. Production bank payouts and KYC remain DISABLED.