Description
AffCoff is a catalog entity in the aff.bio database. Main database domain: affcoff.io. The card is linked to 3 sources and 4 raw evidence records. Public contact signals: email: 1, Telegram: 1. aff.bio keeps this as a verifiable evidence layer; disputed facts and contacts are not treated as confirmed without review.What is AffCoff
This card summarizes how AffCoff appears as a market participant in affiliate, CPA, performance marketing or iGaming-related sources. aff.bio separates public summary information from raw evidence and does not treat source mentions as guarantees.
Work context for AffCoff
The main domain linked with this card is affcoff.io. Check that the brand, domain and public pages match before using the information for outreach, campaign launch or payment.
Linked source records in the database: 3. A higher source count can be useful for verification, but conditions, contacts, GEO, pricing and payout details should be confirmed in primary sources.
Contacts and public data
Public contacts and links are shown only after filtering obvious source noise, footer contacts, tracking links and raw parser data. If a field is missing, treat it as something to check, not as a confirmed absence.
What to verify before working with AffCoff
- official website and clean domain;
- current terms, GEO, traffic-source restrictions or service scope;
- public contacts and support channels;
- related companies, programs, teams, tools or events;
- whether the card is a duplicate, outdated source or thin import.
Full information about AffCoff
Use this page as a structured starting point: review the summary, compare source records and check important facts manually before making business decisions.
catalog_card · editorial_html_review_v2 · 2
FAQ about AffCoff
What is AffCoff?
AffCoff is a catalog cards. This public aff.bio reference page helps understand the entity category and what to verify before contact, campaign launch or payment. Main domain to verify: affcoff.io.
Who may use AffCoff?
Consider AffCoff if you need a “Catalog cards” entity and are ready to verify terms with the official site, manager or dashboard before starting.
Who is AffCoff not for?
AffCoff is not enough if you need guaranteed payouts, exact GEOs, rates, licenses, prices or terms without additional verification. aff.bio does not replace a contract, program rules or official support.
How to compare AffCoff with alternatives?
Compare AffCoff by category, domain, source count, start conditions, traffic restrictions, payouts, support and data freshness. If a fact is missing, treat it as something to verify, not as a promise.
What should be checked before working with AffCoff?
Check the official domain, current rules, GEO and traffic-source restrictions, payment terms, manager contacts and last update date. Source count linked in aff.bio: 3.
Contacts and links
Website
Telegram / messengers
Support
GEO / verticals / attributes
Payouts
Related people / companies
| Name / company | Role / relation |
|---|---|
| Reliable relations are not found yet; uncertain contacts stay in evidence below. | |
Source records and evidence
| Source | Type | Name / domain | URL |
|---|---|---|---|
| CPA Rip | Affiliate programs | Affcoff.io | source |
| CPA Rip | Affiliate programs | Affcoff.io | source |
| Gembla | Catalog cards | AffCoff | source |
| Partnerkin | affiliate_program_or_company | AffCoff | source |
Technical JSON/attributes
CPA Rip · source record
{
"attributes summary": {
"Hold": "14 days (only until the first payout – no further hold).",
"Minimum payout": "$100;",
"Time": "2 times a week.",
"https": "//affcoff.io",
"jsonld_url": "https://cpa.rip/en/partners/affcoff-io/",
"language": "en",
"trust": "medium",
"source_import_mode": "raw_source_layer"
},
"email count": 0,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 1.0
}CPA Rip · source record
{
"attributes summary": {
"https": "//affcoff.io",
"jsonld_url": "https://cpa.rip/partners/affcoff-io/",
"language": "ru",
"trust": "medium",
"source_import_mode": "raw_source_layer"
},
"email count": 0,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 1.0
}Gembla · source record
{
"attributes summary": {
"feedback": "support@affcoff.io"
},
"email count": 1,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 1.0
}Partnerkin · source record
{
"attributes summary": {
"parser": "partnerkin_local_archive_card_v2",
"archive": "PartnerkinArchive",
"needs_manual_review": "True",
"source_policy": "offline_archive_raw_review_only",
"partnerkin_params": [
"30-40%",
"USDT"
],
"official_site_visible": "affcoff.io",
"source_import_mode": "pilot_raw_review_only",
"source_language": "ru",
"market": "RU_CIS",
"trust": "medium",
"clean_reparsed_at": "2026-05-12T10:25:01.691635+00:00",
"clean_reparse_reason": "partnerkin_source_specific_parser_removed_navigation_footer_and_extracted_card_fields"
},
"email count": 0,
"telegram count": 0,
"verification": "Source record used for verification",
"confidence": 0.78
}