Skip to content
A
For administrators
Running the administration — content, users, e-shop, invoicing and settings
Payments / Regions and callbacks

Regions and callbacks#

Two different things. A region says who can pay by what. A callback says what happens once they have paid.

Payment regions#

A region is a group of countries with a shared currency and a shared set of gateways.

Field Meaning
Name per language
Currency what the region pays in
Country picked from Systém → Regiony — can be one specific country, but also a wider group (e.g. "rest of the EU")
Default used when the country is not recognised
Default document language which language invoices to this region come out in
Active

Without a default region, a visitor whose country is not recognised cannot pay

They see no gateway and stall in the cart. One region must be marked as the default — always.

The region and documents#

The payment region also decides how an invoice looks.

What How
The document language the Výchozí jazyk dokladů field; a customer can override it with their own setting
The PDF layout the region is one of the axes of the layout matrix

The same matrix can also be filled in right here, on the region — it carries two tabs for a VAT-registered and a non-registered seller; the rows are buyer types, the columns invoice types.

Set the language on the region, the exceptions on the customer

Do you normally invoice Germany in English? Set it once on the region. Want one German client in Czech? That belongs on their customer card, not in switching the region.

Prices by region#

Tariffs carry a price for each combination of region, gateway and currency. The same applies to e-shop price lists.

A missing price means the item is not offered in that region

No error is shown — it simply is not there. After adding a region, go through the prices.

Callbacks#

A callback is the handler called after a payment status changes. It is what moves the order on, pays for the advert and extends the membership.

Field Meaning
Service name what it concerns
Key the designation the payment carries
Handler the code that runs

Callbacks are system configuration, not content

They are written when a module is set up and should be changed only by someone who knows what they are doing. A deleted callback means paid payments after which nothing happens — the customer pays and gets nothing.

Return and notification addresses#

A payment carries three addresses:

Address Purpose
Success where the customer returns after paying
Cancel where they return if they click out
Notification where the gateway sends its confirmation

The notification address decides, not the return one

The customer may not come back at all. When the notification address does not work, payments hang in "started" even though they are paid. You recognise it by a pile of started payments on one gateway.

The gateway must be able to reach the notification address from outside

On a local or development server behind a corporate network the confirmation never arrives and payment testing there does not work.

When payments stay in "started"#

  1. Check the communication with the gateway on the payment.
  2. Verify the system is reachable from the internet.
  3. Check that the correct notification address is set on the gateway.
  4. Some gateways let you resend the confirmation from their own administration.