Skip to main content
Transactions — Vita Wallet Business API
The Transactions module provides the endpoints needed to query, monitor, and reconcile the transactions created in your Vita account. These endpoints are read-only — they do not create, modify, or cancel transactions — and are designed to support reconciliation processes, accounting integrations, transaction tracking dashboards, and incident recovery flows (such as confirming whether a payout was successfully created after a timeout error). Reconciliation is a critical part of any payments integration, and Vita provides three complementary endpoints to retrieve transaction data with different levels of granularity and filtering.

​
Common use cases

Idempotency after timeouts

Confirm whether a payout was created before retrying.

Daily reconciliation

Fetch all completed transactions from the previous day to match against your records.

Accounting integrations

Export transaction data into ERP, accounting software, or BI tools.

Status monitoring

Track pending or processing transactions in real time.

Customer support

Look up specific transactions when a user asks about a payout.

Audit trails

Retrieve historical data for compliance and audit purposes.

​
When to use each endpoint

→ Use List API Transactions with the order parameter.This is the idempotency check referenced in the payout documentation. When you receive a 500 or timeout from POST /api/businesses/transactions, query this endpoint with your order ID to confirm whether the transaction was actually created on Vita’s side before deciding to retry.
→ Use List All Transactions with date range and status filters.This is the workhorse endpoint for accounting and reconciliation. Fetch all completed transactions in a date range, filter by currency or type, and paginate through large result sets.
→ Use Get Transaction with the Vita transaction ID.When you already have the Vita transaction ID (e.g., from a webhook or a previous list query), use this endpoint to retrieve the most up-to-date and complete information for that transaction.

​
Important considerations

Read-only endpoints. All endpoints in this section are read-only. They never create, modify, cancel, or affect any transaction state. Use them freely without risk of side effects.
Webhooks vs. polling. For real-time status updates, always prefer Webhooks over polling these endpoints. Polling should only be used for reconciliation, retrospective checks, and one-off lookups — never as a substitute for event-driven notifications.
Pagination. Both the order filter and date-range queries can return multiple results. Always paginate correctly to avoid missing data when the result set is larger than the requested count.
Date filters. Use the YYYY-MM-DD format. Filtering is applied based on the transaction’s creation date.