ZenotiHelp

Processor: Sunbit

ZTZenoti Docs Team Updated August 21, 2026 9 min readGuide

Sunbit is a V2 Buy Now Pay Later (BNPL) processor available in the United States only. It lets guests apply for in-store financing through Sunbit's hosted flow and complete their purchase without using a credit card. Sunbit is configured at the organization level, and each center completes its own iframe-based merchant onboarding before Sunbit becomes active at that location.


On this page


Before you begin

Permission: Organization administrator access is required to configure Sunbit.

  • Your organization must have an active Sunbit merchant agreement in the United States.
  • Each center requires its own Sunbit merchant application β€” Sunbit onboarding is per center, not per organization. Budget time for each center to run through the iframe flow.
  • Sunbit is a BNPL loan product, not a card processor. It cannot replace your primary card processor; configure both.

Key details

Detail Value
Availability United States only
Transaction minimum $60 USD
Transaction maximum $10,000 USD
Merchant fee 5% flat per transaction
Settlement timing Full invoice amount (less fee) to the merchant within ~2 business days
Void Not supported through Zenoti
Refund Not supported through the Zenoti UI; post-transaction reversals are handled by Sunbit
Pre-authorize / capture Not supported
Recurring payments Not supported
Chargeback risk None β€” Sunbit bears repayment risk

Sunbit capabilities in Zenoti

Capability Supported
BNPL loan origination Yes
Card reader / terminal No
Stored accounts No
Auto-save card No
Pre-authorize / capture No
Void through Zenoti No
Refund through Zenoti No β€” Sunbit processes reversal events asynchronously when reversals are initiated on Sunbit's side
Per-center merchant onboarding (iframe) Yes
Prequalification (guest credit check) Yes
Text-to-Pay (SMS-based payment collection) Yes
Webhook-driven status updates Yes

Network requirements

Sunbit runs entirely in the cloud. The merchant onboarding iframe and the guest prequalification page are hosted by Sunbit; Zenoti and Sunbit exchange notifications over HTTPS.

Connection Direction Protocol / Port Notes
Guest browser to Sunbit Outbound from guest device HTTPS / 443 Guest completes the application on Sunbit's hosted page.
Merchant browser to Sunbit onboarding iframe Outbound from the center's browser HTTPS / 443 Required once per center during onboarding.
Zenoti to Sunbit API Outbound from Zenoti (cloud) HTTPS / 443 Managed by Zenoti.
Notifications from Sunbit Inbound to Zenoti HTTPS / 443 Zenoti registers the endpoint during organization-level setup.

Centers with strict egress policies should ensure the staff browser can reach Sunbit's hosted domains while completing the merchant application iframe.


External-system prerequisites

These steps happen outside Zenoti, before or during configuration.

  1. Sign a Sunbit merchant agreement at the organization level. Obtain the Sunbit-issued organization credentials from your Sunbit account manager.
  2. Gather the business information Sunbit will request inside the onboarding iframe, per center:
    • Legal business name
    • Federal tax ID (EIN)
    • Contact details for a responsible party
    • Bank account details for settlement
    • Any legal disclosures required by Sunbit's agreement
  3. Plan for Sunbit's approval timeline. Each center's application progresses through: Created β†’ Location Details Added β†’ Contact Details Added β†’ Bank Information Added β†’ Legal Information Added β†’ Submitted β†’ Activated (or Declined). Zenoti reflects the state as Sunbit pushes status updates.

Configure Sunbit (organization level)

  1. Navigate to Configuration > Payments > Process payments > Payment processor onboarding.

  2. Select Pay Over Time, then select Set up next to Sunbit.

  3. Enter the Sunbit organization-level credentials provided by Sunbit.

    Field Source / Owner Notes
    Sunbit organization credentials Sunbit merchant account team Issued when your Sunbit contract is countersigned.
  4. Select Save. Sunbit is now ready at the organization level. No center can accept Sunbit until that center completes its own onboarding (below).


Onboard each center

Sunbit requires per-center onboarding inside its hosted iframe. The fields inside the iframe are controlled by Sunbit and may change; do not expect specific field names in Zenoti.

  1. From Payment processor onboarding > Sunbit, select the center you want to onboard.
  2. Select Launch Sunbit onboarding.
  3. Zenoti registers the center with Sunbit, then loads Sunbit's hosted onboarding iframe inline.
  4. Complete the application in the iframe using the information gathered in External-system prerequisites.
  5. Submit. Sunbit reviews the application and updates the center's status asynchronously. Zenoti reflects the state as it progresses.
  6. Repeat for every additional center.

Note: A center does not accept Sunbit until its state is Activated. Do not offer Sunbit to guests at a center whose onboarding is still in progress.

Worked example

A spa organization with three centers β€” Downtown, Midtown, and Uptown β€” must complete three separate Sunbit applications. The Downtown center submits its application on Monday and receives Activated status by Wednesday. The Midtown center submits Tuesday and is still in Submitted state on Wednesday. Only the Downtown center shows the Checkout with Sunbit button on its HPP that week. Midtown's button appears automatically once Sunbit activates that center's account.


The Sunbit checkout experience

Sunbit payments happen through the Hosted Payment Page (HPP), not through a card terminal.

  1. At the point of sale, the front desk selects Checkout with Sunbit from the HPP payment options. This button only appears if Sunbit is Activated for the center and the invoice total is between $60 and $10,000.
  2. The HPP redirects to Sunbit's hosted prequalification page on the guest-facing device.
  3. The guest completes a short application (typically 30 seconds). Sunbit runs an instant credit check and returns a decision.
  4. On approval, the guest selects a payment plan.

Pre-qualification validity. A guest's Sunbit pre-qualification approval is valid for approximately 30 days. If the guest returns after this window, they must re-apply. Front-desk staff should not assume a prior approval is still active for returning guests if more than 30 days have elapsed since the original qualification date.

  1. Sunbit finalises the loan and redirects back to Zenoti.
  2. Zenoti applies the payment to the invoice and closes it. The front desk sees the paid status without needing to swipe a card.

The merchant receives the full invoice amount (less the 5% fee) from Sunbit within approximately two business days. Sunbit then collects from the guest on Sunbit's own repayment schedule β€” the merchant never handles repayment and bears no chargeback risk.


Text-to-Pay

Sunbit supports SMS-based payment collection. Staff send the guest a text with a link to Sunbit's prequalification flow. The guest completes the application on their own device and the payment applies to the corresponding Zenoti invoice when Sunbit confirms the transaction is complete.

Text-to-Pay is useful when the guest is not at the front desk at checkout time (for example, for deposits collected between visits). The flow and the fee are otherwise identical to in-store Sunbit.


Post-transaction behaviour

Sunbit operates on a loan-based model; once a loan is completed, Zenoti cannot modify it through the UI.

Action Supported in Zenoti UI What happens
Void No Voids are not available after the loan is completed. Guests contact Sunbit or the merchant coordinates with Sunbit directly.
Refund No UI action Sunbit processes reversals on its side; when complete, Sunbit notifies Zenoti and the invoice status updates accordingly.
Partial refund Not exposed Contact Sunbit support for partial reversals.

If a guest requests a cancellation, contact Sunbit support (or your Sunbit account manager) to initiate the reversal. Do not attempt to issue a separate cash or card refund in Zenoti for a Sunbit loan β€” that would double-refund the guest.


Reconciliation

Layer Source Match key
Zenoti Collections by Invoices filtered to the Sunbit payment method Invoice number + Sunbit loan reference (payment log)
Sunbit Sunbit merchant dashboard β€” per-center transaction view Sunbit loan reference / merchant reference
Bank Sunbit settlement report (per center) Merchant reference carrying Zenoti invoice number

Recommended cadence: reconcile daily per center. Because each center has its own Sunbit merchant account, settlements and fees are per center β€” do not aggregate at the organization level.

Accessing the Sunbit Dashboard. Your center receives access to the Sunbit merchant dashboard via an onboarding email from Sunbit at the time your merchant application is approved. The email contains your dashboard URL and login credentials. If you did not receive the onboarding email, contact Sunbit support.


Handle transaction failures

Failure mode Symptom Resolution
Sunbit unreachable Guest sees a timeout on the Sunbit hosted page. Transient; guest retries. If the issue persists, check Sunbit's status page and switch to a card payment.
Prequalification declined Guest-visible "not approved" message on the Sunbit page. Offer the guest an alternative payment method. Sunbit does not share decline reasons.
Prequalification abandoned Guest left the Sunbit flow; invoice remains unpaid. Collect payment another way or resend via Text-to-Pay.
Amount below $60 / above $10,000 Checkout with Sunbit button is hidden on the HPP. Split the invoice or collect via another method.
Status update not received Sunbit dashboard shows the loan completed but Zenoti still shows "pending". Confirm the Zenoti endpoint is reachable. Sunbit retries automatically, but contact Sunbit support to replay an event if needed.
Authentication error on Sunbit API Configuration calls fail with an "unauthorized" error. Re-enter Sunbit organization credentials in Payment processor onboarding > Sunbit. Confirm the credentials have not been rotated by Sunbit.
Center not Activated Checkout with Sunbit does not appear at that center. Confirm the center's onboarding state. Restart the iframe onboarding if required.
Currency mismatch Sunbit rejects non-USD transactions. Sunbit is USD-only. Use a different processor for non-USD centers.

Limitations

Warning β€” surcharge passthrough prohibited. Sunbit's merchant agreement prohibits passing the 5% merchant fee to guests as a separate surcharge. If your organization has enabled Zenoti's surcharge feature for card payments, that surcharge must not apply to Sunbit transactions. Sunbit transactions are exempt from surcharge passthrough. Charging the 5% fee to guests separately violates Sunbit's terms of service and may result in your merchant account being suspended. Zenoti's surcharge feature targets credit-card transactions; confirm your configuration does not inadvertently apply a surcharge to Sunbit.

  • US only. Sunbit is not available outside the United States.
  • No void through Zenoti. Post-approval cancellations are handled by Sunbit.
  • No refund through Zenoti UI. Reversals arrive after Sunbit processes them on their side.
  • No recurring payments. Sunbit cannot be used for membership billing or scheduled package charges.
  • No terminal / card reader. Sunbit is a BNPL loan product, not a card authorisation processor.
  • Minimum $60, maximum $10,000. Transactions outside this range are not offered Sunbit at checkout.
  • Per-center onboarding. Each center maintains its own Sunbit merchant account.
  • Separate from Stripe Express BNPL. Sunbit is a distinct integration from Stripe Express BNPL options (Affirm, Afterpay, Klarna). Enabling Sunbit does not affect Stripe Express BNPL configuration, and vice versa.

Tips

  • Train front-desk staff on the Sunbit application flow and the $60 / $10,000 eligibility window before enabling it at the center.
  • Display Sunbit financing as a payment option for higher-ticket services or packages where it produces the most value.
  • When a guest needs a refund, route them through Sunbit support directly β€” do not create a separate card refund in Zenoti.
  • Keep a record of each center's Sunbit onboarding state. If Sunbit deactivates a center, the Checkout with Sunbit button disappears without a Zenoti-side configuration change.

Troubleshooting

Problem Likely cause Resolution
Checkout with Sunbit button does not appear on the HPP Center is not yet Activated, or the invoice total is outside the $60–$10,000 range. Check the center's onboarding status in Payment processor onboarding > Sunbit. Verify the invoice total falls within the eligible range.
Guest's Sunbit application is declined Guest did not meet Sunbit's credit criteria. Offer an alternative payment method. Decline reasons are not shared with the merchant.
Invoice remains unpaid after guest completes the Sunbit flow Status update from Sunbit has not yet arrived in Zenoti. Wait a few minutes and refresh the invoice. If the status does not update, confirm the Zenoti endpoint is reachable and contact Sunbit support to replay the event.
Settlement amount is lower than expected The 5% merchant fee has been deducted by Sunbit before settlement. This is expected behavior. Reconcile using the Sunbit merchant dashboard, which shows the gross transaction amount and the fee deducted per transaction.
Center's onboarding status is stuck in Submitted Sunbit's review is still in progress, or additional information is required. Log in to the Sunbit merchant dashboard or contact your Sunbit account manager to check the application status and provide any outstanding documentation.

Was this article helpful?
Your feedback helps us improve our documentation.