← Updates
Updates v06.2026

Update 06/2026

This update focuses on controlling payments integrated with Mercado Pago, personalizing the scheduling iframe and refining the appointment confirmation flow.

Payment Method Configuration in Mercado Pago

Each account can now choose which payment methods are available in the Mercado Pago Checkout Pro. Previously, the checkout displayed every method by default.

How it works:

  • New configuration area to enable or disable payment methods.
  • Payment types: you can remove Pix, bank slip, credit card and debit card.
  • Card brands: specific brands such as Visa, Mastercard, Elo and Amex can also be excluded.
  • The selection is applied when the checkout is generated, reflecting directly on the client’s payment screen.

External Payment Confirmation

We added the Payment made externally option to the appointment confirmation modal. It covers the scenario where the client books through the platform but pays through another method.

  • When confirming the appointment, the payment is marked as completed regardless of the response from the Mercado Pago integration.

New Scheduling Iframe

We released a modern iframe to embed schedules on external sites and pages, with a higher level of visual personalization.

Because of the Zoom API daily request limit, some appointments could end up without a meeting link. There is now a button to generate the link manually for these appointments.

Confirm Appointments Screen

The Confirm Appointments screen now displays all appointments pending confirmation automatically, without requiring the user to filter by date.

Fixes and Stability

This version fixed the delivery of notifications for appointments with a pending Mercado Pago payment, which now respect the payment confirmation before sending reminders and the video conference link. We adjusted the Google Calendar integration to also send the client’s name, and corrected the permissions in Access Lists and in view-only access, which were releasing or changing schedules and time slots improperly. We also handled the internal client registration that still required an email even with the field set as optional, the save button in the organization’s payment settings, and several errors in the user groups, plan change, V3 schedule configuration, appointment creation and app registration screens.