Enable DeFi Kickbacks with FinTag
FinTag is a simple way to connect your website to the decentralized finance (DeFi) ecosystem. It uses HTML meta tags to define your wallet address and referral fee structure for on-chain kickbacks. These tags should be placed on your base domain and any subdomains where you want to enable FinTag functionality.
Required Meta Tags
<meta property="ican:xcb" content="cb00…" /> <meta property="defi:fee" content="1.00%" />
ican:xcb
- Your ICAN/XCB address (generated via CorePass).
defi:fee
- The percentage you want to earn from each successful referral transaction (e.g.,
1.34%
). - Allowed values:
0.00%
to4.00%
. - Default value:
0.00%
. - Up to two decimal places.
- The percentage you want to earn from each successful referral transaction (e.g.,
Optional JSON Object
{
"ican:xcb": "cb00…",
"defi:fee": "1.00%"
}
ican:xcb
: Your ICAN/XCB address (same as in the meta tag).defi:fee
: Percentage fee for referrals (same as in the meta tag, e.g.,1.34%
).
Place this JSON at …url…/fintag
to enable automatic FinTag detection for your specific site.
How referrals work
When a user publishes a payment or donation on your site, the browser usually delivers a Referer
header to us. This allows us to validate your FinTag and trigger the DeFi kickback.
Referrer is sent when:
- Users click regular
<a href>
links rel="noreferrer"
is not used- Page uses a standard referrer policy (e.g.
strict-origin-when-cross-origin
)
Referrer is blocked when:
- Links use
rel="noreferrer"
or meta tag<meta name="referrer" content="no-referrer">
- HTTPS → HTTP (downgrade) links
- User's browser is in hardened or private mode (e.g. Brave, Arc, Safari, Firefox private)
- Extensions like uBlock Origin, Ghostery, or DuckDuckGo strip headers
Recommendations:
- Use standard
<a href>
links withoutrel="noreferrer"
- Keep your site and links using
https://
only - Do not override referrer policy unless required
- Educate your affiliates to avoid referral-blocking setups
- Place your FinTag meta tags inside the
<head>
of your HTML document to exact pages you want get kickbacks for
FinTag validation flow
When a payment is made, we follow this validation process to determine which FinTag to use for the kickback:
Extract referrer link
We capture the referrer URL from the browser's Referer header when available.
Try JSON endpoint first
We attempt to fetch JSON data from
…url…/fintag
Example valid JSON response:{"ican:xcb": "cb…","defi:fee": "1.00%"}If valid JSON is returned, we use this data for the kickback.
Domain-level validation
If JSON is not available or invalid, we check the (sub)domain level for meta tags.
<meta name="ican:xcb" content="cb…"><meta name="defi:fee" content="1.00%">
💡 Priority order
- JSON endpoint (
/fintag
) - Domain-level meta tags
After generating, place your FinTag meta tags inside the <head>
of your HTML document.