Kendeepp

Thanks for reading it that closely. As far as I can tell, the first real payout is the only reliable check. PayPal's C2 fee page lists a 4.40% + fixed fee for receiving international commercial transactions, and separate Payouts fees that are charged to the sender, but neither that page nor RapidAPI's Payouts and Finance doc says which one, if any, applies when RapidAPI pays a provider. That's why I left it as not verified instead of guessing. If you want an answer before then, asking PayPal or RapidAPI support directly is the only other route I know of. Once a real payout arrives, its transaction details should show whether a fee was taken, and I'll update the post.

Quick follow-up: v1.8 now has a separate "So far" column that divides by MIN(DAY(TODAY()), days in the month), and the counts accept both TRUE and 1. I checked it in LibreOffice; Excel is still untested on my side. Thanks again for the nudge.

Thanks Yunus — locking nonexistent days is exactly how I wanted to kill the >100% case instead of papering over it. You're right that a full-month DAY(EOMONTH()) denominator understates the current month until it ends; a separate "so far" column with MIN(DAY(TODAY()), DAY(EOMONTH(...))) is a clean fix, and I'll call that out. Good catch on Excel checkboxes too — TRUE/FALSE vs 1/0 depends on how the cells were inserted, so COUNTIF on TRUE needs a retest there.

Thanks — Content-tab-only vs email-only each leave a gap, so doing both (file in Library first, then tell buyers) is the part I care about most. Glad that pairing landed.

Appreciate that. 1920×1080 looking “safe” while failing 2:1 is exactly the trap I wanted to flag. Pairing the ratio check with “enough images” helps avoid the top rejection reason the upload guide calls out.

Thanks — yes, filling the self-check before touching the Dashboard keeps the answers tied to what you already documented. The privacy-practices vs live policy vs code triangle is where quiet mismatches usually hide; worth re-checking those three together right before submit.

Appreciate you calling that out — the free BASIC million-request default is easy to glance past, and it gets painful fast if the origin isn't validating X-RapidAPI-* headers. Glad that line stuck.

Glad the $25 example made the math click. Yeah, once you stack RapidAPI's cut and that wire fee, batching well above the $150 floor is pretty much the only way thin plans stay sane.

Thanks — that unit mismatch is exactly why I dug into those listings. Happy it landed; comparing sticker prices alone is pretty misleading without knowing what each vendor actually meters.

That’s a fair read of the post. Codes don’t stack: if auto-apply is on and someone arrives with a different code, the larger discount is the one that applies, and it’s still one code per product. PPP versus a code is the same rule — the buyer gets the better of the two, and the only way to force the code is to turn PPP off for everyone. On the Discover side, the documented fee line stays the flat 30% (processing included); there isn’t a published formula for the exact net after a code, so the sales CSV is the right check rather than invented math.