Orkesta manages the full lifecycle of corporate payments — creation, approval, processing, settlement, and reconciliation — through a unified interface and REST API. Whether you initiate payments from the dashboard or programmatically via the API, every transaction follows the same lifecycle and is visible in one place.Documentation Index
Fetch the complete documentation index at: https://docs.orkesta.com.tr/llms.txt
Use this file to discover all available pages before exploring further.
Payment lifecycle
Every payment in Orkesta moves through the following statuses in sequence:| Status | Description |
|---|---|
pending | Payment has been created and is awaiting approval or processing. |
approved | Payment has passed the approval workflow and is queued for processing. |
processing | Payment has been submitted to the payment network and is in transit. |
settled | Funds have been confirmed as received by the destination account. |
reconciled | Payment has been matched to a bank statement entry and closed. |
Payments can also move to
failed or cancelled states. See the API reference for the full status machine.Supported payment methods
Orkesta supports the following payment methods across domestic and cross-border transactions:| Method | Description |
|---|---|
| Bank transfer | Standard domestic and international transfers between bank accounts. |
| Credit / debit card | Card-based payments with near-instant authorization. |
| Virtual account | Dynamically generated account numbers that map inbound payments to specific payers. |
| EFT / wire | Electronic funds transfer for same-day domestic TRY transactions. |
| Direct debit | Pull-based collections from authorized bank accounts via signed mandate. |
Key concepts
Accounts — Funding and destination accounts are linked to your workspace. Every payment requires a source (from_account) and a destination (to_account). You can manage accounts from the Orkesta dashboard or via the Accounts API.
Payment references — Each payment carries a unique system-generated ID (e.g., pay_01HXYZ) and an optional reference field you supply. The reference field is your internal identifier — an invoice number, purchase order, or transaction ID — used to match payments during reconciliation.
Approval workflows — Your workspace can require one or more approval steps before a payment moves from pending to approved. Approval workflows are optional and configurable per payment method, amount threshold, or account. When a workflow is active, submitted payments wait in pending until all required approvers act.
Create and manage payments
Create single payments, batch payments, and scheduled transfers via dashboard or API.
Supported payment methods
Compare bank transfer, card, virtual account, EFT, and direct debit.
Reconcile payments
Automatically match transactions to bank statements and resolve discrepancies.