Platform
The compliance layer between your creators and your processor.
Tumban vets every creator profile against the prohibited business lists of the processors you actually use — Stripe, PayPal, Adyen, Braintree, Square — plus Visa VAMP and Mastercard BRAM. One API call in your payout loop.
10,800+ profiles
Vetted in production to date
Under a minute
Per decision, inside your payout loop
7 policy sets
Stripe, PayPal, Adyen, Braintree, Square, Visa VAMP, Mastercard BRAM — maintained and updated
Four capabilities. One decision.
Every evaluation runs the full stack — content, network, policy, decision — and returns a single scored recommendation.
Content screening
Examines what creators actually sell — listings, descriptions, uploads, storefronts — against the prohibited business categories of each processor: piracy, counterfeit, adult, gambling, MLM, regulated goods.
Network analysis
Traces where a creator's traffic comes from and where their outbound links point. A clean storefront with inbound traffic from piracy communities is a signal no content classifier sees.
Policy matching
Findings map to the specific rules of the processors you use — Stripe restricted businesses §6.3, PayPal AUP, Adyen, Braintree, Square — plus Visa VAMP and Mastercard BRAM. Not generic risk rules. Your rules.
Payout decision API
Approve, hold, or escalate returned to your payout loop with a risk score, category, policy references, and audit ID. Tumban scores and recommends — your team makes the final call, and every decision is logged.
One API call. Three stages.
POST /v1/creators/eval in your payout loop. Ingestion, evaluation, decision — every step logged.
Your decisions, where your team works
API
One endpoint in your payout loop. The decision, score, and policy references come back in the response. No SDK, no snippet, no migration.
Dashboard
Review held and escalated creators with the evidence behind each decision — what was found, where, and which policy it maps to.
Audit trail
Every decision logged with an audit ID your T&S, legal, and processor relations teams can produce when it matters.
Frequently asked questions
What is payout compliance?
Vetting who you pay, not what they post. Payout compliance maps creator activity against the prohibited business lists of your payment processors before money moves — so a violation is caught before it becomes an enforcement event.
How is this different from content moderation?
Content moderation catches bad content on your platform. Tumban catches bad payout recipients — including creators whose violations are only visible off-platform, in link graphs and cross-platform activity. Keep your moderation stack; Tumban sits in a different flow.
How is this different from KYC?
KYC verifies who a creator is. Tumban evaluates what they sell and where their traffic flows, mapped against processor policy. A creator can pass identity verification and still be selling something your processor prohibits. The two layers are complementary.
Which processors and card networks do you cover?
Stripe, PayPal, Adyen, Braintree, and Square prohibited business lists, plus Visa VAMP and Mastercard BRAM card network programs. Evaluations map to the specific policies of the processors your platform actually uses.
Does Tumban make the payout decision?
No. Tumban returns a scored recommendation — approve, hold, or escalate — with the evidence and policy references behind it. Your team makes the final call. Every decision is logged with a full audit trail.
How long does integration take?
One API endpoint in your payout loop. Most platforms integrate in days, not months. No platform migration, no SDK, no JavaScript snippet — an API call where you already decide to pay.
See it against your processor mix.
Thirty minutes, your payout flow, your processors.