Skip to main content

​
Overview

In some cases, you may want to process payments outside of UniBee using your own gateway or a third‑party checkout, while still using UniBee to:
  • Generate invoices
  • Track payment status
  • Keep subscription and revenue data consistent
For this scenario, UniBee supports External Gateway Invoices:
  • UniBee issues and manages the invoice
  • The actual payment happens in an external system
  • Your backend calls UniBee APIs to update the external payment link and to mark the invoice as paid or refunded once the external gateway finishes processing
This is useful for:
  • Integrating with an in‑house payment system or legacy gateway
  • Using a regional payment aggregator not directly supported as a UniBee gateway
  • Migrating gradually from an existing billing system to UniBee

​
Typical Workflow

  1. Create an invoice in UniBee (via the normal invoice creation flow / API).
  2. Redirect the customer to your external checkout using your own payment link.
  3. Update the invoice payment link in UniBee so that internal users can see and reuse the external payment URL if needed.
  4. Mark the invoice as paid in UniBee after the external gateway confirms success.
  5. (Optional) Mark the invoice as refunded in UniBee if you process a refund in the external system.
UniBee will then:
  • Update invoice status (Paid, Refunded, etc.)
  • Trigger the appropriate subscription behavior (e.g., activate or renew a subscription when an invoice is paid)
  • Emit webhook events such as invoice.paid or invoice.refund.success
For a full integration guide (security, webhooks, and common patterns), see
External Gateway Integration Guide.