Afterpay Migration
Important
If your app uses an explicit allowlist of Afterpay domains, you must addapi.cash.app and cash.app to the allowlist.API integration
There are no changes to the APIs, so you don’t need to make any changes to your backend systems. While the terminology has changed, the API endpoints are the same.
Afterpay Messaging
We currently support two messaging products, both of which work with Afterpay.
On-Site Messaging is our current messaging product. Our previous product is messaging from the JavaScript Library.
On-Site Messaging
If you use On-Site Messaging, it will be updated automatically, with advance notice sent via email.
If you use elements of Afterpay Messaging, then see the Getting Started with Afterpay On-Site Messaging page for more information.
JavaScript Library
If you use the JavaScript Library for your messaging, it will be updated automatically, with advance notice sent via email.
1.x.js.US Afterpay Experience
-
These docs are for US merchants and partners. If you’re a merchant operating in Australia, New Zealand, or Canada, see the regional Afterpay docs. If you’re operating in the United Kingdom, see Clearpay.
-
The US Afterpay experience operates in US dollars only. Cross Border Trade is available.
-
US customers will see the current Afterpay assets on your product and payment pages.
Brand Assets
See the Brand Assets page in this guide for new assets.
See the Afterpay Merchant guidelines online presentation for detailed information on how to display Afterpay.
Custom messaging updates must be reviewed by your Account Manager.
FAQs
If you have a technical question on the migration, view our FAQ page.
Platforms
This section is for merchants who use a platform for their integration. Find your platform in the list below for information on the Afterpay migration.