Payment Methods

Manage deposits, invoices and packages with flexible wallet-based billing.

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.

eAvio is not a payment intermediary. All transactions occur directly between the user and the organization.

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

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.

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.

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.

---

Billing Models

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.

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.

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.

---

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 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.

---

Configuration Parameters

Payment-related parameters

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

For a full list of payment-related parameters, see the Payments settings page.