Reactivating dead / expired subscription or updating a subscription's next charge date is now possible via Update Subscription API, by specifying the next charge date of a dead/ongoing subscription in the schedule object via next_execution_at. More details here.

We've released a generic QRIS (or also called as Other QRIS) that works similarly like our Other Bank feature, which will present a generic QRIS with various issuers' logo to customers in Snap. This feature aims to improve your transactions' conversion by making it easier for customers to understand that they can pay using various e-wallets and banks. Going forward, we will be making several optimizations from various aspects (e.g. design, copy, UX, etc) to this feature based on our learnings of what works to improve transaction conversion. Generic QRIS can also be used to persistently show QRIS to customer regardless of screen size. See the API reference here.

We updated our Payment Link API requirement so that merchant can indicate which customer details (email, phone, and first name) that customer needs to fill in order to be able to proceed to pay - previously if customer_required is set as true, all 3 fields need to be filled by customer.

Merchant can now customize Snap's page expiry via API request. Follow this guide for more details.

New Android SDK (ver 2.0) that supports the new version of hosted checkout page (Snap) was released on Feb 24th, 2023. Please update immediately if you're still using SDK with version lower than 2.0.

As mandated by principals, starting Feb 9th, we will no longer support card transaction using older 3DS version 1 when merchant sends /charge. You will receive a charge response message: Cards with 3DS version 1 or lower are not supported. Please retry with another card that supports the minimum 3DS version 2.. Transactions will be marked as failure and will not exist.

• Add support for Snap page custom expiry via Dashboard > Snap Preference, which will let merchant set Snap page's expiry time (previously fixed to 24 hours by default).

Midtrans newly revamped technical documentation is now released (what you see here!). We've heard your feedbacks over our documentation in the past and have rebuilt our documentation from ground up in order to be able to make your integration experience easier, while retaining some of the most loved features from our previous documentation. Some highlighted features from our new documentation :

Changelog of addition to Midtrans's product and API can be found here.