This weeks release 11.08.25 includes:

• Managing metadata for usage-based billing products directly in the admin UI
• Usage records for usage-based billing now display from latest to oldest
• “All numbers are in DKK” message has been removed from all dashboards - KPIs now reflect your configured account currency
• Legacy Payment Dashboard deprecation, and a reminder of where to find your metrics in Revenue Insights

👉 Read the full release note
🔔 Follow the release notes page to stay updated

We’ve dropped this week’s release – including:

• 🧾 Access to Transaction Settlement Reports in-app
• 📊 New report categories for cleaner navigation
• 🧷 Additional fields in Subscription Details
  
  

Whether you're deep in billing workflows or just like staying in the loop - check these out.

👉 View the release notes
The Frisbii Team

This week’s release introduces a new way to credit invoices, smarter invoice templates, and cleaner plan updates—plus bug fixes for API access and subscription pricing.

👉 View the full release here to see what’s new.

🎥 LAST CHANCE - Register for the webinar 'Beyond Spreadsheets: The Future of Revenue Planning and Prediction'
Join us live to explore what’s next in Revenue Insights - Predictive Analytics.

🔔 Want to stay in the loop?
Hit Follow on the Release Notes Overview page to get future updates straight to your inbox.

This week's release includes UI tweaks, new invoice fields, decimal updates for Usage Based Billing, and bug fixes for invoice downloads.

👉 View the full release here to see what’s new.

🔮 Coming soon: Performance Analytics & Predictive Analytics

🎥 Register for the webinar 'Beyond Spreadsheets: The Future of Revenue Planning and Prediction'
Join us live to explore what’s next in Revenue Insights.

🔔 Want to stay in the loop?
Hit Follow on the Release Notes Overview page to get future updates straight to your inbox.

We’re excited to share that weekly release notes for Frisbii Billing & Pay are now available directly in our Knowledge Base!

Each week, we’ll highlight what’s new, what’s improved, and what’s been fixed — clearly tagged by:

✅ Product - Billing – Starter, Growth, Enterprise, or Pay
⚙️ Platform - App or API
🛠️ Type - New Feature, Enhancement, Bug Fix or Coming Soon

📅 What to expect:

• New updates posted every Monday or Tuesday 
• A quick view of what’s changed and why it matters
• Links to Knowledge Base articles or deeper documentation when needed

👉 Start here:

• 📚 Release Notes Overview
• 🚀 This Week’s Release – June 23, 2025

Stay in the loop, and make the most of what Frisbii has to offer.

Let us know what you think — and what you’d love to see next!

The Customer Portal configuration has been moved to a new location: Sidebar → Customers → Customer Portal. This centralizes all customer-facing settings, including Email one-time password verification in one place.
This update will streamline the user experience by consolidating all customer-facing setting into a single, easily accessible section. By grouping these configurations together, you can now manage customer interactions and validation settings more efficiently, without jumping between different parts of the app.

This change also lays the foundation for upcoming enhancements to customer record creation and additional Customer Portal capabilities that we will be releasing soon

Starting during June and onwards, you will begin receiving payment method updated webhooks for stored Apple Pay payment methods.

These webhooks work just like the ones you already receive for Visa and Mastercard through our tokenization solution, letting you know when a stored Apple Pay payment method has been updated or is no longer valid.

🔔 Note: This is only relevant if you are saving Apple Pay payment methods.

There is no action required on your part, unless you are performing custom validation or handling of these webhooks in your own systems. In that case, you may want to review how your integration responds to these new Apple Pay events.

The webhooks are provided simply for your convenience, so you can proactively detect failed or invalid Apple Pay tokens before attempting a recurring charge.

If you have any questions or concerns, we’re here to help.

What’s changing?

Effective June 25, 2025, all system emails currently sent from:

• @reepay.com
• @billwerk.plus

…will instead be sent from:
@frisbii.com

This applies to transactional emails such as receipts, subscription confirmations, payment notices, and other customer communications triggered via the Frisbii platform.

Action Required (If applicable)

If your integration or infrastructure relies on sender domain filtering or validation, please update your settings to accept emails from @frisbii.com by June 25, 2025 to prevent any service disruptions.

This depends on your own email domain or server settings, which are managed outside of Frisbii. If you're unsure how this might affect your setup, we recommend contacting your IT team or email administrator.

No action needed if…

You’re using a custom email domain (e.g., @yourcompany.com) configured in Frisbii. These will remain unchanged and continue to function as expected.

If you have any questions or need help updating your configuration, please contact our support team at support@frisbii.com.

Many thanks, The Frisbii Product Team 💙 

Say hello to the Frisbii Knowledge Base!

All Help Center content for Frisbii Billing & Pay has officially migrated to our new, unified Knowledge Base.

📌 New Link: help.frisbii.com/docs
📌 Bookmark it! You can also access it anytime:

• From within the Frisbii app, under ? Help
• Through the Resources on our website

Just like before, you'll find everything you need to support your day-to-day with guides to help with your Frisbii setup. But this is just the beginning—we’re actively expanding and improving the content, and soon, all Frisbii product help centers and release notes will live in one cohesive Knowledge Base space.

🔎 Spotted something missing or a little dusty? Give us a shout! We’re here to keep things fresh and helpful - your input makes it better for everyone. 

Thanks for growing with us!
– The Frisbii Team 💙

We will update the TLS certificates used to secure API connections to our services on May 7, 2025. 

This change is unlikely to affect you, unless you have explicitly chosen to implement certificate pinning in your HTTPS client.

Impact

Clients utilizing certificate pinning may experience connection failures or trust errors following this update.

Action required

If you're affected, we recommend discontinuing the use of certificate pinning, as it is generally discouraged. However, if this isn't possible, instructions for pinning our new certificates are provided below.

We are moving to Amazon Web Services (AWS) certificates. AWS cross-sign an intermediate certificate with different root CAs. This ensures that the certificate is trusted by a wider range of clients, especially legacy systems or older devices that may only trust a certain root. But it also means that it is not enough to add a single root certificate to trust store.

AWS provides resources for certificate pinning here: https://www.amazontrust.com/repository/ (Trust Store and Pinning Recommendations).

To recap:

1. Use public key pinning, not full certificate pinning: 
2. Pin all available root certificates found here: https://www.amazontrust.com/repository/

Testing

Testing can be performed by performing a HTTP get with the updated client to this endpoint: 

https://staging-api.reepay.com/info/

If pinning has been successfully implemented, a connection will be established, and a JSON object will be returned.

Need Help?

If you need assistance or have concerns about this change, please contact: support@frisbii.com.