Create a new payment intent with inline source and destination account data.
The API accepts account details directly in the request - no need to pre-create external accounts. External accounts are created internally as an implementation detail.
The system will automatically:
Auto-Complete Feature: For returning customers who have already completed compliance requirements,
the API will automatically create a transaction and return deposit instructions immediately,
skipping the onboarding workflow. In this case, transaction will be present and onboardingUrl
will be null.
Idempotency: Supports the Idempotency-Key header for exactly-once processing. Duplicate
requests with the same key and body return the cached original response with
X-Idempotency-Replayed: true.
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.
uRamp JWT bearer token for authenticated customer requests
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.
256Request to create a payment intent with inline account data
Source account details
Destination account details
Source amount as a decimal string (not a number to avoid precision issues)
^[0-9]+(\.[0-9]+)?$"100.50"
Redirect URL after onboarding/compliance completion (must be http/https)
"https://example.com/onboarding-complete"
Redirect URL after checkout/payment completion (must be http/https)
"https://example.com/checkout-complete"
Auto-execute transaction after compliance completes
Preferred provider ID (must be a valid candidate for the payment path)
"bridge"