Create intent
Create a payment intent
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Headers
Setting the idempotency key header to a unique value for each request ensures that transactions are never duplicated. Push recommends storing your internal transaction identifier in this field.
255
Body
Direction of the money flow, from the perspective of the Push Account
cash_in
, cash_out
Push's unique identifier for the user
Amount for the transaction, in smallest unit of specified currency (ie if currency is USD, the unit would be cents)
Currency associated with the amount
USD
The url to which the user will be redirected after completing the payment session.
If this parameter is omitted, the UX will use postMessage
to notify the wrapping browser that the payment session has been completed.
The url to which Push will send a webhook notification when the intent is approved.
If this parameter is omitted, Push will use the default webhook URL registration for the operator.
How the intent should be approved and submitted for processing
automatic
, manual
The settlement account which should be used for the transaction. If your program with Push utilizes multiple settlement accounts, this field is required to be set.
Shows loyalty opt-in screen if set to true
Shows request limits screen if set to true
Response
The URL for the payment session