Skip to content

Prepaid and postpaid in comparison

In tebio, subscription products can be configured as Prepaid or Postpaid depending on the business model. The selection determines when services are billed, which payment logic is used and which documents are generated for customers.

The difference is fundamental:

  • Prepaid: The customer pays in advance for a future service period.
  • Postpaid: The customer uses the service initially, billing takes place subsequently or at a defined billing time.

The choice of prepaid or postpaid affects product configuration, payment process, invoicing, billing documents and customer communication.

Prepaid is suitable if a service is only to be provided after successful payment.

Typical examples are:

  • digital subscriptions with immediate access after payment
  • Prepaid memberships
  • Media or SaaS subscriptions with monthly or annual prepayment
  • Credit models or time-limited service packages
  • Products for which payment defaults should be avoided as far as possible

With prepaid, payment is at the beginning of the process. Only when payment has been successfully completed can the service be provided or the subscription activated.

Postpaid is suitable if services are initially provided and then billed.

Typical examples are:

  • Business customer contracts with monthly invoices
  • usage-based billing
  • Telecommunications or service provider models
  • B2B subscriptions with payment by invoice or SEPA direct debit
  • Billing for multiple subscriptions on a single invoice
  • Business models with approval processes before invoicing

At Postpaid, the focus is on service provision. The invoice or billing document is generated at a later point in time, for example as part of a regular billing run.

topicPrepaidPostpaid
Time of paymentBefore the service or at the beginning of the service periodAfter the service or at a defined billing time
Typical payment processDirect payment at checkoutInvoice, SEPA direct debit or downstream payment
Typical payment methodsCredit card, PayPal or other direct payment methodsBank transfer, SEPA direct debit or other configured payment methods
DocumentsOften a receipt or proof of paymentOften invoice
Risk of payment defaultsLower because payment takes place before performanceHigher because performance can occur before payment
Typical target groupB2C, self-service, digital productsB2B, contracts, complex billing
Suitable for usage-based billingOnly limited, depending on the modelOften suitable
Approval process before invoicingUsually not necessaryOptionally possible
Typical entryHosted page or self-care / customer portalBusiness portal, API or regular billrun

For both models, a subscription is usually created through an order.

The difference lies in how tebio handles payment and billing.

With prepaid, payment is typically initiated directly during the ordering process. The customer chooses a payment method, confirms the payment and then receives access to the booked service.

This is particularly suitable for ordering processes via hosted pages, where customers can place the order themselves and use payment methods that require active confirmation.

Examples:

  • Credit card
  • PayPal
  • other direct online payment methods

If payment fails, the order cannot be completed successfully or the subscription cannot be activated.

With Postpaid, the order can also be completed without direct online payment. Billing is then carried out using the configured invoicing logic.

This is particularly suitable for business customers, manual order entry in the business portal or API-controlled processes.

Examples:

  • Invoice with bank transfer
  • SEPA direct debit
  • regular invoice run
  • Approval process before final invoicing

Prepaid and postpaid also differ in which billing documents typically arise.

With Prepaid, a payment voucher or receipt is often generated because the payment is made in connection with the order or the start of the service period.

With Postpaid, an invoice is typically generated because services are billed subsequently or periodically.

Which specific documents are created depends on the product configuration, the payment strategy, the invoice settings and the invoicing configuration.

The ongoing subscription lifecycle is also influenced by the billing model.

With prepaid, the decisive factor for extending a subscription is often whether the next payment can be made successfully. If a payment fails, depending on the configuration, this may affect the renewal, status or service provision.

With postpaid, the subscription can continue while open invoices or incoming payments are checked and processed separately. This is particularly relevant for business customer processes in which payment deadlines, dunning processes or manual checks play a role.

Prepaid is often used in B2C-related scenarios because customers pay directly and then use the service.

Postpaid is often used in B2B-related scenarios because business customers usually need an invoice, a payment term, an order number, a project reference or a release process.

However, the decision for prepaid or postpaid is not exclusively tied to B2C or B2B. B2B customers can also book prepaid products, and B2C scenarios can also be billed postpaid if the business model requires it.

Prepaid and postpaid must be distinguished from the basic tax configuration of the account.

The selection of the primary target group during registration determines whether prices are managed gross or net:

  • For private customers (B2C) prices are managed and displayed gross.
  • For Business customers (B2B) prices are managed and displayed net.

This setting is independent of whether a product is configured as prepaid or postpaid.

Important: Whether e-invoices can be created does not only depend on prepaid or postpaid, but in particular on the account configuration, the billing model and the invoice settings.

Use Prepaid if:

  • Customers should pay before using the service
  • Payment defaults should be avoided as far as possible
  • the checkout should take place via hosted pages or self-care / customer portal
  • digital products are provided immediately after successful payment
  • the process should be as close as possible to classic e-commerce

Use Postpaid if:

  • Services are initially provided and billed later
  • Business customers should receive invoices with payment terms
  • several services or subscriptions should be billed collectively
  • an approval process is required before invoicing
  • Usage-based or complex billing models are used

Don’t just see prepaid and postpaid as payment methods

Section titled “Don’t just see prepaid and postpaid as payment methods”

Prepaid and postpaid are not payment methods. They describe the billing logic of a product.

The specific payment method, for example credit card, PayPal, SEPA direct debit or bank transfer, is configured separately.

Prepaid often produces receipts or payment receipts, while postpaid often produces invoices. However, the actual document creation depends on your configuration.

Distinguish between hosted pages and manual orders

Section titled “Distinguish between hosted pages and manual orders”

Payment methods such as credit card or PayPal usually require active confirmation from the customer. This makes them particularly suitable for orders via hosted pages or the self-care/customer portal.

If you enter an order on behalf of a customer in the business portal, usually only payment methods are available that can be used without active customer approval.

Usage-based billing is usually more of a postpaid scenario because the actual usage is only known afterwards.

If usage-based billing is required, the configuration should be coordinated with the tebio team as part of a project.

Prepaid and postpaid are not viewed in isolation as a payment method in the API, but rather depend on the product and billing logic.

The following areas are particularly relevant for API users:

areaMeaning
Product/Product Price ListDefinition of product, price, term and billing logic
OrderInitiation of an order and creation of the subscription
SubscriptionCurrent status of the booked service
Invoice / ReceiptGenerated billing documents
PaymentPayment, payment status and refund
Usage/meteringTransmission of consumption data for usage-based billing

The technical details can be found in the separate API reference.