Page tree
Skip to end of metadata
Go to start of metadata

This guide explains how you to can use the Direct Carrier Billing (DCB) or the other payment options available through the Bango Platform.

You will need to establish a commercial agreement with Bango and you will need to have commercial agreement from the payment routes you want to use through the Bango platform.

Bango Platform Flexibility  

The Bango Platform enables you to integrate once, then activate multiple payment routes through the single integration. You can quickly grow your base of paying customers beyond credit card, especially in places where credit card and bank account adoption is low, without having to schedule development time or learn new technologies or authentication methods.

Develop and code your integration once and then activate multiple payment routes as soon they are commercially attractive to you. Activation is by simple configuration changes made within the Bango Platform.

The uniquely flexible architecture of the Bango Platform provides you standardized access to all payment routes that are available now or which might be developed in the future. Payment routes already supported include all variants of DCB, operator provided non-airtime wallets and mobile money Mobile Network Operator (MNO) independent wallets. Existing pre-integrated payment routes are quickly configured and activated when required. 

Bango technology actively encourages payment innovation by both merchants and payment providers (e.g. mobile operator). The innovative architecture, which is based on experience over 4 previous generations of payment platform, quickly supports the latest methods of authentication, payment experiences, and security requirements. By delegating the handling of diversity and complexity of the wide range of possible client types and user flows to the Bango Platform you can deploy new identity methods without having to make any coding changes to your applications. Existing models such as mobile network identification (typically header enrichment), SMS or two factor authentication flows, open identity standards (OpenID, oAuth), or custom identity standards are already supported. The architecture is designed to handle innovations in the future which might include (but is not limited to) biometrics, proximity, speech authentication or behavioral. 

New payment routes are being added all the time. They automatically appear for activation in Bango Grid - your view into the universe of alternative payment routes around the world. 

The Bango Platform also separates user identity from their multiple billing credentials, allowing a payment to be made based on a wide range of user credentials, not just their phone number (MSISDN) alone. Bango provides you with a tokenized ID so you don't need to worry about PCI compliance or Mobile Operator Audits and privacy requirements.

Separation of user authentication and consent from payment transactions also enables you to manage subscriptions, split sales and physical goods if you want, without re-coding your Bango API integration.

The Bango Platform handles refund operations and provides a rich API to allow detailed inspection of historic or active transactions. 

Technical Capabilities of the Bango Platform

When you integrate with Bango using the Bango API and guidelines, you simply provide the Bango Platform with the high level requests to authenticate, bill or refund a user. The Bango Platform maps these requests to the wide variety of underlying payment provider systems. The Bango Platform will map your request to the best possible payment provider side operations to achieve the functions you require. If a payment provider cannot implement your request, the Bango Platform will automatically apply steps to achieve an equivalent result or return a useful response code.

The Bango Platform handles the following common situations, whether you offer your users a native app or an HTML website:

  1. When a DCB operator changes its protocols, URLs, identification MSISDNs etc. Bango makes appropriate changes in the Bango Platform so you don't need to change your software or processes.
  2. If different flows are required for pre-pay or post-pay users, the Bango flows and business logic will dynamically adapt for you.
  3. When a DCB operator requires special payment related messages to users to meet regulatory or other needs, Bango arranges those without you needing to change your code.
  4. If an MNO requires a consent screen on one of their own hosted domains, the Bango Platform can handle these automatically.
  5. If an MNO requires a consent once per user, Bango can eliminate this friction for your first transaction if the user has already provide consent with another merchant.
  6. If you already have trusted credentials for a payment provider, pass those to Bango and they can be used by the Bango Platform directly without further validation.
  7. Your implementation will be billing model agnostic, allowing incorporation of Credit Card or social payments though the Bango Platform at a later stage if you want.
  8. Your single implementation works across multiple MNOs and has been designed to apply "best of breed" techniques to handle SIM change, number porting and similar situations.
  9. You can request payment flows targeted at specific "selected" users to allow for testing and benefit from code to allow User Acceptance Testing
  10. The design allows "failover" to a second or third identity model if a primary one cannot be used
  11. Bango platform operations is available 24/7 to provide diagnostic or operational support as required 
  12. All Bango Platform transactions are recorded for reconciliation or analysis
  13. Bango Care tool provides an alternative route than API to inspect user transactions
  14. The Bango Dashboard allows your staff to monitor sales and the performance of any payment route in detail  
  15. Unique Bango Boost technology can scan your successful and failed transactions and benchmark them against your peers or the industry best performers 

Integration Steps

The integration process is straightforward:
 

  1. Sign the Bango Platform Agreement

  2. Exchange info & credentials to become a trusted source into the Bango Platform and obtain a password for Bango Grid

  3. Add the Bango API calls and recommended business logic to your store.

    The API and how to integrate it in detail is described at http://docs.bangoapi.apiary.io/
    (The Bango Platform Agreement specifies a technical support contact point to make the integration quick and smooth)

  4. Test using the STUB API http://docs.bangoapistubfeature.apiary.io/#introduction/stub-feature-general-guideline

  5. Test using Bango TestPay - a simulated DCB payment method

    Bango will provide recommended test case scenarios based on requirements of payment providers

  6. Use Bango Grid or ask your support contact to select and activate each payment provider you have an agreement with

    • An activation may require a contract with the payment provider, and proof to Bango that such an agreement is in place

    • Final launch testing may be required for each payment provider before you can use their systems

Information needed from you to use the Bango API

The Bango Platform is configured to map your requirements across the differences between mobile operators or other payment systems.

During the activation process, Bango handles any specific additional requirements from the payment provider and also any regional requirements for your content or service.

If Bango is involved in the Cash settlement from Payment provider Routes, Bango sets up the necessary business rules and procedures for reconciliation and settlement.

The Bango Grid and the Bango Operations Team is your ongoing way to manage configuration.

Bango may also suggest that you provide a number of optional parameters to improve the user experience or commercial models with billing partners. If these parameters are provided but not required, they will have no adverse impact on billing transactions.

For more detail on parameters, please refer to the API documentation (http://docs.bangoapi.apiary.io/)

Examples

The API document lists and defines the purpose of parameters. 

Examples include:

  • Alternative amounts and currencies - to offload presentation and support of multiple currencies
  • Tax information:
    • To provide information sometimes needed by DCB systems to optimize tax treatments item information
    • Or allow provision of tax information to the MNO DCB system if this is required item category
  • To allow the user's bill to contain information about the purchase
  • To categorize different items being billed into categories that your relationships with the payment provider might require
    • This might be used by the Bango Platform to select among different DCB models within a specific MNO, drive different MNO pay-out rates or settlement models for different types of item or service types

Deciding what parameters to provide

The Bango support team assigned to your integration has access to hundreds of previous agreements between stores and their MNO partners and is therefore in an excellent position to predict what requirements there will be as you expand your coverage across the entire Bango payment provider footprint. At the point you prepare to connect to the API, a Bango project manager will review your deployment plans and suggest a set of recommended optional parameters that you should provide if you can, to ensure that you are planning well ahead of deployment and can future-proof your integration with Bango.

In general, while the Bango API can support complex MNO requirements, and can implement workarounds for DCB platform restrictions, it is better to reduce complexity when negotiating an MNO contract. For example by performing single simple transactions rather than complex multi-item transactions that can sometimes complicate DCB integrations for the MNO.