As part of our evolution from Reepay and Billwerk to Frisbii, we are rolling out a comprehensive rebranding initiative that reflects our growth and expanded vision. Frisbii is a modern European-based recurring revenue management platform trusted by over 4,000 businesses in 95+ countries. With this rebranding, we're aligning our identity, infrastructure, and communications to better support our global customer base and our mission to simplify billing, subscription management and payment at scale.
➡️ Learn more about the Frisbii rebranding
One of the key technical updates during this transition is the domain change for our API services.
Dual Domain Availability
We are currently rebranding the primary API domain from:
api.reepay.com→api.frisbii.comcheckout-api.reepay.com→checkout-api.frisbii.comcustomer-portal-api.reepay.com→customer-portal-api.frisbii.com
Both domains are fully operational during this transition period. However, we recommend that all developers and partners useapi.frisbii.com, checkout-api.frisbii.com,customer-portal-api.frisbii.com in new integrations and begin updating existing systems accordingly.
Checkout domain
Frisbii Checkout is available on both checkout.frisbii.com and checkout.reepay.com. Both are fully supported, and existing integrations do not need to change anything.
- Checkout JS SDK: new integrations should load
https://checkout.frisbii.com/checkout.js. Integrations that loadhttps://checkout.reepay.com/checkout.jskeep working. The JavaScript namespace is the same on both (Reepay.EmbeddedCheckout,Reepay.ModalCheckout, …). - Hosted checkout (Window Checkout, payment links): always send the customer to the
urlreturned when you create the session, and never build checkout URLs yourself. New accounts getcheckout.frisbii.comURLs. Existing accounts continue oncheckout.reepay.com; moving tocheckout.frisbii.comis optional. - Content Security Policy and firewalls: if you restrict scripts or frames, allow the checkout domain your integration uses. Allow both if you are unsure.
