Skip to main content
POST
/
intent
/
{intentId}
/
transaction
Execute transaction for payment intent
curl --request POST \
  --url https://app.gnosisramp.com/api/v1/intent/{intentId}/transaction \
  --header 'Authorization: Bearer <token>'
{
  "intentId": "intent_123",
  "status": "IN_PROGRESS",
  "transaction": {
    "id": "txn_123",
    "status": "PENDING",
    "createdAt": "2024-01-01T00:00:00.000Z",
    "updatedAt": "2024-01-01T00:00:00.000Z",
    "context": {}
  },
  "depositInstructions": [
    {}
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.ramp.gnosis.io/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

uRamp JWT bearer token for authenticated customer requests

Headers

​
Idempotency-Key
string

Optional unique key for exactly-once processing. When provided, the server guarantees that the request is processed at most once. Duplicate requests with the same key and body return the original cached response with the X-Idempotency-Replayed: true header. Using the same key with a different body returns 422. Keys are scoped per project and cached for 24 hours.

Maximum string length: 256

Path Parameters

​
intentId
string
required

Intent identifier

Response

Transaction accepted for execution

Response from executing a money movement transaction

​
intentId
string
required

Intent identifier

Example:

"intent_123"

​
status
enum<string>
required

Transaction status

Available options:
IN_PROGRESS
Example:

"IN_PROGRESS"

​
transaction
object
required

Money movement transaction

​
depositInstructions
object[]

Deposit instructions for the transaction (provider-specific structure)