White-Label SaaS

Add a DutyClaims-powered refund workflow to your SaaS without owning the operational headache.

White-labeling lets your platform keep the customer relationship while DutyClaims handles the refund workflow underneath. Your clients stop asking where to send their IEEPA refund questions, your team stops improvising an answer, and your product gains a new revenue layer without becoming a customs-financing operator.

Partner Admin Guide Developer Hub API Quickstart

What white-labeling means here

DutyClaims gives SaaS partners a branded hosted intake and customer journey that can live under the partner relationship layer. Your logo, support routing, and hosted experience can be partner-facing, but eligibility, offer generation, agreement workflow, funding, and servicing still run through DutyClaims.

Your product keeps the front-door relationship and branded user experience.
DutyClaims powers the refund workflow behind that experience.
Your team does not need to invent a customs-refund operating stack from scratch.

Why partners use it

Keep clients happy: customers get a concrete answer when they ask how to recover IEEPA overpayments instead of hearing “we do not handle that.”
Unlock additional revenue: the refund workflow can become an expansion surface inside your existing SaaS relationship.
Reduce support drag: your team stops fielding the same “How do I get my IEEPA refund?” question without a real product path behind it.
Stay focused on your product: DutyClaims handles the refund-specific complexity so your roadmap does not turn into a trade-finance operations backlog.

How it works

Your organization is onboarded as a SaaS partner tenant.
Your partner-admin team configures branding, disclosures, support routing, credentials, and launch readiness.
DutyClaims reviews the hosted setup and controls go-live.
Customers enter through the hosted tenant, complete onboarding, and move into the supported customer-safe dashboard and claim flow.
DutyClaims handles the underlying refund lifecycle while your platform keeps the relationship and branded surface.

What you get

Partner-branded hosted landing, auth, onboarding, and dashboard flow.
Main-host partner-admin workspace for setup, review state, and launch readiness.
Managed credentials, webhook support, and API tenancy for integration work.
DutyClaims-owned financing and operational controls behind the branded experience.

What DutyClaims handles for you

Refund-workflow product logic, hosted runtime, and customer-safe route support.
DutyClaims-controlled review, launch gating, and hosted operational truth.
Eligibility, agreement, offer, funding, and servicing workflows that should not be improvised by each SaaS partner separately.
Host and launch controls such as dark launch, domain readiness, failover, and suspension.

What stays true

White-label does not turn the partner into the financing provider.
The hosted experience is intentionally bounded to the supported customer-safe route set.
Branding readiness, hosted-site readiness, and sender-domain readiness are separate states.
Production launch remains admin-controlled in the current platform.

Best fit

Compliance and trade-workflow SaaS products that already own importer relationships.
Platforms that want new revenue without standing up an internal refund-ops function.
Teams that want a branded answer to IEEPA refund demand rather than referring customers out of product.