Customers and businesses
Identify the account owner and the permissions attached to an operation.
API overview
The objects behind
a financial workflow.
Connect account ownership, balances, quotes and payment outcomes through the Finanzer platform model. This is a domain overview, not an executable API reference.
Concept documentation. Request the versioned production specification before implementation.
Map your workflow to a domain.
Accounts, balances and wallets
Represent currency accounts and wallets while keeping available money, pending amounts and other balance types distinct.
Quotes and transfers
Review amounts, currencies, fees, rates and timing before a transfer. Follow the operation through processing to its final state.
Cards and events
Connect card activity and financial events to your application's own records.
A request needs a recorded outcome.
Accepting a request does not mean the financial operation has completed. Use the API contract's object identifiers, explicit states and error definitions to track the result.
Before a write
Check the required permissions, validation rules and idempotency contract.
After acceptance
Keep the operation identifier and distinguish processing from final success or failure.
When retrying
Follow the documented retry rules so a repeated request does not repeat the financial operation.
TRANSFER / LIFECYCLE
Quote preparedReview
Transfer acceptedProcessing
Outcome recordedFinal state
Event deliveredReconcile