Skip to main content
Barker Yield Engine supports two integration modes. They run against the same engines and the same on-chain fee split — the only difference is where the deposit/withdraw UI lives.

Side-by-side

Decision tree

Pick Embed if any of the following:
  • You want to ship in a sprint, not a quarter
  • You don’t have a frontend engineer with on-chain experience available
  • The deposit flow is a self-contained “Earn” tab, not interleaved with other steps
  • You’re A/B testing whether yield even belongs in your product before committing engineering time
Pick Headless API if any of the following:
  • The deposit must be one step inside a longer flow (KYC → deposit → top-up → confirmation)
  • Your product has a custom design system that an iframe would break
  • You want native mobile (iOS / Android) UI, not WebView
  • You want to display multiple Barker products (e.g. 3 risk tiers) on one screen with custom comparison UI
  • Regulatory or InfoSec posture requires that the deposit UI runs on your origin only

Can I mix both?

Yes. They’re not mutually exclusive — same partner account, same engine, same key. Common patterns:
  • Embed for web, headless for mobile — fastest desktop launch, native iOS/Android in v2
  • Embed in onboarding, headless in dashboard — quick “Try yield” CTA, deeper portfolio view later
  • Headless for primary, embed as fallback — internal “Open in Barker” debug link
The same product slug works in both modes.

What’s next