Twilio Changelog

Accept PIX Payments on WhatsApp with Twilio/pay
Move from conversation to conversion with native in-chat payments

We’re excited to announce support for PIX payments on WhatsApp using Twilio/pay templates. You can now guide customers through completing a financial transaction directly in WhatsApp.

Use Content Templates with Twilio/pay to:

• Send Order Details messages with a PIX copy code button that opens the user’s banking app

• Send Order Status updates as payment progresses through stages like pending, shipped, or completed

• Display itemized order summaries, expiration details, and total amounts—all within a single message

To enable this, your business must:

• Have a valid WhatsApp sender in Brazil

These templates support variables for payment ID, merchant name, itemized details, and expiration. Rich metadata can be passed to payment processors, with updates automatically sent to users through Order Status messages.

Ready to embed seamless checkout into your messaging flows?
Explore the docs to get started:
twilio/pay

We’re making it easier to troubleshoot Toll-Free Verification (TFV) errors!

Starting May 15, 2025, we’ll begin rolling out more specific and detailed error codes for TFV requests. These new codes are designed to give you clearer, more actionable feedback when a submission doesn’t go through— so you can fix issues faster and keep things moving. 

Don’t worry, the old codes will still be supported— but we think you’ll find these new ones to be more helpful.

What’s changing?

Right now, TFV error messages can be a bit vague. With this update, you’ll start seeing granular error codes that explain why a verification was rejected. These new codes will appear in: 

• API responses

• Webhooks

• Email notifications

• Twilio Console

What this means for you

If you’re a customer that has set up custom logic to handle TFV errors—like mapping them in dashboards or internal tools—be sure to review and update your error mapping to reflect the new codes.

For more details, check out the Twilio API Docs and the Twilio Error Code Dictionary.

We hope this update makes your TFV experience smoother and more efficient. 

Thank you for building with Twilio!

As of April 10, 2025 the Legacy Boku Identity APIs Infrastructure in Europe will be migrated.

We would like to inform you about upcoming changes to Legacy Boku Identity API’s production infrastructure in Europe. These changes will not impact your current service. Our goal is to minimize impact to your current integration to our services. These updates are part of our ongoing commitment to improving performance, scalability, and reliability for all our customers.

If you have whitelisted or hardcorded our IP addresses instead of URLs, please make a note of our new IP addresses. These new IP addresses will take effect once we perform the switchover to AWS cloud services.

Our support team is available to assist you with any questions or concerns at accsec-onboarding@twilio.com.

Thank you for choosing Twilio. We appreciate your partnership and look forward to continuing to provide you with exceptional service.

You can now sign up to receive a weekly email of your [Deliverability Score], so you can track your messaging health and performance. 

The [Deliverability Score] provides a simple, comprehensive view of your messaging traffic and helps you target specific areas for improvement. The new weekly email summarizes your score and provides links to Twilio Console Messaging Insights where you can view score details, identify optimizations, and troubleshoot. 

We're excited to announce that we have made updates to the existing Compliance Report to now include Toll-Free & Regulatory Compliance Information.  Compliance information from all 3 programs (A2P, Toll-Free & Regulatory Bundles) can be downloaded from one singular report on demand and can be accessed on the download page located on Twilio's Console.

ConversationRelay has been updated to include ElevenLabs as a text-to-speech provider. 

As of March 31, 2025 the Legacy Boku Identity APIs Infrastructure in Australia will be migrated.

We would like to inform you about upcoming changes to Legacy Boku Identity API’s production infrastructure in Australia These changes will not impact your current service. Our goal is to minimize impact to your current integration to our services. These updates are part of our ongoing commitment to improving performance, scalability, and reliability for all our customers.

If you have whitelisted or hardcorded our IP addresses instead of URLs, please make a note of our new IP addresses. These new IP addresses will take effect once we perform the switchover to AWS cloud services.

Our support team is available to assist you with any questions or concerns at accsec-onboarding@twilio.com.

Thank you for choosing Twilio. We appreciate your partnership and look forward to continuing to provide you with exceptional service.

On April 1st, 2025, the WhatsApp Template Console Tab and Templates API will be deprecated. As part of the deprecation Twilio will implement brownouts for the product from April 1 to April 21. After April 22 WhatsApp templates sent with the legacy WhatsApp Templates product will no longer be able to be sent.

Customers will start to see 63016 errors if they continue sending templates without making the necessary changes. Sending WhatsApp templates using the body parameter will be deprecated. Customers need to migrate to Content Template Builder (formerly known as Content API and Content Editor) and change their how they send templates to use Content Sid and Content Variables to avoid a disruption.

Your Content Templates can be found in the Content Template Builder in Twilio console.

More information about the deprecation can be found in this support article.