Kardlane
Operate

Vendors

How vendors are asked, trusted, chosen and set up — and the per-vendor settings that make Kardlane fit how each one works.

A vendor is a WhatsApp group linked to your project. Kardlane learns nothing about a vendor’s prices in advance: for every trade it asks, and only that vendor’s answer to that question is used. (A price list the vendor sends as the answer counts, if the price for this card can be read from it.)

Trust#

A vendor is trusted when you mark it so, or once it has completed enough trades with you (default 10, set per vendor). Only trusted vendors’ outcomes close trades automatically — the most common escalation reason is trusted_vendor. Mark reliable vendors trusted as soon as you’re comfortable.

Your team in vendor groups#

If people on your side also post in your vendor groups, such as a VA who checks rates a few times a day, add them under Settings → Your team in vendor groups. Pick them from recent senders, or add a number or WhatsApp name. Then:

  • Their messages are never read as a vendor’s quote, decline or verdict, and aren’t part of what Kardlane learns from.
  • A vendor replying to them, or filling in their rate list (“Nike $100? no need … Sephora $50? 1100”), isn’t taken as an answer to Kardlane.
  • A reply that doesn’t quote anyone, sent after they asked in the same group, could be for either of you. It’s kept on the trade but never used as a quote or a decline.

Even without this, a vendor’s reply that quotes any message other than Kardlane’s rate request is never counted as their answer to Kardlane: an answer to someone else isn’t a quote for your trade.

How a vendor is asked#

  • Request format — by default USD 100 APPLE/ITUNES (with CODE for a typed code). Set your own template per vendor to match how they like to be asked.
  • Rate unit — per unit, total, or auto-detected. Kardlane converts every quote to one comparable rate per unit in your payout currency.
  • Vendors who quote in another currency (e.g. RMB): set the currency, and either a fixed conversion rate or use the vendor’s own rate. With the vendor’s rate, Kardlane asks only for the card rate first. Once they quote, it uses the conversion rate they last posted in the group if it’s recent enough; otherwise it asks then, in your wording (e.g. naira rate?). The answer must come within that vendor’s usual rate deadline — asking never adds time; without it (and with no fallback rate) their quote isn’t used. “Recent enough” is learned from how often their rate has changed (between 1 and 6 hours; Learn from chat history reads past posts), or you set it yourself.
  • Card prefixes they won’t take — when a vendor says it won’t take cards starting a certain way (“6347 不要”, “cvs 不可用的卡头 6037”, “9 start no”), Kardlane records it on that vendor and stops asking them about such cards (matched on the code or the card number read off the photo). You can add or remove prefixes yourself.
  • How replies are read — in a list of values (“$100 945 / $50 no”) only the line for your card’s value counts. When several of the vendor’s staff quote, the latest price that stands counts; a correction with no new price (“mistake”, “ignore that”) cancels the earlier one.
  • Adjustments — add or take a fixed amount or percentage for some cards (by type, e-code/physical, value range).
  • Notes — anything the AI should know about this vendor’s style; it reads them with every reply.

Rules for each vendor#

On a vendor’s page, Rules for this vendor holds up to 20 short rules the AI reads when it handles that vendor — for example “they post a screenshot of the card before loading it; that isn’t a credit”. Each rule applies to some cards or all of them, and before quoting (when their replies are read for a price), after the card is sent (when their messages are read for a verdict), or both. Rules are context about how the vendor works, not instructions that override anything: they never change a price, a verdict, an approval or a payout. Prices still have to come from the vendor’s own messages, and verdicts still go through every check. Each rule shows who last changed it and when.

A rule can also let Kardlane reply. You write When (the situation, e.g. “the vendor asks whether the card is physical”) and Say (e.g. Physical card). The AI can only point at the rule; Kardlane sends your words exactly, as a reply to the vendor’s message, and only when all of these hold:

  • Reply using vendor rules is on (Settings → Vendor replies → Following up). It’s off by default, because it messages vendors.
  • The rule is on and covers this card, after the card is sent.
  • The card has been sent and the trade is waiting on the vendor — not closed, with a person, paused or stopped.
  • No new rate from the vendor is waiting on a decision, and nothing in their messages reports a problem with the card.
  • That rule hasn’t replied on this trade yet (each rule replies at most once per trade).

A reply can’t contain a price, an amount, a number of 4 or more digits, a card code, a link, an email address or a phone number — the vendor page won’t save one that does. Each reply shows on the trade’s timeline as Replied using a vendor rule. Sending a reply never settles or changes the trade: the AI’s reading is handled exactly as it would be without it.

Choosing between vendors#

The best rate that passes your margin wins. Quotes within a small tolerance count as a tie, broken by your preference rules, then vendor priority (lower first), then reliability (how often the vendor gives a verdict in time), then who quoted first. Routing rules can send a card type to a specific vendor regardless of rates, with a fallback. Look-alike cards are spread across vendors where possible so replies stay unambiguous. The timeline of every trade shows the full ranking and why.

Screen photos#

Customers sometimes photograph their card on another phone’s screen, and some vendors refuse that or pay less. Kardlane notes when a card photo is of a screen and remembers which of your vendors have completed one. The card always goes to the best quote first; if that vendor refuses it as a “screen card”, it goes next to the vendors that have accepted screen photos before, highest quote first. The photo is always sent exactly as the customer took it.

Workflows#

Actions per vendor at four moments — each can wait a while and be limited to some trades:

WhenTypical use
Before the card is sentA note the vendor needs with every card.
After a successful tradeYour account details for payment (only after the vendor confirmed the load).
After a failed tradeAsking for the card back, or a thank-you.
When a trade goes to reviewLetting the vendor know someone will reply.

Each vendor can also override the project’s check-ins: its own timing and wording, its own rules for some cards, or none at all.

What Kardlane understands from vendors#

  • Quotes in many shapes (1130, 28000 25, 100*1150 + 50*1100), foreign-unit rates, and clear declines (“no need”, “pause”, ticket-tagged replies).
  • Credit lines and bookkeeping-bot ledgers — including one total for several cards — matched to your card by its code ending.
  • Waits (“wait 40 minutes”, “1–3h”), re-quotes, reversals (撤回), and failure wordings in several languages.
  • Placeholders (“1”, “.”, “0”, “+”, “'”). Vendor staff send these to claim a request before answering it. They’re never a price, a verdict, or evidence for one, so a lone “0” is never read as a $0 balance or a “+” as a credit.

How Kardlane learns#

Every vendor message is logged with how it was read, and every case where a person decided differently from the agent is kept. Every 6 hours Kardlane groups the wordings it doesn’t read well yet across all its users, and proposes fixes: a new reader for wordings that never decide a card (greetings, price broadcasts, “we’re not buying today”), or a note for the AI about what a wording means.

  • Only a message’s shape is used: lowercased, with every number, code and ticket tag masked. Card codes, PINs, amounts and names never leave your trades.
  • Each fix is replayed on past messages first and only ships if it touches nothing that decided a card. A Kardlane person approves every one.
  • Learned readers can only say a message is chatter, an acknowledgement, a question, or a decline while you’re asking for a rate. They never mark a card redeemed or failed, and built-in readers always come first.
  • After a fix ships it is watched. If what it reads turns out to matter, it switches itself off.