Payment gateways
Payments can be connected via configured payment providers such as Stripe, Computop or PayPal.
For payments, finance, validation, SSO, communication, shipping and partner services
Connect tebio with payment providers, communication interfaces, shipping services, validation services, identity verification, e-signature processes, SSO, DATEV, house banks and other systems. The tebio platform supports pre-integrated services, configurable partner integrations and structured data formats for downstream processes.
Not every connection works the same way. tebio distinguishes between payment gateways, communication services, shipping services, partner services, validation services, identity and SSO processes, and data formats for downstream systems.
Payments can be connected via configured payment providers such as Stripe, Computop or PayPal.
E-mails to customers are sent on behalf of the respective tebio platform user. SMTP or Microsoft Graph can be configured for this. For postal or hybrid document communication, the E-POSTBUSINESS API can be used.
For orders that include goods, DHL can be connected to create shipping labels directly from the order process.
External services such as Endereco or Pxl Vision can support processes for address validation, identity verification or signatures.
Keycloak supports login, authentication and SSO scenarios so that tebio can be connected with existing identity providers and central access processes.
tebio can use external or rule-based checks, for example VIES for VAT ID validation or IBAN validation based on official rules.
For DATEV and house banks, tebio can provide data in specific formats, for example DATEV export, pain.008 and pain.001 files.
Your own systems can be connected to tebio via API and Webhooks to process customer, subscription, billing, payment, document or shipping events.
tebio can connect payment gateways to link payment processes with subscription management, billing, Hosted Pages and finance processes. Actual use depends on the respective provider, contract, account, approval and configuration.
Stripe can be connected as a payment gateway, among other things for digital payment processes and the payment methods available depending on your Stripe configuration.
Computop can be used as a payment gateway for credit card payments and recurring payment processes, provided the corresponding access has been set up.
PayPal can be used for PayPal payments. Recurring subscription payments may require additional approvals for the PayPal merchant account.
Customer communication from tebio should match the brand and sender identity of the respective company. That is why e-mails to customers are sent on behalf of the tebio platform user. SMTP or Microsoft Graph can be configured for this.
E-mail delivery
SMTP can be configured to send customer e-mails via the platform user's e-mail infrastructure. As a result, e-mails appear in the name of the respective company and not as generic tebio communication.
E-mail delivery
Microsoft Graph can be used to send customer e-mails via the platform user's Microsoft 365-based e-mail infrastructure, provided it has been set up accordingly.
Letter and document communication
tebio can use the Deutsche Post E-POSTBUSINESS API for document and communication processes, for example when companies want to include postal or hybrid delivery processes in their customer communication.
Shipping & fulfillment
If goods are sold via tebio, the DHL integration can be used to create shipping labels directly for incoming orders. This lets you connect goods processes with the order, customer, address, documents and shipping.
The DHL integration complements subscription management and billing wherever shipping goods is part of the business model — for example for physical products, bundles, hardware, starter kits or accompanying deliveries of goods.
Address validation
Endereco can be used for address checks and autocomplete. This allows address data in order, customer or registration processes to be validated and completed.
Identity verification & signature
Pxl Vision can be used for identity verification and qualified electronic signatures in suitable processes. This lets you connect digital onboarding, verification or signature processes with tebio workflows.
Identity & SSO
tebio uses Keycloak as the identity and access layer for login and authentication processes. This allows suitable SSO scenarios to be implemented with existing identity providers, provided they are configured accordingly.
This can be particularly relevant for companies with central user management: employees, customers or partners should not have to log in to every system separately, but should be able to access tebio-related applications through existing identity processes.
VAT ID validation
tebio can use the EU's VIES VAT number validation to check VAT identification numbers in a European context. This is particularly relevant for B2B customers, cross-border EU transactions and tax-relevant customer classifications.
IBAN validation
tebio can validate IBANs based on the official bank sort code directory and the IBAN rules of the Deutsche Bundesbank. This allows bank details in payment processes, SEPA procedures and customer master data to be checked.
DATEV export
tebio can provide billing and financial data in DATEV-relevant formats. This allows invoices, booking data and billing-related information to be prepared for downstream accounting and tax advisor processes.
SEPA file · House bank procedure · Export format
For established B2B payment processes, tebio can provide files for further processing by house banks. This is particularly relevant for companies that use SEPA direct debit or SEPA bank transfer via their own bank account.
pain.008 files can be used for SEPA direct debit processes. Companies can use them to process direct debits further via their own bank.
pain.001 files can be used for SEPA bank transfer processes. Companies can use them to process bank transfers further via their own bank.
In tebio, integrations are not isolated. They connect with customers, subscriptions, orders, invoices, payments, documents, identity processes, communication processes, shipping processes and events. This allows external services to be used exactly where they are relevant in the process.
Endereco, payment gateways and Hosted Pages can support digital order processes.
Address validation, IBAN validation and VAT ID validation can improve the quality and usability of customer data.
SMTP or Microsoft Graph can be configured for e-mail delivery on behalf of the platform user. The E-POSTBUSINESS API can complement this with postal or hybrid document communication.
DHL can be used to create shipping labels for incoming orders that include goods directly from tebio.
Keycloak can support login, authentication and SSO scenarios when tebio is to be connected with existing identity providers.
Pxl Vision can support identity verification and signature processes in suitable workflows.
DATEV export, pain.008 and pain.001 support downstream accounting and house bank processes.
Some integrations can be configured directly in tebio. Others require separate contracts, credentials, approvals or technical setup with the respective provider. Which integrations make sense for a company depends on the business model, payment processes, customer type, identity provider, shipping processes and downstream systems.
tebio supports integrations and formats in several areas: payment gateways such as Stripe, Computop and PayPal, e-mail delivery via SMTP or Microsoft Graph, communication processes via the E-POSTBUSINESS API, DHL shipping labels for orders that include goods, address validation with Endereco, identity verification and signature processes with Pxl Vision, login and SSO scenarios via Keycloak, VAT ID validation via VIES, IBAN validation, DATEV export and SEPA files such as pain.008 and pain.001 for house bank procedures.
Stripe, Computop and PayPal can be integrated into payment processes as payment gateways. Actual use depends on the respective provider, contract, account, approval and configuration in tebio.
E-mails to customers are sent on behalf of the respective tebio platform user. SMTP or Microsoft Graph can be configured for this, so that communication runs via the company's e-mail infrastructure.
No. Customer e-mails are sent on behalf of the platform user. tebio provides the processes; the e-mails are sent via the configured e-mail infrastructure of the respective company.
Yes. Microsoft Graph can be used to send customer e-mails via the platform user's Microsoft 365-based e-mail infrastructure, provided it has been set up accordingly.
Yes. SMTP can be configured to send customer e-mails via the platform user's e-mail infrastructure.
Yes. tebio can use the Deutsche Post E-POSTBUSINESS API for postal or hybrid document communication, provided it has been set up accordingly.
Yes. tebio can connect DHL for shipping goods, so that shipping labels can be created directly for incoming orders that include goods.
Yes. For orders that include goods, tebio can create shipping labels via the DHL integration, provided the integration has been set up accordingly.
No. tebio is neither an inventory management system nor a logistics system. The DHL integration supports shipping labels for orders that include goods, but does not replace full warehouse or shipping software.
tebio can support SSO scenarios via Keycloak. Actual use depends on the identity provider, the desired login process and the respective configuration.
Keycloak serves as the identity and access layer for login and authentication processes. It allows suitable SSO integrations with existing identity providers to be implemented.
Yes, suitable identity providers can be connected via Keycloak, depending on setup. This lets you connect login and SSO processes with existing IAM or identity provider structures.
No. SSO depends on the respective identity provider, the desired login flows and the technical configuration. The specific setup must be reviewed for each company.
Yes. tebio can use Endereco for address checks and autocomplete to validate and improve address data in customer, order or registration processes.
Yes. tebio can use the EU's VIES VAT number validation to check VAT identification numbers. This supports B2B processes, but does not replace a tax assessment.
Yes. tebio can validate IBANs based on the official bank sort code directory and the IBAN rules of the Deutsche Bundesbank. This supports payment processes and SEPA procedures.
tebio can use Pxl Vision for identity verification and qualified electronic signatures in suitable processes. Actual use depends on the setup and the respective process.
Yes. tebio can provide billing and financial data for DATEV export and downstream finance processes.
Yes. tebio can provide SEPA files such as pain.008 for direct debit processes and pain.001 for bank transfer processes. These files can then be processed further via the company's own bank.
No. pain.008 and pain.001 are file formats for SEPA payment processes. tebio can provide such files; the actual processing then takes place via the respective house bank process.
Yes. Via API and Webhooks, your own systems such as CRM, ERP, finance systems, customer portals, provisioning systems or data warehouses can be connected to tebio.
No. The availability of individual integrations depends on provider contracts, credentials, approvals, account configuration, process, country and business model.

Start for free with tebio or talk to us about which integrations, payment gateways, communication channels, shipping processes, validation services, SSO processes, DATEV exports, house bank files, API and webhook processes make sense for your business model.