Build the financial workflow, end to end.
Understand the resources, permissions and state transitions behind customer accounts, card issuing, conversion, payouts and agent-assisted finance.
Start with the resource you need
Follow customers and verification into accounts and wallets. Connect cardholders with issued cards, funding and transactions. Work from a conversion quote to its funded result, or from a beneficiary to a payout and its final state.
Browse the conceptual reference
Follow a complete integration journey
The guides cover authentication and tenant context, onboarding and information requests, receiving accounts, issuing variants, secure card display, FX funding and payouts. Each guide includes the objects, dependencies and recovery states that matter after the first successful request.
Read the guides
Keep your application in step with financial state
Use events to connect the right customer or transaction record with a change. Distinguish an account becoming active, a deposit settling, a conversion settling and a payout being funded. Verify delivery using the supplied contract, and reconcile repeated or out-of-order notifications.
Events and subscriptions
Give card data the right boundary
The host interface can show masked identity and status while sensitive details are delivered through the approved secure display. Handle session expiry and denied access without copying card data into logs, analytics or ordinary application storage.
Secure card display guide
Prepare agents with explicit authority
An agent can prepare a proposal within its allowed tools. Execution requires the relevant permission and approval, bound to the exact account, recipient, amount and currency. Keep the request, approval and result inspectable.
MCP integration
Test beyond a successful response
Exercise incomplete verification, expired quotes, insufficient funds, restricted cards, failed recipients, duplicate delivery and unknown outcomes. Match the result back to the originating object before treating a workflow as complete.
Sandbox and test scenarios
SDKs and tools
Use the contract for your integration
This centre provides conceptual reference and lifecycle guidance. Production hostnames, schemas, credentials, versions and exact error semantics come from the approved integration contract. Keep those executable details versioned with your implementation.
Example: from supplier instruction to reconciled payout
Identify the customer and funding account, collect the route-specific beneficiary fields, review the amount and currency, authorise the instruction, then follow the financial state through events and retrieval. A funding notification updates funding state; recipient delivery must come from the relevant final record.
Questions about developer centre
Discuss your integration
Discuss your integration
Browse the reference
Auracle home · All pages · Contact
Auracle Technologies Inc. is a technology provider and does not provide banking, custody, or investment services. Financial services are provided by licensed third-party partners.
