Create a new payment intent between source and destination external accounts.
The system evaluates each active provider’s capabilities against the external account metadata
(currency, account type, rail, country) to determine which providers can handle the payment.
If providerId is specified, it must be among the eligible candidates — otherwise a 400 error
is returned. If omitted, the first eligible provider is selected.
The selected provider determines which compliance requirements (KYC/onboarding steps) apply. Different providers may have different compliance flows.
Auto-Complete: 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 frontendUrl
will be null.
GnosisRamp JWT bearer token for authenticated customer requests
Request to create a payment intent
Source external account identifier
"ext_acc_src_123"
Destination external account identifier
"ext_acc_dest_456"
Transfer amount as a decimal string (not a number to avoid precision issues)
"100.50"
When true, automatically execute the transaction after compliance completes (skips the manual execute step)
Optional redirect URL after intent completion
"https://example.com/callback"
Optional preferred provider ID. Must be a valid candidate for the payment path — i.e., the provider must support the currencies, rail, country, and account types of the external accounts. Use GET /currencies/supported or GET /providers to discover available provider IDs.
255"provider_123"
Intent created successfully