A resource map for the financial work you are building.
Browse the customer, account, card, conversion and payout concepts behind an integration, with dependencies and lifecycle meaning intact.
Using this reference
This is a conceptual resource reference, not executable API documentation. Operation names describe the work; fields below describe domain meaning, not a universal request schema. Use the issued version, paths, authentication, enums, units and errors for your actual integration.
Authentication and context
Establish a server-side session or credential context for the authorised customer and tenant. Keep privileged credentials outside the browser.
A request reference supports tracing. It is not, by itself, a guarantee of idempotent execution.
Customers and verification
The customer identifies the individual or business receiving the service. Verification and requests for information determine the next permitted step.
Customer onboarding guide
Accounts
An account record connects a customer with its receiving arrangement, currency and financial activity.
Account lifecycle guide
Cardholders
Keep the person using a card distinct from the customer or business responsible for it. Cardholder records can include individual or delegated roles.
Create, list, retrieve, update and delete operations are mapped in the underlying references. Identifier selectors and permitted changes depend on the contract. A deleted holder and a closed card are different objects and outcomes.
Issuing verification
Some issuing flows require additional verification before a wallet or card can be created. Retrieve the relevant KYC state and information request, then submit the required response through the issued operation. Do not apply one programme’s extra steps to every banking-linked card flow.
Issuing programmes guide
Wallets
A wallet record carries the balance and funding role defined by the service. A dedicated issuing wallet is distinct from a treasury balance.
Create, retrieve and history concepts appear in the mapped references. Preserve currency, owner, current state and original identifiers. A history operation does not imply a transfer endpoint or unrestricted movement between wallets.
Cards
Connect card identity, holder, format, funding and status throughout the lifecycle.
Secure card display
FX
Separate rate discovery, the quoted transaction and its financial execution.
Do not infer currency precision, funding limits or a forward product from a field name. FX lifecycle.
Beneficiaries and payouts
The beneficiary defines the recipient and route-specific details. The payout defines the authorised financial instruction.
Beneficiary and payout guide
Subscriptions and events
Discover available event types, create a subscription, inspect its details, update it or remove it according to the contract. Programme and customer context determine subscription scope. Machine callbacks and email notifications are different delivery surfaces.
Event families and processing
Tenants and agent tools
Tenant creation and configuration establish operating context, not automatic financial entitlement. Keep tenant roles, keys and callbacks separate. Agent tools sit on top of explicitly authorised operations; approval must bind to the exact execution arguments.
Tenant operations
MCP reference
Questions about api reference
Discuss your integration
Discuss your integration
Follow integration guides
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.
