Introducing CC49, a newly implemented response code designed to facilitate smoother transactional processes in South Korea.

Response Code: CC49
Response code CC49 is a decline transaction error response code due to a suspended credit card.

Handling Of Error

CC49 has been mapped to the Ezypay response code customer_to_contact_bank. This indicates that customers encountering CC49 should promptly contact their bank for further assistance in resolving the issue.

Resource

For detailed information on handling failed payments and understanding response codes in South Korea, please refer to our failed payment response guide for South Korea.

Security Monitoring Tool Upgrades
Release Period: January and February 2024

As part of our continuous commitment to maintaining a secure and PCI compliant platform, we've implemented upgrades to our security monitoring tools, including Tenable and DataDog. These enhancements bolster our capabilities in detecting and mitigating potential threats, ensuring the integrity and confidentiality of sensitive data. By staying proactive and leveraging new technology, we reaffirm our dedication to providing a safe and reliable environment for our customers.

Enhanced Canary Release Functionality
Release Period: January and February 2024

We've made improvements to our canary release functionality, designed to facilitate safer and faster deployments. With these enhancements, deploying updates becomes more seamless and efficient, minimizing the risk associated with new releases. The refined canary release process ensures smoother transitions, allowing for better monitoring and validation before full-scale deployment, ultimately enhancing the reliability and stability of our services.

Improvements to Fee Data Management
Release Period: January and February 2024

We've been implementing incremental changes to enhance our capability to capture and store more detailed information regarding fee rates, calculated fee amounts, and their linkage to invoices. These improvements are geared towards providing more comprehensive and accurate reporting of fee data in the future. Stay tuned for further updates as we continue to refine and enhance our reporting capabilities.

New Validation Rule in Customer Object
Release Date: 13 February 2024

Added validation rule for the following Customer object fields to prevent card data from being accidentally entered.

• firstName
• lastName
• email
• homePhone
• mobilePhone
• companyName
• referenceCode
• address1
• address2

Implemented restriction: Fields cannot contain 15 or more consecutive digits.

Enhanced Smart Payment Retry Feature
Release Date: 8 February 2024

We've made improvements to our smart payment retry functionality to further streamline transactions involving tokenised Visa cards issued by Standard Chartered Bank. Now, the system automatically initiates retries when encountering failure response code 82, ensuring a smoother transaction experience for customer and merchant. This enhancement optimizes the process, reducing the likelihood of transaction failures and providing a more reliable payment solution.

Internal Platform - Search Bar function/symbol & email symbol
Release Period: January and February 2024

We’ve made several improvements to our internal interface to enhance our user search function. Ezypay support teams now have a comprehensive and accurate search function which will enhance our customer service.

If you look at the entries preceding this update, you'd be forgiven for thinking that the last update on the Ezypay platform was 9 months ago. That is far from the truth - the reality is that we average between 15 and 20 Production releases per month, so almost every business day there is a new feature, enhancement or bugfix going out.

We've been so busy focusing on building and releasing that we've neglected to maintain this changelog. That's about to change, and you'll start to see regular updates and communication from us on the changes that are being released. We're proud of our platform, our velocity, and we want to make sure everyone hears of all the great stuff our engineers are working on. We know our Product and Engineering teams are awesome, but do our customers and partners?

After all, If a tree falls in a forest and no one is around to hear it, does it make a sound?

Since the launch of PayTo in Australia last year there are over 50 banking institutions that are now live with PayTo processing. Westpac was the latest of the Big 4 banks to enable their customers with PayTo, meaning more Australian accounts can now transact via PayTo.

We have our first Partner integrated and using Ezypay’s PayTo functionality on their platform. And we are also continuing to work with our early adopter partners to enable PayTo on their platforms so they can offer PayTo as a payment method.

A reminder of how PayTo will benefit your customers:

• PayTo allows real-time bank-to-bank payments through faster processing times and enhanced customer validation to reduce payment risk.
• PayTo also enables more customer flexibility as it will allow customers to move or update accounts associated to their PayTo debit agreement without having to update these details through your platform or the need to contact the merchant.

To keep up to date on news and events regarding Ezypay and PayTo, please visit our PayTo webpage.

PayIDWe are also excited to announce that we now allow customers to use PayID with PayTo. PayID allows customers to use their linked email or phone number to setup their payment method.

How PayID will benefit your customers:

• Using PayID instead of an account number is not only easier for customers to remember – reducing the risk of entering incorrect bank details, there is also real-time PayID verification.

Technical details on how PayID works with PayTo can be found here.

We are excited to announce that Ezypay has adopted Mastercard’s tokenised payment security technology in Hong Kong, following its successful implementation in Malaysia and Singapore. This advanced payment technology, Mastercard Digital Enablement Service for Merchants (MDES), replaces a customer’s physical card information, including the card number and expiry date, with an encrypted digital token that is unique and specific to each merchant. The token can be updated by the card issuer, allowing lost, expired, or replaced cards to be automatically updated and processed – greatly improving payment data security and increasing the likelihood of a successful transaction.

Our adoption of MDES ensures that your merchants can continue to collect payments seamlessly and securely. There are no additional steps or actions required by you to enable this technology.

At Ezypay, we are committed to ongoing innovation and providing you with an effortless payment experience that results in increased Collection Rates. With our adoption of the MDES technology, your merchants can continue to focus on growing their businesses while achieving successful payment collection outcomes more consistently. You can read more about this in detail here.

We are excited to announce that Ezypay has adopted Mastercard’s tokenised payment security technology in Malaysia & Singapore. This advanced payment technology, Mastercard Digital Enablement Service for Merchants (MDES), replaces a customer’s physical card information, including the card number and expiry date, with an encrypted digital token that is unique and specific to each merchant. The token can be updated by the card issuer, allowing lost, expired, or replaced cards to be automatically updated and processed – greatly improving payment data security and increasing the likelihood of a successful transaction.

Our adoption of MDES ensures that your merchants can continue to collect payments seamlessly and securely. There are no additional steps or actions required by you to enable this technology.

At Ezypay, we are committed to ongoing innovation and providing you with an effortless payment experience that results in increased Collection Rates. With our adoption of the MDES technology, your merchants can continue to focus on growing their businesses while achieving successful payment collection outcomes more consistently. You can read more about this in detail here.

We would like to inform you that on Monday, March 6th (7PM AEDT time), Ezypay will be performing a required upgrade to our Sandbox Environment. This will result in an estimated 2-hour disruption of services to the Sandbox environment.
If you have any questions, please do not hesitate to contact our Implementations Team.

As we know, PayTo is the latest innovation in Australian payments to initiate recurring real-time payments from customers' bank accounts. We have recently integrated this new payment method (PayTo) on our platform. To support this, we have made some changes to how the Hosted Payment Page works.

If you have enabled PayTo as a payment method option, we have added a new parameter that is now required for the Hosted Payment Page:

* MandateTypeId

The MandateTypeId parameters must be specified in the Hosted Payment Page integration if the merchant is using PayTo as a payment method.

We have also made an update to the existing PaymentMethods parameter. This allows for the PayTo payment method to be displayed on the Hosted Payment Page. You will find this payment method option on the Hosted Payment Page if the merchantId is specified, and if you have enabled PayTo against your Ezypay account.

The PaymentMethods parameter allows you to specify payment method options that you can accept from customers. For example, if you have enabled PayTo against your Ezypay account, but do not yet want it to be displayed as a payment method option for the customer, then you can choose to not specify PayTo in PaymentMethods.

Further details on the Hosted Payment Page can be found here.

Here is an example of what the Hosted Payment Page will look like with PayTo as an additional payment method.

PayTo will apply to Australia only and will not impact your current integration. More details about PayTo can be found here.

Credit, debit & prepaid card providers - Visa and Mastercard have mandated to extend their 6-digit Bank Identification Number (BIN) to an 8-digit BIN from April 2022. This means that from 1st April 2022 onwards, any new BINs issued will be an 8-digit BIN. Other card providers are not moving to 8-digit BINs yet.

There is no change in the way merchants or customers submit card account details and how we process card payments.

More details about Bank Identification Numbers can be found here..

We would like to inform you that we will be performing scheduled maintenance to improve the infrastructure and stability of the Ezypay V2 platform. This will result in a 1-hour disrupted service during the following period:

Australian Eastern Standard Time (AEST):
Wednesday, September 28th from 9:00pm to 10:00pm

New Zealand Daylight Time (NZDT):
Thursday, September 29th from 12:00am to 1:00 am

Malaysia, Singapore, Taiwan, Philippines, Hongkong Time (MYT, SGT, CST, PHT, HKT)
Wednesday, September 28th from 7:00pm to 8:00pm

Thailand Standard Time (ICT):
Wednesday, September 28th from 6:00pm to 7:00pm

South Korea (KST):
Wednesday, September 28th from 8:00pm to 9:00pm

Coordinated Universal Time (UTC):
Wednesday, September 28th from 11:00am to 12:00pm

What this means:

• Ezypay’s online services will be affected during this period. This includes our hosted payment pages, checkout pages and our failed payment collection pages (paynow.ezypay.com).

• Any attempts to add, edit or make payments during this time will return an error. Please complete these actions after our system is back online.

• Payments that were scheduled before the outage time will not be affected and will be processed as normal.

• All API calls to api-global.ezypay.com during this time will receive a HTTP 503 Please retry these calls after our system is back online.

For up-to-date status of our system, please visit Ezypay System Status.
If you experience any system issues after the scheduled maintenance, please contact us at [email protected].

We apologize for any inconvenience this may cause.

Kind regards,
The Ezypay Team