v1

latestOpenAPI 3.1.0MIT2026-08-0659118508.8 KB

Voids

Get a void

Returns the details and current status of a void, including the authorisation it cancelled. Use this to track a void's outcome after creation, since processing is asynchronous.

Required scope: <code style="background:#e8f0fe;color:#1a73e8;padding:2px 8px;border-radius:12px;font-size:0.85em">void:read</code>

get/void/{id}

Path parameters

idstring uuid required

The void's unique identifier (the id returned when the void was created).

Response

status'pending' | 'processing' | 'success' | 'failed'

Indicates the current status of the void:

pending: Initial state — the void has been created and queued.
processing: The void is being processed by the acquirer.
success: The void completed successfully (the authorisation was released).
failed: The void could not be completed due to an error or issue.

idstring uuid

A unique identifier for the resource. While typically formatted as a UUID (Universally Unique Identifier), it can also be in other formats as defined by the user. This field ensures the resource can be distinctly recognized and referenced.

transaction_keystring

A customizable text field for users to input their own identifier for the resource. This can be any string that helps the user uniquely identify or reference the resource in their own system.

descriptivestring

A text field that describes the transaction as it will appear on the end user's account statement. This is typically used to provide clear, recognizable information about the payment, such as "Payment of Invoice Nº 1982652" or "Ticket for Queen".

Example response

{
  "authorisation": {
    "customer": {
      "id": "649e88cf-0b78-4c36-8f99-33f5ebb812a1",
      "name": "John Doe",
      "email": "john.doe@example.com",
      "phone": "911234567",
      "phone_indicative": "+351",
      "fiscal_number": "PT123456789",
      "key": "customer Key Example",
      "language": "PT"
    },
    "value": 15.78
  }
}