Saltar para o conteúdo
Transferir a descrição da OpenAPI
Visão geral
Easypay Documentation
Licença
Idiomas
Servidores
Sandbox
https://api.test.easypay.pt/2.0
Production
https://api.prod.easypay.pt/2.0

Create and manage one-time payment transactions

Operações

Tokenize payment details for variable on-demand charges

Operações

Set up and manage automated recurring payments

Operações

Operations for managing payment captures

Operações

Operations for managing payment authorisations

Operações

Operations for managing payment voids

Operações

Pedido

Segurança
accountId and apiKey
Caminho
idstring(uuid)obrigatório

Resource Identification

curl -i -X GET \
  'https://api.test.easypay.pt/2.0/void/{id}' \
  -H 'AccountId: 2b0f63e2-9fb5-4e52-aca0-b4bf0339bbe6' \
  -H 'ApiKey: eae4aa59-8e5b-4ec2-887d-b02768481a92'

Respostas

OK

Corpoapplication/json
statusany

Indicates the current status of the refund. Possible values include:

  • processing: This is the initial state, and it means that the void is queued.
  • success: The void has been completed successfully.
  • failed: The void could not be completed due to an error or issue. This field provides a clear indication of the current state of the refund, helping users understand its progress and outcome.
Enum"success""processing""failed"
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".

authorisationobject
Resposta
application/json
{ "status": "success", "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "transaction_key": "string", "descriptive": "string", "authorisation": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "waiting", "key": "string", "customer": {}, "method": {}, "currency": "EUR", "value": 15.78 } }

Voids a Single Auth or Frequent Auth

Pedido

Segurança
accountId and apiKey
Caminho
idstring(uuid)obrigatório

Resource Identification

Corpoapplication/jsonobrigatório

Void details

descriptivestring<= 255 charactersobrigatório

This will appear in the bank statement/mbway application.

transaction_keystring<= 50 characters

Your internal key identifying this void.

curl -i -X POST \
  'https://api.test.easypay.pt/2.0/void/{id}' \
  -H 'AccountId: 2b0f63e2-9fb5-4e52-aca0-b4bf0339bbe6' \
  -H 'ApiKey: eae4aa59-8e5b-4ec2-887d-b02768481a92' \
  -H 'Content-Type: application/json' \
  -d '{
    "descriptive": "string",
    "transaction_key": "string"
  }'

Respostas

Created

Corpoapplication/json
statusstring
Exemplo: "ok"
messageArray of strings

An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

Exemplo: ["Your request was successfully created"]
idstring

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.

Exemplo: "8010e7d5-9985-4ae3-b1bf-6b70019439c7"
Resposta
application/json
{ "status": "ok", "message": [ "Your request was successfully created" ], "id": "8010e7d5-9985-4ae3-b1bf-6b70019439c7" }

Operations for managing payment refunds

Operações

Operations for managing chargebacks

Operações

Configure and manage webhook notifications for payment events

Webhooks

Access transaction and ledger reports

Operações

Transfer funds from Easypay accounts to SEPA bank accounts

Operações

Configure account URLs for notifications and credit card transactions

Operações

Embedded payment form solution for websites

Operações

System health check endpoints

Operações