Introduction to BPAY (Bill Payments)

This module allows the customer to make payments through channels like internet banking or phone payment. The customer can also make the payment by setting a standing order in advance.

As part of this module, before fetching the biller details, the API will first retrieve the token using the Client Id and the Client Secret fields. Once the token is retrieved, the biller code will be sent along with the token to retrieve the details.

BPAY is an electronic bill payment system in Australia, which enables payments to be made through a financial institution's online, mobile, or telephone banking facility to organisations that are registered as BPAY billers.

The organisations or businesses participating in BPAY are assigned with a unique biller code. When a customer receives the bills with the BPAY logo, he or she will also see the unique customer reference number along with the biller code in the bill. The customer will then make the payment with the information supplied in the bill.

By setting up a standing order for BPAY, Temenos Transact triggers a payment order on the execution day.

The benefits of this module are:

• Biller and payment verification.
• The biller verification is done in both STO and payment order, the payment verification is done in the payment order.

Click here to understand the terms and abbreviations used in this module.

Generic API's

This functionality allows banks to manage the standing order and payment order pertaining to a bill payment.

The following items have been released as part of this functionality:

• The STANDING.ORDER,AUBPAY.API.STANDING.ORDER.1.0.0 version is used to create, update and retrieve the details of a standing order pertaining to the bill payment.
• The PAYMENT.ORDER,AUBPAY.API.PAYMENT.1.0.0 version is used to create a payment order for the bill payment.

Manage BPAY Biller Details

BPAY is Australia’s most widely used bill payment service, which enables bill payers to transfer funds electronically from their bank accounts to BPAY registered billers. CUSCAL, an Authorised Deposit-taking Institution (ADI), is Australia’s leading provider of end-to-end payments solution. CUSCAL supports the processing of BPAY transactions. TPH will act as Cuscal’s BPAY payments processing system.

This functionality supports the on-boarding and maintenance of new billers.

When a business registers with BPAY, it will provide the biller for that business. This functionality details the registration and the management of the biller through Temenos Transact.

In Temenos Transact, the biller management involves the creation of the requests below:

• Add biller: This request is used to create a new master biller or sub-biller.
• Update biller: This request is used to update the details of a master biller or sub biller, which is already created and available in the BPAY system.
• Transfer biller: This request is used to transfer a biller from one financial institution to another institution.
• Close biller: A biller can be closed using this close request.

A separate version has been created for each request. Upon approval of each of these requests in Temenos Transact, the BPAY API will be called to pass the details to the BPAY external system where the biller details are created or updated based on the request.

Apart from the above change requests, an option is available to delete the pending change request at BPAY.

As part of the solution three new applications have been created:

• The AUBPAY.BILLER.PARAMETER application has been created to store the parameter details of the biller.
• The AUBPAY.BILLER.REQUEST application has been created to store the details of the change requests of both the billers master and sub-biller.
• The AUBPAY.BILLER application has been created to store the actual details of billers master and sub-biller as per the BPAY system. An entry will be created in this application when the actual requests are applied in BPAY.

This functionality allows banks to display the validation rules and the check digit rules through the AUBPAY.VALIDATION.RULE.API.QUERY.1.0.0 and AUBPAY.CHECK.DIGIT.RULE.API.QUERY.1.0.0 enquiries.

Storing and managing reserved biller codes will be done through customisations.

Biller Facility Check

The TPH can accept the incoming BDFs from BPAY clearing. The BDFs sent by the BPAY, contains multiple transactions and will be received three times per day.

With this functionality the system will be able to check the Biller Status in the AUBPAY.BILLER application for the Biller Code.

If the biller is not available in the AUBPAY.BILLER or the biller status is other than ACTIVE the values will be cleared based on the instruction type in the following tags:

• For the Instruction Type=05 (Payment) values will be cleared in the Creditor Agent Financial Institution Id_Member Id tag.
• For the Instruction Type= 15 or 25 (Error correction or Reversal) values will be cleared in the Debtor Agent Financial Institution Id_Member tag.

If the biller code in the AUBPAY.BILLER is sub-biller, for example if the Mast Biller Ind is false map the Mast Biller Code of the sub biller to the following tags based on the instruction type.

• For the Instruction Type=05 map the Mast Biller Code to the Creditor Agent Financial Institution Id_Member Id tag.
• For the Instruction Type= 15 or 25 map Mast Biller Code to the Debtor Agent Financial Institution Id_Member tag.