Create Payment via Tokenisation
This endpoint allows you to create a card payment intent using a previously tokenised or newly provided card.
tokenobject is required and should contain aidandtypecard method reference.webhook_notificationobject is optional. If not provided, we will use your default webhook configuration that you’ve previously set up. If provided, we will send webhook notifications to the specified endpoint for this specific payment.- When the card requires 3DS authentication, we will return a
pay_codeobject containing{3ds_url: ''}. You must direct your customer to this URL to authorise the payment. After successful authorisation, customer back toreturn_urland you can use the capture API normally to collect the payment from the user.
Authorizations
A unique identifier assigned to each application.
A secure token associated with the app-id.
Body
Amount in smallest currency unit (e.g., cents)
1000
ISO 4217 currency code (e.g., AUD, USD)
"USD"
The card token object
External ID
"order_test_xxx"
Return URL
"https://example.com"
Whether to auto capture the payment (if applicable)
The type of payment.
regular, unscheduled Indicates the reason for a merchant-initiated payment request. Should be provided if payment_type is unscheduled.
resubmission, delayed_charge, no_show, reauthorisation "resubmission"
An identifier that links the payment to an existing series of payments. Should be provided if payment_type is unscheduled.
"1GKPTU7E"
Response
Payment created
"7PPPMXIGH"
"Testing"
"test@example.com"
"wc_order_6C1hcvg4T7Pom"
pending, authorised, waiting, received, expired, return_pending, return_expired, partially_refunded, return_received, return_rejected, failed, in_dispute, dispute_lost "authorised"
"USD"
10000
10000
0
false
"card"
""
false
"regular"
"2025-05-28T04:22:21.567+0000"