Create a payment

Authentication

Requires product-api-token (sent via the configured auth header as a JWT bearer token) headers.

Request body

JSON payload matching CreatePaymentDto.

Required fields:

  • amount (number, min 0.000005)
  • currency (string)

Common optional fields:

  • paymentMethods (array of strings: card | crypto | bank_transfer)
  • paymentMethod (string: card | crypto | bank_transfer)
  • cardPaymentType (on_ramp for on-ramp HPP only)
  • orderReference (string)
  • customerReference (string)
  • successUrl (string URL)
  • failureUrl (string URL)
  • expiryTime (string datetime)
  • useHostedPaymentPage (boolean)
  • metadata (object)

For an on-ramp HPP payment, set paymentMethod to card, useHostedPaymentPage to true, and cardPaymentType to on_ramp. Send the selected metadata.asset and metadata.network from GET /product-apis/on-ramp-networks. Idempotency-Key is required for this payment type.

Response

201: Payment created successfully. Returned data (PaymentResponseDto) includes:

  • paymentId
  • status (created | processing | completed | failed | expired | refunded)
  • amount
  • currency
  • paymentMethod (card | crypto | bank_transfer)
  • orderReference (object in schema; may be provided by your integration)
  • customerReference (object in schema; may be provided by your integration)
  • hostedPaymentUrl (object)
  • expiresAt (object)
  • instructions (object)
  • createdAt-

400: Bad request

401: Unauthorized

403: Forbidden

500: Internal server error

Body Params
number
required
≥ 0.000005
string
required
length between 3 and 10
paymentMethods
array of strings
paymentMethods
Allowed:
string
enum
Allowed:
string
enum
Allowed:
string
string
string
string
string
string
boolean
metadata
object
Headers
string
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json