Skip to content

Last Updated: 15 July 2025 | Change Log

Guest card payment

Take a one-time card payment.

If PSD2/SCA or other regional mandates apply you should follow the steps for enabling 3DS

1. Integration Type

Apply card details directly in our Payments API, or use our PCI-compliant Checkout SDK to create a session

Collect the card details and send an API request with these details to the payments resource.

2. Basic Request

application/json

A one-off card payment using a plain card number

{ "transactionReference": "Memory265-13/08/1876", "merchant": { "entity": "default" }, "instruction": { "method": "card", "paymentInstrument": { "type": "plain", "cardHolderName": "Sherlock Holmes", "cardNumber": "4000000000001091", "expiryDate": { "month": 5, "year": 2035 }, "billingAddress": { "address1": "221B Baker Street", "address2": "Marylebone", "address3": "Westminster", "postalCode": "SW1 1AA", "city": "London", "state": "Greater London", "countryCode": "GB" }, "cvc": "123" }, "narrative": { "line1": "trading name" }, "value": { "currency": "GBP", "amount": 42 } } }

3. Add additional features

In most cases you will need to add some additional features such as 3DS, auto settlement or a risk assessment

4. Response

Features that change the API flow

Certain features add additional requests and responses:

  • 3DS - you will receive a 201 - 3dsDeviceDataRequired as well as the possibility of an issuer challenge
  • FraudSight - you may receive a 201 - fraudHighRisk outcome, stopping the payment
  • Auto Settlement - automatic 202 - sentForSettlement following authorization.
    • If any of the AVS/CVC response riskFactors are marked as notMatched the payment will be sentForCancellation automatically by default but can be disabled.
application/json
No response example