Create Payment via Card Information (S2S)
This endpoint allows you to create a card payment intent using raw card information.
card_infoobject is required and should contain the card number, expiry month/year, CVV, and cardholder name.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, the customer will return toreturn_url, and you can use the capture API normally to collect the payment from the user. - If
captureis set totrue, the payment will be automatically captured after successful authorisation. Ifcaptureis set tofalse, the payment will remain in theauthorisedstatus until you explicitly call the capture API.
When the payment reaches the authorised status, a token object will be returned in the API response and also included in the webhook notification.
You should save this token to create future payments without requiring your customer to re-enter their card details.
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)
"AUD"
Customer's email.
"email@gmail.com"
Customer's first name.
"John"
Customer's last name.
"Doe"
Customer’s billing address details.
Card information.
External ID
"order_test_xxx"
Return URL
"https://example.com"
Description for the payment.
"Payment for invoice #1234"
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"
Browser details information.
The IP address of the cardholder
"192.168.1.1"
Whether to auto capture the payment (if applicable)
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 "waiting"
"USD"
10000
10000
0
true
"card"
""
false
"regular"
"2025-05-28T04:22:21.567+0000"