CollectRefund Embedded
Put unclaimed-property recovery inside your product.
Connect your users with money they are already owed through a direct API, hosted flow, or referral experience.
- Recovered for clients
- $7.5M+
- Clients helped
- 1,000+
- Records monitored
- 250M+
- Managed-recovery states
- 50
Backed by Techstars and USC
Fintech, banking, payroll, benefits, insurance, and credit products.
CollectRefund Embedded is built for product teams whose users have money waiting in state unclaimed-property systems. Which is most of them.
Value your users can feel
Surfacing money a user is already owed builds the kind of trust and engagement no rewards program can match.
Integration on your terms
Direct API, hosted flow, referral handoff, white-label, or co-branded, choose the depth that fits your roadmap.
CollectRefund does the heavy lifting
Identity confirmation, state processes, documentation, and recovery operations stay on CollectRefund’s side of the line.
Integration options
Direct API
JSON endpoints for search, identity confirmation, and monitoring enrollment inside your own UI.
Hosted flow
Send users to a CollectRefund-hosted experience with your attribution.
Referral handoff
The lightest lift: a tracked referral into CollectRefund’s own funnel.
White-label & Co-branded
The CollectRefund engine under your brand, or a shared experience carrying both.
What your users would see.
A polished, phone-first search with identity confirmation built in. All data shown is representative.
Embedded search · example experience, representative data
- Mobile number
- (555) 010-1234
- First name
- Jordan
- Last name
- Avery
- Result
- 3 possible claims · representative aggregate value $1,900
- Supported states
- CA CO GA HI MN NE NY
- Integration
- JSON API / Hosted flow / White-label
A mobile number begins the search. First and last name may be required when a phone number alone cannot produce a confident match. Identity confirmation is required before match details are shown. Monitoring enrollment is offered after the first search.
From consent to recovery.
When a user pursues a claim, CollectRefund’s managed recovery process takes over. We handle the documentation, state submission, follow-up, and payment.
- 01
Consent & Search
A mobile number begins the search inside your product or the hosted flow.
- 02
Identity confirmation
Before any match details are shown, the user confirms their identity, protecting their data and yours.
- 03
Possible claims appear
The user sees how many possible claims were found and a representative aggregate value.
- 04
Recovery and monitoring
If the user pursues recovery, CollectRefund manages the claim. Monitoring enrollment keeps watching for new matches.
Consent first, identity confirmed, data minimized.
Users consent before a search runs, and identity confirmation is required before match details are shown. Partners receive only the data their integration model requires, never a user’s full claim file.
Family monitoring, coming soon
Monitoring for funds tied to a user’s family members is in development and will be announced to partners when it is live.
Standard OAuth2, no surprises.
Partner integrations authenticate with OAuth2 client credentials: your service exchanges its credentials for a short-lived access token and calls the API server-to-server.
API documentation, endpoints, schemas, and integration guides are shared with approved partners after a request-access review. No live endpoints or credentials are published here.
Pricing.
Partnership pricing, recovery fees, and any commercial or revenue-sharing terms are established in the applicable partner agreement.
Integration questions, answered
What integration models does CollectRefund Embedded support?
A direct API, a hosted flow, referral handoff, white-label, and co-branded experiences. Partners choose the model that fits their product and compliance needs.
Where does CollectRefund Embedded work today?
CollectRefund Embedded currently supports All 50 states. CollectRefund Monitoring covers All 50 states.
How is user privacy and consent handled?
Users consent to the search before it runs, and identity confirmation is required before match details are shown. Partners never receive more personal data than the integration model requires.
What does an embedded partnership cost?
Partnership pricing, recovery fees, and any commercial or revenue-sharing terms are established in the applicable partner agreement.
How do we get the API documentation?
API documentation is shared with approved partners. Request access with a short description of your product and use case, and the partnerships team will follow up.
Request access to CollectRefund Embedded
API documentation is shared with approved partners. Tell us about your product and use case to request access.
Put unclaimed-property recovery inside your product.
Direct API, hosted flow, referral, white-label, or co-branded, start the conversation.