This guide covers managing transactions after ingestion — retrieving individual transactions, updating transaction data, updating statuses, and applying bulk updates across multiple transactions. Full API reference is available in the API Reference.Documentation Index
Fetch the complete documentation index at: https://docs.corsa.finance/llms.txt
Use this file to discover all available pages before exploring further.
To ingest new transactions (deposits, withdrawals, trades, transfers), see the Ingest Operations guide.
Get a Transaction
Endpoint:GET /v1/transactions/{id}
Retrieve a transaction by its Corsa-generated UUID or your external referenceId.
Response Fields
| Field | Description |
|---|---|
id | Corsa-generated UUID |
referenceId | Your external reference ID |
type | DEPOSIT, WITHDRAW, TRADE, or TRANSFER |
currentStatus | Current status object with type and timestamp |
amount | Amount in the transaction currency |
convertedAmount | Amount converted to your platform’s preferred currency |
from / to | Source and destination parties |
txHash | Blockchain transaction hash (for crypto transactions) |
evaluationResult | Rule evaluation result, if the transaction was evaluated at creation |
customFields | Any custom key-value data |
Update a Transaction
Endpoint:PUT /v1/transactions/{id}
Update mutable fields on an existing transaction. Useful for enriching transactions with data that arrives after initial ingestion (for example, a blockchain hash that’s confirmed later, or updated risk data from a screening provider).
Updatable Fields
| Field | Description |
|---|---|
txHash | Blockchain transaction hash |
paymentMethod | Method used for payment |
paymentRail | Payment network or settlement rail |
transferType | INTERNATIONAL, DOMESTIC, or INTERNAL |
amount | Transaction amount details |
convertedAmount | Converted amount details |
currentRisk | Updated risk assessment |
integrations | Third-party integration data |
customFields | Custom key-value data |
Update Transaction Status
Endpoint:PUT /v1/transactions/{id}/updateStatus
Update the status of a transaction. Corsa tracks a full status history — each call appends a new entry.
Status Fields
| Field | Required | Description |
|---|---|---|
type | Yes | SUCCESS, PENDING, CANCELLED, FAILED, or FROZEN |
timestamp | No | ISO 8601 timestamp of the status change |
reason | No | Human-readable reason for the status |
subStatus | No | Additional status detail |
updateParentStatus | No | If true and the transaction belongs to a trade, recalculates the parent trade status |
Bulk Update Transactions
Endpoint:PATCH /v1/transactions/bulk/update
Apply the same field changes to up to 100 transactions in a single request. Use this to enrich or correct a batch of transactions efficiently.
Maximum 100 transaction IDs per request. You can pass Corsa UUIDs or your external
referenceId values interchangeably.Response
| Field | Description |
|---|---|
updatedTransactions | Array of successfully updated transaction objects |
failedTransactions | Array of transaction IDs that failed with error details |
totalProcessed | Total number of transaction IDs received |
successCount | Number of transactions successfully updated |
failureCount | Number of transactions that failed |
What’s Next?
Ingest Operations
Ingest deposits, withdrawals, trades, and transfers for your clients.
Manage Alerts & Cases
Bulk create, assign, and update compliance alerts and investigation cases.