⚡free Webinar: AI-powered regular giving in Payments2Us🤖

Need Help? Let's Find the
Answer Together!

Sorry, we didn't find any relevant articles for you.

Send us your queries using the form below and we will get back to you with a solution.

BPAY

Topics on BPAY

Why do I get an Error Log with "Program/Area: BPAYUtil.accessToken" and Subject: "HTTP Callout response: UNAUTHORISED"

You need to make sure you have set up your BPay API credentials and entered them ...

You need to make sure you have set up your BPay API credentials and entered them against the Merchant Facility. Follow the procedure: How to setup BPAY API Credentials 

When setting up the credentials, please pay particular attention to the BPay Key/Token that is used and make sure that is the correct one for your Environment (Production/Sandbox). See Pre-production vs. Production. 

You may also want to check the Environment on the Merchant Facility is correctly set to "Production" when in production mode or "Sandbox" when testing. For BPay, you'll need to have been approved by BPay for their production details and have the correct credentials from them.

If you might also pay to check you have the BPay Remote Site settings as active. Navigate to setup (cog in the top right), then search "Remote Site Settings". The edit and make active the following:

  • BPayPreProduction
  • BPayProduction

Finally, also check if your Payments2Us version is 9.4 and above if you are getting this error when using the checkout option to generate BPAY.

Ezidebit automated BPay Testing

Pre step: Setting up the BPAY CRN Payment2us invokable action in salesforce by fo ...

Pre step: Setting up the BPAY CRN Payment2us invokable action in salesforce by following article here: How to Setup BPAY Customer Reference Numbers

The only way to test BPay in sandbox and not live mode is to contact EziDebit technical support. They can setup specific BPay codes and references for specific dates and amounts.  You can contact EziDebit to setup these sample transactions in your test account.  Note, these are for fixed dates. 

Ezidebit will probably ask you for the CRN, dates and amounts that you would like.

Example request:

Could I please get some BPAY payments setup in our test environment.
Please use any CRN No and just let me know what they are.  There would be 5 different CRN’s.

$100 every 2 days from 10/6 for say 2 months
$200 every 2 days from 10/6 for say 2 months
$300 every week from 10/6 for say 2 months
Varied amounts – say from 10 – 1000 for every 2 days for 2 months
Varied amounts – say from 10 – 1000 for every week for 2 months
 

In reply to the above Ezidebit setup 25 transactions based on the above and provided the CRNs.  After this you need to setup contacts with those CRN and the expected amounts and dates.

Note: once EziDebit set the transactions up, you should be able to see a payment source filter for BPAY in your EziDebit portal:

After this, the overnight run will then retrieve these payments from EziDebit and mark off as required. That is, after the recurring payment processor runs, a BPAY check processor is run.  This will create an Import File, import file line item and form there, this will update the Payment Txns This is the automatic reconcilliation provided by Ezidebit.

How to test with BPAY Sandbox APIs?

BPAY developers portal has moved from bpaygroup-portal.apigee.io to developers.au ...

BPAY developers portal has moved from bpaygroup-portal.apigee.io to developers.auspayplus.com.au/bpay/. It now provides Sandbox APIs for initial testing and integration. These can be used alongside Pre-Production APIs within Payments2Us. 

Pre-Production APIs vs Sandbox APIs

The Pre-Production APIs (also referred to as Non-Production or Certification APIs) are different from Sandbox APIs.

It is recommended to use Pre-Production APIs for BPAY testing. As they better reflect real-world behaviour.

 

 

1. Setup BPAY Sandbox APIs

  • Add the Remote Site Setting sandbox.api.bpaygroup.com.au and ensure it is activated in your Salesforce org
  • Add BPAY Sandbox API keys in your Merchant Facility.

 

2. Understanding BPAY Sandbox Limitations

The BPAY Sandbox environment is designed for basic connectivity testing and contains limited test data. The CRNs can only be generated using a specific test customer number: 123456 on Sandbox APIs. Payments2Us generates customer numbers dynamically (see How to setup CRNs in Payments2Us), which are not supported in the BPAY Sandbox environment. 

During testing with Sandbox APIs, you will notice that the Payment Txns are created successfully, but an error log is generated with the message: “Unsupported Request Payload”. This error is expected and indicates that the BPAY APIs are successfully connected and working, but the request is not supported due to the limitations. You can safely ignore this error during Sandbox testing.

 

For accurate and complete testing, use BPAY Pre-Production API keys (with the BPPC prefix), which better reflect real-world behaviour. You may need to contact BPAY Support to request access to the Pre-Production environment.

 

If you encounter errors other than “Unsupported Request Payload”, or have any questions, please contact Payments2Us Support for further assistance.