Skip to content

Payment gateway integration for recurring billing

Use plug-ins to integrate with your preferred payment gateway.

Your customers keep paying the way that works for your business. OpenBRM handles payment processing for every invoice — card, direct debit, EFT or cash bill payment — and collects payments automatically, and you can add localised gateways — or any gateway of choice — as time goes on.

Card payment processing & recurring payments

Authorize.Net, PayPal, FirstData, Chase Paymentech, DIBS, PayWay, PaymentsGateway, eWAY

Authorize.Net, PayPal and FirstData work out of the box: charge cards on each billing cycle for subscriptions, plans and usage invoices.

Direct debit

Ezidebit, Westpac

Collect from bank accounts on a schedule, with settlement files for reconciliation.

Instant EFT

PayFast

Card and instant EFT, popular with ISPs and telecom customers in South Africa.

Cash bill payment at retail stores

EasyPay

Let customers pay bills in cash at retail outlets, posted back to the account.

Bank payment collection

Nedbank, Westpac

Bank-level collection and settlement files matched to invoices.

Built into payment processing

  • Card tokenisation — card details are stored as gateway tokens, so recurring charges run without storing card numbers.
  • Automatic payment retries — failed recurring payments are retried automatically, reducing involuntary churn and manual follow-up.
  • Recurring billing — subscriptions, one-off charges and rated usage are collected on each customer’s own billing cycle.
  • Payments posted to invoices — every amount received is recorded against the customer account and invoice, ready for CRM and accounting.

CRM billing integration

Keep sales, support and billing working from the same customer records.

For CRM integration, connect OpenBRM billing to the CRM your team already uses, or use the built-in CRM. Customer accounts created in the CRM can be billed in OpenBRM, and invoices and payments stay visible to sales and support.

  • vTiger CRM — accounts, leads and tickets kept in sync.
  • SugarCRM — customer records and opportunities linked to customer accounts.
  • SuiteCRM — open source customer accounts and contacts shared both ways.

SOAP and REST billing API

Set up OpenBRM to communicate fluidly with your own application.

OpenBRM is built on open source standards, so integrating is fast. Many RDBMS vendors already run it, which means you can read billing data straight from your application. Customers, products, orders, invoices, payments, billing runs and mediation are available through the SOAP and REST billing API — SOAP for secure external integration, REST for internal application integration.

TM Forum Open API mapping for telecom billing

OpenBRM's REST and SOAP APIs are organised around the same business entities as the TM Forum Open APIs — customers, accounts, product catalogue, orders, usage, bills and payments. OpenBRM is not a certified TMF Open API implementation, but because the core domains are exposed through its REST and SOAP APIs, a thin adapter layer can present these domains in TMF shape to an ODA-style architecture. That keeps TMF Open API billing work small: a TM Forum Open API telecom stack talks to the adapter, and the core stays unchanged.

OpenBRM areaRelated TM Forum Open API
Customers & billing accountsTMF629 Customer Management · TMF666 Account Management
Products, plans & pricingTMF620 Product Catalog Management
Orders & subscriptionsTMF622 Product Ordering · TMF637 Product Inventory
Rated usage (OpenRate)TMF635 Usage Management
Invoices & bill itemsTMF678 Customer Bill Management
Payments & payment methodsTMF676 Payment Management · TMF670 Payment Methods
Support tickets (CRM)TMF621 Trouble Ticket
SIM, MSISDN & device inventoryTMF639 Resource Inventory Management (managed in the application today; not yet exposed through the REST API)

TMF678 Customer Bill Management API

Invoices and bill items in OpenBRM cover the same entities as the TMF678 Customer Bill Management API: customer bills, their line items and the billing account they belong to. Both are available through the REST and SOAP APIs, so a thin adapter can present them in TMF678 shape. OpenBRM is not a certified TMF implementation.

See the documentation for the API reference, how OpenBRM works as an open source BSS, or how it compares with Oracle BRM, whose REST Services Manager exposes TMF-compliant endpoints.

Integrated third-party software

Live integrations shipped with the platform, covering CRM, accounting, banking, card processing, network access and CMS storefronts.

vTiger CRM integration

vTiger CRM

CRM — accounts, leads and tickets in sync

SugarCRM integration

SugarCRM

CRM — customer records and opportunities

SuiteCRM integration

SuiteCRM

CRM — open source customer accounts and contacts

Westpac integration

Westpac

Banking — direct debit and settlement files

Nedbank integration

Nedbank

Banking — payment collection

eWAY integration

eWAY

Payment gateway — cards and recurring payments

Ezidebit integration

Ezidebit

Payment gateway — direct debit collection

PayFast payment gateway integration

PayFast

Payment gateway — card and instant EFT

EasyPay integration

EasyPay

Bill payment — cash payments at retail stores

KashFlow integration

KashFlow

Accounting — invoices and ledger posting

Joomla integration

Joomla

CMS — storefront and customer portal

WordPress integration

WordPress

CMS — storefront and customer portal

RADIUSdesk integration

RADIUSdesk

Network access — RADIUS for ISPs and Wi-Fi hotspots

Need something that is not on this list? Tell us what you run — most integrations are a few days of work.

Payment gateway and billing integration: common questions

Authorize.Net, PayPal, FirstData, Chase Paymentech, DIBS, PayWay, PaymentsGateway, eWAY, Ezidebit, PayFast and EasyPay, plus bank collection with Westpac and Nedbank. Other gateways can be added as plug-ins.

Yes. Card details are stored as gateway tokens and charged automatically on each customer’s billing cycle for subscriptions, one-off charges and usage.

OpenBRM retries failed recurring payments automatically, so fewer customers lapse because of a temporary card or bank problem.

Yes. Direct debit is available through Ezidebit and Westpac, instant EFT through PayFast, and cash payments at retail stores through EasyPay.

Yes. Gateways are plug-ins, so a local gateway can be added. Tell us which one you use and we will scope the integration.

vTiger CRM, SugarCRM and SuiteCRM integrate with OpenBRM, and OpenBRM also includes a built-in CRM for accounts and support tickets.

Yes. Customers, products, orders, invoices, payments, billing runs and mediation are available through SOAP and REST APIs — SOAP for secure external integration, REST for internal application integration.

OpenBRM is not a certified TMF Open API implementation, but its REST and SOAP APIs cover the same billing domains, such as TMF620, TMF622, TMF635, TMF676 and TMF678, so a thin adapter layer can present them in TMF shape.

Ready to get started with OpenBRM?

Download the package and run it yourself, or ask us for a hosted trial account.

Open source and self-hostable — no licence cost.