For payment gateways, SEPA, bank transfer and payment status
Payments for recurring business models
Manage payment methods, payment gateways, SEPA direct debit, SEPA bank transfer, online payments, incoming payments, open items, failed payments and refunds directly in the context of customers, subscriptions and invoices.
Payments are more than a payment method at checkout.
In recurring business models, payment methods, invoices, incoming payments, failed payments, open items, refunds and customer communication must fit together. At the same time, different payment methods run through different channels: via payment gateways, via your own bank or as a documented external payment.
Payment providers & contract requirements
Payment gateways require separate contracts and credentials.
House bank procedures follow different flows than online payments at checkout.
Depending on the setup, SEPA direct debit can be used via your own bank or via a gateway.
Depending on the setup, credit card payments can run via Stripe or Computop.
PayPal requires additional approvals for recurring subscription payments.
Payment methods & payment processing
Payment methods must be enabled for the appropriate roles and touchpoints.
Incoming payments, open items and failed payments must remain traceable.
Refunds and corrections must be visible in the customer and invoice context.
Payment integration
External systems must be notified about payment events.
tebio connects payment methods, payment channels and billing processes.
With tebio, you configure which payment methods are available to your customers, internal teams or partners. The platform distinguishes between payment gateways such as Stripe, PayPal or Computop and house bank procedures such as external SEPA direct debit or external SEPA bank transfer.
In tebio, payment methods stay connected to customers, subscriptions, orders, invoices, incoming payments, open items, refunds, reports and Webhooks. This makes payments part of the entire subscription and billing process instead of an isolated checkout step.
Which payment methods does tebio support?
tebio supports payment methods through different channels. Payment gateways connect external payment providers. House bank procedures document or support payment processes via the company's own business account.
Payment gateways
Payment gateways process transactions via specialized payment service providers. This requires a separate contract with the respective provider and the necessary credentials.
Stripe
Stripe is connected via Stripe Connect. You connect your own Stripe account from the Business Portal. Depending on your Stripe activation, this enables credit card payments, Google Pay, Apple Pay, Klarna, SEPA direct debit with virtual IBANs and Amazon Pay.
PayPal
PayPal enables payments via a PayPal account. For recurring subscription payments, the Reference Transactions feature must be enabled for the PayPal merchant account.
Computop
Computop can be used as a gateway for common credit cards such as Visa, MasterCard and American Express and for automated recurring payments, provided the corresponding Computop access has been set up.
House bank procedures / external payments
With house bank procedures, the actual money transfer does not run directly through the portal. tebio documents these payments and, depending on the procedure, can generate bank files for further processing at your bank.
External SEPA direct debit
For SEPA direct debit via your own bank, details such as creditor ID, IBAN, BIC and account holder are stored. tebio can generate pain.008 XML files for further processing at your bank.
External SEPA bank transfer
For SEPA bank transfer, recipient, IBAN, BIC and bank name are stored. Customers receive this payment information at checkout as the destination for their transfer. tebio can provide corresponding bank files for this.
Other external procedures
If needed, other external payment documentation such as cash on delivery, point of sale or cash payment can be supported via interfaces.
Not every payment method is automatically available in every account, country, product or process. Availability and use depend on contracts, provider approvals, configuration, role permissions and business model.
Which payment method runs through which channel?
Payment methods differ not only in the customer experience but also in their technical and operational payment channel. This overview shows which methods can typically be used via payment gateways, Hosted Pages, your own bank or external payment documentation.
Important NoteNot identical to the external SEPA house bank procedure. Availability depends on Stripe activation and configuration.
House bank procedure
External SEPA direct debit
Processing PathHouse bank procedurevia your own bank account
Typical Customer Touchpoint
Business Portal
Hosted Pages
Self-Care or API, depending on role approval and process
Typical Use Case
Recurring fees
Subscriptions
Memberships
Subscription payments via your own bank
Important Notetebio can generate pain.008 XML files for processing at your bank. Payment actions such as Authorize, Capture, Cancel or Refund are not supported by the system for external payments.
External SEPA bank transfer
Processing PathHouse bank procedurevia your own bank account
Typical Customer Touchpoint
Checkout
Invoice
Customer communication
Self-Care or Business Portal
Typical Use Case
Invoice-based payments
Prepayment
B2B payments
Manual payment by customers
Important NoteCustomers receive the stored bank details as the payment destination. Incoming payments must be reconciled or finalized according to the selected status model.
External payment documentation
Cash on delivery
Processing PathExternalpayment documentation via interfaces
Typical Customer Touchpoint
External process
Typical Use Case
Special processes with payment on delivery
Important NoteSpecial case. Do not position as a standard checkout payment method.
Point of sale
Processing PathExternalpayment documentation via interfaces
Typical Customer Touchpoint
On-site payment / external POS process
Typical Use Case
On-site payments
Branch processes
Manual payment documentation
Important NoteSpecial case. The actual flow of money takes place outside of tebio.
Cash payment
Processing PathExternalpayment documentation via interfaces
Typical Customer Touchpoint
External or manual process
Typical Use Case
Manual payment documentation in special cases
Important NoteSpecial case. The actual flow of money takes place outside of tebio.
Enable payment methods for specific user groups
In tebio, you can define for each payment method which user groups can use it in the payment process. This lets you provide payment methods specifically for internal teams, customers in Self-Care, customers on the order page or sales partners.
Subscription management with full access
Account holder
Customer service
Customers in Self-Care / customer portal
Customers on the order page
Sales partners
If no roles are selected, the payment method is available to all authorized users. If a method is restricted specifically, the approval should match the intended process.
Payment method
Role-based approval
Business Portal / Self-Care / Order page / Sales partners
Payment process
From payment channel to payment status
tebio supports payment processes along the entire subscription lifecycle — from configuring the payment method via checkout, Self-Care, Business Portal or API to invoice, incoming payment, open item, refund, reporting and Webhooks.
1. Configure the payment method
Payment gateways or house bank procedures are set up in the Business Portal and provided with the required credentials, bank details or parameters.
2. Enable user groups
For each payment method, you can define whether it is available to internal teams, customers in Self-Care, customers on the order page or sales partners.
3. Use the payment method in the process
Depending on approval and process, the payment method can be used at checkout, in Self-Care, in the Business Portal or via API.
4. Connect the subscription or order
The payment method is connected with the customer, order, subscription and billing process.
5. Generate an invoice or receipt
Billing processes generate matching documents that stay connected with the customer, subscription and payment context.
6. Track payment status
Payment status, open items, failed payments and refunds stay visible in the customer and invoice context.
7. Trigger downstream processes
Reports, journal, customer communication, manual finalization or Webhooks can build on payment events.
Payment gateways for online payments and recurring payments
Payment gateways connect external payment providers. This requires a separate contract with the respective provider and the necessary credentials. tebio provides the configuration in the Business Portal and connects the payment processes with subscription management, billing and Finance.
Stripe Connect
With Stripe Connect, you can connect your own Stripe account with tebio directly from the Business Portal. Depending on activation in the Stripe account, credit cards, Google Pay, Apple Pay, Klarna, SEPA direct debit with virtual IBANs and Amazon Pay can be used.
Online checkout
Digital subscriptions
Credit card payments
Modern wallets and other payment methods supported by Stripe
PayPal
PayPal can be connected via client ID, client secret and merchant ID. For recurring subscription payments, PayPal must enable Reference Transactions for the merchant account.
PayPal payments in the online checkout and recurring payments, provided the required PayPal features are enabled.
Computop
Computop can be used as a gateway for common credit cards such as Visa, MasterCard and American Express and for automated recurring payments.
Credit card payments
Recurring payments and setups in which Computop is used as the payment service provider.
House bank procedures for SEPA and bank transfer
With house bank procedures, the actual money transfer runs through the company's own bank account. tebio documents these payments and, depending on the procedure, can generate bank files for further processing at your bank.
For external payments, payment actions such as Authorize, Capture, Cancel or Refund are not supported by the system. The payment process is documented and evaluated in the portal according to the status model.
Customer
Payment method: external SEPA
Subscription / invoice
Bank file / payment information
House bank
Payment status in the portal
Report / journal / downstream process
Use your own bank account
SEPA direct debit and SEPA bank transfer can be handled via the company's bank account.
Prepare SEPA direct debit
For external SEPA direct debit, you can configure creditor ID, IBAN, BIC, account holder, batch booking and direct debit schemes such as CORE or B2B.
Generate bank files
tebio can provide pain.008 XML files for SEPA direct debit and bank files for SEPA bank transfers, which can be used in the further process at your bank.
Control the status model
The status model lets you define whether external payments are documented as successful immediately or kept as pending first and finalized later.
Track payments in the Business Portal
Finance, support and operations can review payment processes in the Business Portal in the context of customers, subscriptions and invoices. This makes payment methods, incoming payments, open items, failed payments, status models and refunds traceable.
Configure payment methods
Payment gateways and house bank procedures can be set up and managed in the invoicing and invoices area.
Enable payment methods
Role-based permissions let you control which user groups can use a payment method.
Track incoming payments
Incoming payments can be reviewed in the context of invoice, customer and subscription.
Identify open items
Outstanding amounts stay visible and can be used for clarification, communication or downstream processes.
Handle failed payments
Failed payments can be identified and handled further in the customer context.
Record refunds
Refunds can be documented and tracked in the payment context, provided the respective payment channel supports this.
Payments, billing and Finance belong together
In tebio, payments are connected with billing, invoices, receipts, refunds, journal, financial reports and DATEV-ready processes. This means payment information doesn't have to be viewed separately from subscription and invoice data.
Via API and Webhooks, payment data, payment methods, payment status and payment events can be connected with external systems. Depending on your integration needs, configuring payment methods or retrieving generated SEPA files can also be automated.
The tebio documentation shows step by step how payment methods, payment gateways, house bank procedures, role approvals, payment status, invoices, incoming payments, refunds, Hosted Pages and integrations are used.
tebio supports payment methods via payment gateways and house bank procedures. Payment gateways include Stripe, PayPal and Computop. House bank procedures include external SEPA direct debit and external SEPA bank transfer. In addition, other external payment documentation such as cash on delivery, point of sale or cash payment can be supported via interfaces if needed.
Which payment methods run via Stripe?
Stripe is connected via Stripe Connect. Depending on activation in the connected Stripe account, credit card payments, Google Pay, Apple Pay, Klarna, SEPA direct debit with virtual IBANs and Amazon Pay can be used via Stripe.
Which payment methods run via PayPal?
PayPal enables payments via a PayPal account. For recurring subscription payments, PayPal must enable Reference Transactions for the merchant account.
Which payment methods run via Computop?
Computop can be used for common credit cards such as Visa, MasterCard and American Express and for automated recurring payments, provided the corresponding Computop access has been set up.
Which payment methods run via our own bank?
External SEPA direct debit and external SEPA bank transfer can be handled via the company's own bank account. With these procedures, tebio documents the payment process and, depending on the procedure, can generate bank files for further processing at your bank.
Is SEPA direct debit always the same?
No. Depending on the setup, SEPA direct debit can be used in different ways: as external SEPA direct debit via your own bank or via Stripe with virtual IBANs. These channels differ in processing, configuration and payment status.
Can payment methods be shown only to specific user groups?
Yes. Payment methods can be enabled based on roles, for example for subscription management, account holders, customer service, customers in Self-Care, customers on the order page or sales partners.
Is tebio a payment service provider?
No. tebio is not a pure payment service provider solution. tebio connects payment processes with subscription management, billing, invoices, open items, refunds, reports, Hosted Pages, API and Webhooks.
Can incoming payments and open items be tracked in the portal?
Yes. Incoming payments, open items, failed payments, refunds and payment status can be tracked in the Business Portal in the context of customers, subscriptions and invoices.
Are all payment methods available automatically?
No. The availability of individual payment methods depends on provider contracts, credentials, approvals, account configuration, role permissions, process, country and business model.
Does tebio support recurring payments?
Yes. tebio supports recurring payment processes in the context of subscriptions. Depending on the payment channel, different prerequisites apply, for example PayPal Reference Transactions, a configured Stripe or Computop gateway or configured SEPA procedures via your own bank.
Can payment events be transferred to external systems?
Yes. Via API and Webhooks, external systems can react to relevant payment, billing, invoice or subscription events.
Ready for payment processes that fit subscription billing?
Start with tebio for free or talk to us about how you can connect payment gateways, SEPA via your own bank, online payments, invoices, payment status, open items and finance processes in one platform.