Algorand USDC for operational teams
FastPay
Send payment-ready counterparties USDC with workspace permissions, browser-side authorization, and an audit trail your team can actually read.
Platform
Operational USDC payments without losing governance.
Settlement rail Algorand
Payment asset USDC ASA
FastPay is built around the workspace, not a single private wallet. Teams can invite members, onboard counterparties, prepare payments, and keep the audit trail in the same place.
The browser wallet flow keeps authorization local while the backend prepares transactions, sends network submissions, and records the operational state your team needs later.
That means a payment is not just a chain transaction: it is a reviewed workflow with people, roles, history, and support context attached.
Open the workspaceControls
Focused product surfaces for the payment lifecycle, from access to settlement.
Workspace governance
Invite users, change roles, revoke pending invitations, and preserve a required admin so access stays recoverable.
Open team controls
Counterparty readiness
External contacts move from invitation to accepted relationship, then become payment-ready when their wallet can receive USDC.
Review contacts
Payment review
Before authorization, teams can inspect the recipient, USDC amount, FastPay fee, and transaction details.
Start a payment
Wallet readiness
The wallet page checks active LogicSig revision, USDC opt-in, authorization policy, and whether this browser can sign.
Check wallet
Settlement history
Status pages and history tables keep completed, confirming, submitted, and failed states understandable.
Open history
Recovery and support
Recovery, problem reports, and notification events keep operational mistakes visible instead of hidden in a chain explorer.
Open support pathA dashboard that shows balance, wallet readiness, quick payments, contacts, members, invitations, and transaction history without jumping through five different tools.
Operational signals
What your team can see after the payment leaves the form.
Every payment keeps its direction, amount, FastPay fee, status, transaction IDs, and on-chain link in one workspace record.
Wallet readiness calls out the next action when a browser, LogicSig, USDC opt-in, or signing fallback needs attention.
Notifications and support reports point users back to the payment page instead of leaving them with an opaque internal ID.
Frequently Asked Questions
What does FastPay actually move?
FastPay prepares and submits Algorand ASA transfers for USDC payments between payment-ready counterparties. The application records the business context around those transfers.
Can a team member pay without being an admin?
Workspace roles separate access management from payment operations. Admins manage members and invitations; payment readiness is checked separately through wallet state and authorization material.
What happens if a transaction is rejected before chain submission?
Algorand nodes can reject a group before it reaches the chain. FastPay records that status clearly so the user can prepare a fresh group instead of assuming an on-chain payment failed.
How does a counterparty become payment-ready?
The counterparty accepts the invitation, creates or connects the required browser wallet, and opts in to the configured USDC ASA. FastPay then shows the relationship as ready for payments.
Where do I find the audit trail?
The dashboard, history page, and payment status page keep status, transaction IDs, group information, and support actions linked to the workspace.