Kardlane
Operate

Project settings

Every setting that changes how Kardlane handles your trades, what it does by default, and when to change it.

Settings live on each project (dashboard → your project → Settings), in tabs: General, Decisions, Card protection, Vendor questions, Timing, Rejections & re-quotes, and Alerts. Defaults are chosen to be safe: Kardlane decides on its own only when it’s sure, and never messages vendors beyond the trade itself unless you switch that on.

Your price list — what you pay customers, by card and value — is on the project’s Rates page, next to what your vendors actually paid this week. Your system sends it with PUT /v1/price-list; Kardlane uses it to price a sale correctly when the photos show several cards sold as one.

Automatic decisions#

SettingDefaultWhat it does
Auto-approvaloffLets Kardlane close trades itself (success and failure). Off: every outcome comes to you as an escalation with the agent’s reading.
Minimum margin0Quotes below customer rate + this are never chosen; a re-quote below it is never accepted automatically.
Highest sane rate (× customer rate)3A quote above this multiple is treated as a misread, not a price.
Auto-approve value capnoneTrades above this card value always come to you.
AI confidence — success / failure95% / 85%How sure the AI must be before its reading can close a trade. Credit lines read by code don’t need the AI.
Second-pass verifieronAn independent pass must agree with every AI verdict that would close a trade.
Only auto-fail for trusted vendorsonA dishonest vendor could redeem a good card and call it used; untrusted vendors’ failures come to you.

Timing#

SettingDefaultWhat it does
Longest rate wait180 sHard limit for collecting quotes. Each vendor also has its own deadline (default 120 s). The window closes the moment every vendor has quoted or clearly declined (“no need”, “pause Apple for few days”) — a reply in an unusual shape (a price-list line, a total, “1” then the price) is read within a few seconds, so it never holds the window open.
Confirmation timeout10 minHow long to wait for the vendor’s verdict after sending the card. A vendor’s stated wait (“40 minutes”, “1–3h”) extends it.
Per card type—Override the timeout for slow cards (e.g. Sephora 180 min). Up to 5 hours.
Wait for the rest of a partial credit10 minA vendor that loads part of a card (“+20” on a $25 card) often loads the rest soon after. Kardlane waits this long after their last credit before settling on what loaded; 0 settles at once. A credit of the card’s whole printed value never waits, and the confirmation timeout doesn’t cut this wait short.
Let Kardlane apply learned timeoutsOffApply the timeouts Kardlane learns from your vendors (below) without asking. Each can still be undone.

Learned from your vendors#

Kardlane measures how long each vendor really takes to give a verdict on each card type, from the card going out to the vendor confirming or rejecting it, over your last 60 days. Once a vendor has given at least 5 verdicts on a card type and your timeout doesn’t fit them, Settings → Timing suggests one: the slow end (90th percentile) plus a margin, never below half or above 4× your own setting. A vendor’s own suggestion wins over the one for the card across all vendors.

  • Apply uses it for new trades within a minute; your own setting stays as it is underneath. Undo goes back to yours.
  • Dismiss hides it until the numbers move a lot.
  • With Let Kardlane apply learned timeouts on, new suggestions are applied when the loop runs (every 6 hours) and marked “Applied by Kardlane”. Undoing one keeps it off.

Checking in with a quiet vendor#

Off by default, because it messages vendors. When on, Kardlane replies to its own card message if the vendor has said nothing: first after 5 min, then every 5 min, at most 2 times, with your wording (placeholders for amount, card and minutes). Never during a wait the vendor asked for. Each vendor can use the project default, its own timing and wording, or no check-ins at all (Vendors → workflows).

Different check-ins for some cards. Slow cards (some Apple, Sephora) need a gentler pace and different wording than cards that confirm in minutes. Add a card rule: tick the cards (search, Select all, untick to adjust), then set its timing and wording. Blank boxes use the setting for every card, shown greyed out. A card can be in one rule only. Each rule shows when its check-ins land against the slowest of its cards’ timeouts, and warns when one comes after it. At most 0 turns check-ins off for those cards.

Vendors set to “Custom” get the same: their own setting for every card, plus their own card rules. The most specific setting wins, field by field:

  1. this vendor’s rule for the card
  2. the project’s rule for the card
  3. this vendor’s custom setting
  4. the project’s setting

A vendor set to “Never” is never checked in on, whatever the card. A vendor on “Use project settings” follows the project, card rules included. When project check-ins are off, only vendors set to “Custom” get them.

Re-quotes#

SettingDefaultSent when
Reply when a vendor re-quotes“Ok, proceed ✅”Kardlane accepts a re-quote on its own (still profitable and no worse than agreed or than other quotes), or you press Accept new rate.
Reply when you decline a re-quote“No please, don’t load. Return the card 🙏”You press Decline (or call POST /requote with decline).
SettingDefaultWhat it does
Re-quote: move the card to a better quoteonA vendor lowers its price after getting the card and asks whether to go ahead. If another vendor quoted more for this trade (quotes from this trade only, not older than 30 min), the vendor is asked not to load (your decline reply) and the card goes to the highest of them.
Margin threshold (per unit)your minimum marginVendor rate − customer rate. A trade is never just taken below it — the negative-margin setting decides.
Negative margin: proceed and reportoffBefore sending: every quote is below the threshold (maybe a loss) → the card still goes to the best quote. After sending: a lower re-quote no other vendor beats → the vendor is told to proceed. Either way trade.succeeded carries lowMargin and you re-price your customer. Off: those trades come to you. A quote or re-quote under half the customer rate / first quote always comes to you.

When a vendor asks before quoting#

Some vendors ask something before they’ll price a card: “Which country?”, “Single or multiple?”, “First 4 digits?”, “E-code or physical?”, “Need original pic”. A reply like that, with no price in it, isn’t a quote or a decline. That vendor gets extra time to quote (90 s by default, once per trade), and the window’s limit stretches with it. A vendor asking you to hold (“hold on”, “checking”, “1 min”, “稍等”) gets the same extra time; nobody needs to answer that.

SettingDefaultWhat it does
Extra time for that vendor90 s0–300 seconds added to the vendor’s own deadline once it asks.
Answer from the tradeOffReplies to the question (quoting it) with only what the trade says: country, single card or the cards’ values, the value, or e-code / physical card. Anything else (pictures, receipts, other questions) comes to you as a WhatsApp alert. Off: every question comes to you.
…including the first 4 characters of the codeOffOnly when the code is known for sure. The rest is never sent before the card goes out.

If several of your trades asked the same vendor at once, Kardlane doesn’t answer: one answer can’t fit them all, so it comes to you. Questions show on the trade’s timeline with what happened.

Three follow-ups, all off by default because they message the vendor’s group (Settings → Vendor replies → Following up). A vendor gets at most one price follow-up per trade:

SettingDefaultWhat it does
Ask again when a reply has no priceOff“Rate now sir”, “ok” — no number. After 20 s without a price, Kardlane asks once more, as a reply to its own ask: How much for USD 100 APPLE/ITUNES? Words about a card they already hold (“account”, “loading”) don’t count as a reply. Only while that vendor still has time on its deadline; it never adds time.
Nudge a vendor that hasn’t repliedOff · after 60 sNo reply at all to the rate ask. After the wait you set (10–600 s from the ask), Kardlane replies once to its own ask: How much for USD 100 APPLE/ITUNES? Only while that vendor still has at least 20 s on its deadline and the window is still open; it never adds time.
Point out a code the vendor typed wrongOffWhen the vendor writes your code back a character or two off, Kardlane sends once: Please check the code: it ends …L6Q8YF (Q, not O). Only the differing part, never the whole code. Off (or either way): an “invalid” after a misread comes to you instead of failing the card.

When a vendor rejects a card#

Kardlane first works out whether the rejection is about the card or about this vendor — see Failure reasons. Then:

SettingDefaultWhat it does
Send the card again when the vendor can’t read iton“Can’t see it, send again” → the photos go to the same vendor once more.
Crop and straighten the photoson“Send clear and complete cards one by one” → each card is cut out of the photo, turned upright and sent as its own image (the card itself is never altered). A flat image fee applies if the trade then succeeds.
Offer it to the next vendoron“We don’t take this card” → the card goes to the vendor with the next-best quote for this trade that hasn’t had it. After a “screen card” refusal, vendors that have completed a screen photo for you before go first (still highest quote first).
Use quotes up to30 min oldOnly quotes from this trade’s own rate window, and only this recent. Older → the card fails as retryable instead.
Most vendors to try after the first10–3.

Repeat cards#

SettingDefaultWhat it does
Card history guardonChecks every card against your earlier trades (same photo or same code) before any vendor is asked.
Fail repeat cards automaticallyonA certain repeat of a card that sold, is in progress, or was rejected as used closes as trade.failed (kind duplicate). Off: it comes to you.
Note: Cards rejected only as not active yet, unreadable, or refused by one vendor never count as repeats — your customer can submit them again.

Testing#

Shadow mode does everything real — asks vendors, picks the best rate — but stops before sending the card, so nothing is ever redeemed. Use it to prove your vendor setup before going live. Turning the card history guard off is only for deliberate tests with known-bad cards.

Alerts#

WhatsApp alerts go to the numbers you list per project (or your organization’s list). Each kind can be switched on or off: trades needing review (also used for a vendor changing its verdict after close), failed cards, a WhatsApp number disconnecting or no longer receiving messages (it can show connected while nothing comes in), the AI being unavailable, webhook delivery failing, billing, the daily summary, unsupported card types.