Payment Methods

EPS

Providers:

aci

ACI
buckaroo

Buckaroo

Buckaroo

Request example

Payments expiry time for EPS via Buckaroo is 30 minutes. EPS amounts are expressed in euros; typical integration uses EUR for the Austrian EPS network.

The create-payment request follows the usual Paymexx payment shape (method key eps, EUR transaction body, return and webhook URLs). Buckaroo EPS service parameters (issuer, and any required bank selection) follow your Buckaroo contract and gateway configuration rather than mandatory extra fields on this payload. See also the Buckaroo EPS Pay request documentation for upstream field details. 

                                                            
{
   "id": "7bb6f1f3-d280-4b0c-a74f-90471ea69426", // Auto-generated UUID
   "paymentMethod": "eps",
   "returnUrl": "http://example.com", // URL to return after payment completion.
   "webhookUrl": "https://example.com", // URL to receive webhook notification.
   "transaction":{
      "reference": "test-1111", // Max 20 characters
      "currency": "EUR", // ISO 4217
      "amount": 2000, // Amount in cents, 2000 = 20 EUR. Must match line totals.
      "description": "test-1444",
      "lines":[
         {
            "name": "Some purchase - 20 EUR", // Max 100 characters.
            "category": "PREPAID-VOUCHER",
            "brand": "alphacomm",
            "quantity": 1,
            "amount": 2000
         }
      ]
   },
   "provider": "Buckaroo"
}

Responses and completion

After Buckaroo EPS Pay is invoked, behaviour depends on Buckaroo's outcome:

  • Immediate success – When Buckaroo returns a terminal success status (HTTP success and main Buckaroo status code indicating success without a payer redirect URL), Paymexx completes the transaction in one step and returns a JSON body that does not expose a payer URL. Your backend should rely on webhook and transaction status APIs as usual.
  • Redirect flow – When Buckaroo returns a redirect URL (payer action at the bank), the create response includes a payer URL and the payment stays pending until return or push status updates.

Always consult the original provider payload stored on the transaction for full Buckaroo diagnostics and troubleshooting.

Buckaroo sandbox

In Buckaroo EPS integration, issuer and EPS behaviour are driven by Buckaroo test data and merchant configuration.

For environment setup and issuer behaviour, coordinate with Paymexx and use Buckaroo's test console as documented in their EPS guide.

Merchant Configuration

  • guid - Buckaroo account (set by devs)
  • key - Buckaroo account (set by devs)
  • secret_key - Buckaroo account (set by devs)
  • store_name - Merchant display name configured for Buckaroo