# Enable and restrict payment methods for persons and countries

Restricting the payment options in the application is necessary in some situations. In Converia, there are various ways of mapping these restrictions. The configuration options are described below using two application examples.

## Case studies

### 1. Activate payment method with a voucher

**Use case:** Credit card payment is the only payment method offered. If necessary, people who are unable to pay by credit card should contact the event organizers to enable payment by bank transfer. In this case, the one-time payment by bank transfer can be implemented using a voucher code.

#### **Procedure**: 

* The payment method, which can only be activated via a voucher, must be **activated** and **not visible** (Fig. 1).

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2F4tFzEp5XbNiY5ryxGr8V%2Fimage.png?alt=media&#x26;token=4083221b-1789-4fe9-b63d-10752ed9e0af" alt="Fig. 1: Configuration of a hidden payment method"><figcaption><p>Fig. 1: Configuration of a hidden payment method</p></figcaption></figure>

* Make sure to enter a valid start- and end-date respectively
* Create a voucher category that makes the hidden (invisible) payment method visible (Fig. 2).

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2Fk3p7njSHYjeC9LalLc3Z%2Fimage.png?alt=media&#x26;token=f8e5eef0-1002-4f4d-b778-056b2f71ec52" alt=""><figcaption><p>Fig. 2: Create a voucher-category, which makes a hidden payment method visible</p></figcaption></figure>

* Create the desired number of vouchers and send them to the persons concerned.

### 2. Restriction of the payment method to countries and groups of people

PayPal charges different fees depending on the country in which the payment is made. These fees are to be charged as incidental payment costs for bookings from the respective countries.

#### **Procedure**:

In the tab *Limit payment method*, you can select whether the payment method should be restricted to a **price group** or a **country**, i.e. all countries/price groups in which this payment method should be available, must be selected (Fig. 3).

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FYmEAeqZHqrYe8RuyggrM%2Fimage.png?alt=media&#x26;token=dcae8af8-0a44-4b2a-b92e-834e3c7f8c5b" alt=""><figcaption><p>Fig. 3: Limiting the payment method to certain countries</p></figcaption></figure>

* The payment method itself is configured as usual, apart from the restriction.
* A payment type can be created for each charge rate, which is restricted to the corresponding countries.
* Different *internal names* should be used, so that the payment types can be distinguished. In the frontend, however, the name of the payment type can be uniformly named.