> For the complete documentation index, see [llms.txt](https://eavio.gitbook.io/eavio-club/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eavio.gitbook.io/eavio-club/functionalities/payment-methods.md).

# Payment Methods

The **eAvio** payment system revolves around a **Wallet-based billing model** that keeps funds in the hands of organizations while supporting multiple funding options, flexible billing models and automated notifications.

{% hint style="warning" %}
**eAvio is not a payment intermediary.** All transactions occur directly between the user and the organization.
{% endhint %}

The eAvio platform provides a complete financial and billing system for:

* Aero clubs
* Flight schools
* Small air tour operators

***

## Wallet (Account Balance)

Every user has a **Wallet** associated with their organization. The Wallet enables:

* Deposit funds for prepaid operations
* Purchase and use packages
* Track transactions and download invoices
* Receive internal credits for services provided

Funds can be added to the Wallet in several ways:

* [ ] Self-deposit – the user adds funds
* [ ] Authorized deposit – an organization administrator adds funds
* [ ] Member-to-member transfer – if allowed

***

## Funding Methods

{% tabs %}
{% tab title="Bank Transfer (SEPA)" %}

1. **Prepaid deposit (advance payment)**
   * A pro forma invoice is issued.
   * After the transfer is received, the Wallet is credited.
2. **Payment for already invoiced services or flights**
   * A standard invoice is issued immediately.
   * No pro forma invoice is generated.
     {% endtab %}

{% tab title="Stripe Payments" %}

* Organizations connect their own Stripe account.
* Supported methods include credit/debit cards, Apple Pay and Google Pay.
* Funds are credited directly to the organization's Stripe account and reflected in the Wallet.
  {% endtab %}

{% tab title="Recurrent SEPA Payments" %}

* Users link their bank account for automatic payments.
* After an invoice is issued, funds are withdrawn automatically.
* A pre-notification is sent a few days before the withdrawal.
* If no dispute is raised, the payment executes automatically.
* This method usually has the lowest Stripe fees.
  {% endtab %}
  {% endtabs %}

***

## Billing Models

{% tabs %}
{% tab title="Prepaid Model" %}

* Users deposit funds to their Wallet in advance.
* A pro forma invoice is issued for the deposit.
* Funds can then be used for flights, packages or services.
  {% endtab %}

{% tab title="Pay-Per-Flight" %}

* After a flight log is submitted, the system calculates the charge.
* The user receives an invoice, payable via bank transfer or Stripe.
  {% endtab %}

{% tab title="Monthly Cumulative" %}

* Users receive informational receipts for individual flights.
* At the end of the month, a cumulative invoice for all flights/services is issued.
* If recurrent SEPA is enabled, the invoice is paid automatically after pre-notification.
  {% endtab %}
  {% endtabs %}

***

## Packages (Memberships, Training & Flight Packages)

Organizations can create and manage packages for their users:

* Memberships – valid for a specific time period
* Flight minute packages – deduct flight time from prepaid minutes
* Launch packages – e.g., 60 glider launches
* Training packages – tailored for flight schools
* Custom packages – for any other products or services

### Sellable Packages

Each package has a **Sellable** property:

* **Sellable = Yes** → visible to all users on the front-end, available for purchase
* **Sellable = No** → visible only to authorized personnel, who can manually activate it for a user

***

## Organization-Specific Configuration

### Bank Accounts

Organizations can configure single or multiple bank accounts, typically separated by operation type (motor aircraft, gliders, parachuting, ultralight aircraft).

### Stripe Accounts

Each operational section can have its own Stripe account, allowing each section to manage its finances independently.

### Internal Service Payments

Users such as instructors can receive credit to their Wallet for services and later use it for flights or other services.

### Invoice Customization

Organizations can tailor invoices with a custom header and footer. Configure the `invoice_header` and `invoice_footer` parameters in [Payments settings](https://github.com/eAvio/eavio-gitbook/blob/master/settings/payments/README.md) to brand documents with organization-specific details.

***

## Notifications

Users automatically receive notifications for key financial events:

* Negative Wallet balance
* Overdue invoices
* Upcoming SEPA direct debit charge
* Successful payments and fund deposits

More details are available on the [Notifications page](/eavio-club/notifications/notifications.md).

***

## Configuration Parameters

<details>

<summary>Payment-related parameters</summary>

| Parameter                  | Description                                            |
| -------------------------- | ------------------------------------------------------ |
| `iban`                     | Main IBAN number used for bank transfers               |
| `iban_power`               | IBAN number for the power section                      |
| `iban_glider`              | IBAN number for the glider section                     |
| `iban_ultralight`          | IBAN number for the ultralight section                 |
| `iban_parachute`           | IBAN number for the parachute section                  |
| `stripe_secret_power`      | Secret key for power section credit card payments      |
| `stripe_secret_glider`     | Secret key for glider section credit card payments     |
| `stripe_secret_ultralight` | Secret key for ultralight section credit card payments |
| `stripe_secret_parachute`  | Secret key for parachute section credit card payments  |
| `enable_card_payment`      | Enables credit card payment through Stripe             |
| `combine_section_accounts` | Use one account/balance for all sections               |

</details>

For a full list of payment-related parameters, see the [Payments settings](https://github.com/eAvio/eavio-gitbook/blob/master/settings/payments/README.md) page.