Advanced Implementation

Varies by topic

This hub covers optional work you can add on top of the core flow in Implementation. Use it when you want stronger branding, pre-filled onboarding data, programmatic bills and vendors, category setup, linked-account control, customer activation toggles, webhooks, or a Custom Banking integration.

You can adopt topics in any order; most teams start with theming and Implementation (if you have not finished the core embed yet), then add API Reference or Webhook Events as product needs grow.

Optional by design

Nothing here is required to ship Ready-to-Launch Bill Pay. Several features need Unit-side configuration (for example pre-fill or team-list endpoints, webhook subscriptions, or Ready-to-Launch API tokens). When a page says to contact Unit, plan for that in your rollout.

Typical starting points

• Theming — align the White-Label App with your brand.
• Implementation — core embed and platform setup if you have not finished it yet.

In this section

Topic	What it’s for
Theming	Colors, logos, fonts, and settings-json for the White-Label App
Pre-filling User Information	Let Unit pre-fill the bill pay application from your API
API Reference	Bill Pay HTTP APIs (bills, vendors, categories, linked accounts, customer activation, reactivation URL)
Webhook Events	Real-time notifications for Bill Pay activity
With Custom Banking	Ready-to-Launch Bill Pay when you already use Custom Banking