Skip to main content
POST
/
api
/
partner
/
v2
/
off-ramp
/
execute
Execute an off-ramp transaction
curl --request POST \
  --url https://staging-api.capa.fi/api/partner/v2/off-ramp/execute \
  --header 'Content-Type: application/json' \
  --header 'partner-api-key: <partner-api-key>' \
  --data '
{
  "transactionId": "8374f327-38bd-4b0b-b8a7-2524599eb903",
  "transactionHash": "0x48c78b33abc0256b217bebbb3f0a30642c17c5527761f09d35c24aa85361b7f0"
}
'
{
  "success": true,
  "data": {
    "id": "8374f327-38bd-4b0b-b8a7-2524599eb903",
    "status": "PENDING"
  }
}
Executes a previously created off-ramp transaction, triggering the fiat payout to the user’s bank account. Call this after the user has sent crypto to the destinationWalletAddress returned by the Create Off-Ramp endpoint.

​
Transaction Status Values

StatusDescription
PENDINGTransaction is pending processing.
IN_PROGRESSTransaction is being processed.
COMPLETEDTransaction has completed successfully.
FAILEDTransaction has failed.
CANCELLEDTransaction was cancelled.
CRYPTO_RECEIVEDCrypto payment has been received.
CRYPTO_NOT_RECEIVEDCrypto payment was not received.
COMPLETED_CRYPTO_RECEIVALCrypto receival process has completed.
BANK_TRANSFER_PENDINGBank transfer is pending.
READY_BANK_TRANSFERReady to initiate bank transfer.

​
Important Notes

  • The transactionId must reference a valid off-ramp transaction created via Create Off-Ramp.
  • The transaction must belong to the partner associated with the API key.
  • Optionally include transactionHash, the blockchain hash of the user’s crypto transfer, to help Capa locate and confirm the incoming funds. It must be a valid blockchain hash.

​
Use Cases

  • Manual Execution: Trigger execution after verifying crypto receipt.
  • Workflow Integration: Separate transaction creation from execution in automated workflows.

​
Error Codes

​
Common Errors

HTTP StatusCodeMessage
401UNAUTHORIZED”API Key is missing”
401UNAUTHORIZED”Invalid API Key format”
401UNAUTHORIZED”Invalid API Key”

​
Endpoint-Specific Errors

HTTP StatusCodeMessage
400INVALID_USER_INPUT_ERROR”Invalid User Input”
404TRANSACTION_NOT_FOUND”Transaction not found”
403TRANSACTION_ACCESS_DENIED”Transaction does not belong to this partner”

Headers

​
partner-api-key
string
required

Api key for the affiliated partner that is performing the request

Body

application/json
​
transactionId
string<uuid>
required

Identifier for the off-ramp transaction to execute

Example:

"8374f327-38bd-4b0b-b8a7-2524599eb903"

​
transactionHash
string

The blockchain transaction hash of the user's crypto transfer

Example:

"0x48c78b33abc0256b217bebbb3f0a30642c17c5527761f09d35c24aa85361b7f0"

Response

201 - application/json

Transaction execution initiated successfully

​
success
boolean
Example:

true

​
data
object