This transaction type is available for: Cards.

Use the one-time purchase flow when you want to charge the shopper immediately.

Check below the available environments where you can perform a server-to-server POST request to generate the transaction.

Before you make the payment

• Ensure the order has been created and submitted
• The request needs an Authorization Header with the transactionsignature returned on the order creation response.

In this request, the Bearer Token is replaced by the checkout response transactionSignature.

The message below represents the one-time purchase where the payment is performed immediately, and no additional services (3D Secure, Tokenization, and Card OneClick) are identified for calling.

Header parameters

Request parameters

Here is an example of how to make a one-time purchase:

{
    "cardInfo": {
        "PAN": "5236410030000927",
        "secureCode": "776",
        "validationDate": "2026-05-26T00:00:00.000Z",
        "cardholderName": "Jane Smith",
        "createToken": false
    }
}

What’s next?

Have a look at the other Card payment features you can use.

• Payment with pre-authorized and subsequent capture when you charge only upon delivery (total or partial charge).
• Payment authorization with 3D Secure authentication (frictionless or challenged).
• Payment based on card Tokenization.
• Payment based on Card OneClick.

After you make the payment, you will receive a response comprising a paymentStatus in the message. It informs whether the transaction was accepted, declined, still pending a final result, or requires additional action.

• Success: The purchase has been processed successfully and the customer has been debited.
• Declined: The purchase has been declined.
• Pending: The final result of the purchase is not yet known. You will need to inquiry on the status of this transaction until it reaches a final state, or you decide to cancel it.
• Partial: The purchase is partially accepted, but requires additional actions to the completed (e.g. 3D-Secure authentication). The actionResponse element is provided for instructions on how to proceed.

Get the payment status

Afterwards, once the payment has been processed, you can check the status of your transaction making a GET request.

The Authorization HTTP header is set to the Bearer token as it was used in the initial Checkout.

Request URL:

https://stargate-cer.qly.site1.sibs.pt/api/v1/payments/{transactionID}/status

Request Headers:

Autorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6I (...)
X-IBM-Client-Id: b4480347-9fc8-4790-b359-100a99c60ea3
Content-Type: application/json

A successful technical response comprises of an HTTP-200 status and a returnStatus.statusCode=”000″.

Here are some examples of the possible result codes: