Revion Crew Board

The domain fix landed in the blind window: the merchant row read https://biopepusa.com as of the 15 Sep read (it was www at the 2 Sep read). Since 13 Sep mrc_roNy1mlK9Ij5 showed four sessions and zero payment intents: cs_RVasVZH_AAxR1qMea1PK $109.00 and cs_EZO-PKMQnMyecR0VfwTx $3,277.87 (no buyer email), then cs_ZK_B_CCbydE0g6S43ljT and cs_xzPaO8-h-7F5c3TwHr1C, both $69.99 from info@biopepusa.com. Nobody got as far as submitting a card. REV-241 (PR #461, prohibited products allowed at checkout by default) shipped 15 Sep as a plausible fix if BAC Water was the wall; nobody has re-run Biopep's cart to check, and REV-231, which asked Nur to confirm the BAC Water refusal directly, no longer appears in today's Linear pull either way.

Two days running now with nothing fresh: the DB is down again today, same as yesterday, so none of it has been re-checked against what actually happened since 13 Sep.

Next action

Ask Casey to try the $69.99 cart again today, now that REV-241 has had two days to reach production, and email him regardless: what he saw on the checkout screen if it still fails. Get Nur's BAC Water answer directly since REV-241 changing the default is not the same as confirming what Biopep actually hit.

As of the 15 Sep read, #rhp-rhpeptides ended on Jarrod's 1 Sep 05:57Z message: "that text is from the master document, not the one you signed... I will discuss with Aadil today and get back to you." Your 31 Aug 16:36Z answer to his Washington question rested on three things: Revion is the seller of record, "Revion is registered in Florida today", and sections 8.5 and 8.7. RHP: 0 sessions since 13 Sep, fee_rate 14. None of that has been re-checked in two days, Slack is down again today.

REV-196 ("Turn OFF Florida sales-tax collection until registered") is still [In Progress] p1 @nur in today's Linear pull, unchanged since the suppression code merged 15 Sep (PR #465). The refund and TaxJar-purge parts of REV-196 are still unshipped, and no commit has touched it today.

Next action

Check whether a fresh Florida quote now comes back at $0 before replying to Jarrod. Still get the Florida registration fact and the executed RHP agreement from Aadil, since REV-196 turning tax off does not by itself answer whether Revion is registered.

REV-250 "Seven Sigma: get bank details before the 18 Sep payout" ([Todo] p1 @tim) is unchanged in today's Linear pull. No detail on Seven Sigma is in any readable source today either; Slack and the DB are both down again, so whether they have transacted yet, what they are owed, or who the contact is stays unverified. REV-244 (Cloudflare blocks Seven Sigma's and Bioscience's webhooks) is also unchanged, still open.

New today, and it raises the stakes on this deadline: REV-256 "Close out sent payouts: bank reference and sent date, not stuck in processing" ([Todo] p1 @nur), filed today. If payouts are getting stuck in processing platform-wide, Seven Sigma's first payout tomorrow is walking into the same failure mode, not a clean run.

Next action

Get Seven Sigma's bank details in today, not tomorrow. Ask Nur what REV-256 found before assuming tomorrow's run will actually complete once the details are in.

REV-233 (build the box, live paid order Wed, Apex switched by Fri 18 Sep) has dropped out of today's Linear open-issues pull entirely, and REV-234 (Narboto's QA plan, M1 Wed + M2 Thu with you) is still [Todo] p1, unchanged since 16 Sep. Read together with today's git, the likely story is that M1 ran and found real defects: PR #480 "Align REV-233 embedded Visa checkout with approved box spec", PR #481 "postmerge P1 fixes" (recovery failure now keeps the box locked as review rather than silently wrong), PR #482/#483 (a box that was expiring silently instead of showing the notice, now guarded), a separate fix to "recover embedded payment retries and restore iframe startup watchdog", and PR #477 off a codex-assisted branch fixing the WooCommerce embedding configuration itself. REV-239 (Apple Pay in the box) is also now filed, p1.

None of this has been confirmed working end to end by QA today; whether M2 with you has happened, or whether M1's defects are now actually closed rather than just committed, is not in any readable source. Today is also the day Synergy Labs, on a different but adjacent checkout path, started showing buyers "Card processing is temporarily unavailable" (REV-254, see Nur's section), worth checking whether that and today's box fixes share a root cause before you sign off on tomorrow's switch.

Next action

Get a straight answer from Narboto and Nur today: did M1's defects get fixed by tonight's batch, has M2 run, and is there a real pass/fail record anywhere. Do not let the Friday switch happen on "it compiled."

REV-251 "Apex: cross-check the 25 approved September payments against Matt cancelled orders" ([Todo] p2 @tim) is unchanged in today's Linear pull. Matt is almost certainly Matthew Jensen, the Apex contact you and Aadil were meant to call. No detail on which orders Matt disputes is in any readable source today.

New today: REV-256 (see Aadil's top item) suggests sent payouts can get stuck in processing without a bank reference. Cross-checking cancelled orders is moot if the payout itself has not actually landed yet; check REV-256's outcome first.

Next action

Get the list of cancelled order numbers from Matt on your call, and check none of the 25 approved payments were built from an order Woo shows cancelled. First confirm with Aadil/Nur that the transfer itself cleared, not just that it was approved.

As of the 15 Sep read: 11 Sep run, Halo $1.32, Zen $801.06; 14 Sep run, Halo $358.16 (Mercury ••••2806), Narboto inc $0.09, Zen $2,491.16; Andrew, 15 Sep 13:12Z: "others got paid". The 1 Sep draft was also $358.16; if those are the same two orders, the 1 Sep draft was either never sent or sent and never recorded, and in the second case Halo has now been paid twice. The 27 Aug $1,139.16 (9 orders) had not appeared in any run since, and no reference for it was visible. None of this has been re-checked in two days now, Slack is down again.

New today: REV-256's "sent payouts stuck in processing, no bank reference" finding is exactly the failure shape this task has been chasing for Halo specifically. Worth asking Nur whether Halo's runs are part of what REV-256 found.

Next action

Ask Andrew for the bank references of the 27 Aug and 1 Sep Halo drafts and of the 15 Sep send, check each one is recorded in Revion, then close REV-163 with Aadil.

As of the 15 Sep read, #best-peptide-lab: your 31 Aug 09:06Z follow-up offered 20 minutes to run the first embedded order together, no reply, then Slackbot, 11 Sep 09:44Z, the team removed themselves. Merchant row: active, banking approved 2 Sep, contact dev@guardedpaypro.com, fee 12, 0 sessions and 0 orders since 13 Sep. None of it has been re-checked today, Slack is down again for a second straight day.

REV-247 (rotate the "GuardedPay" password leaked in Core Engineering) is still open, unchanged today. Note for the record: today's git also carries a branch named "payment-links-guardedpay" for an unrelated payment-links feature (guarded catalogue prices), a naming coincidence, not the same "GuardedPay" as this merchant's dev@guardedpaypro.com contact; don't conflate the two.

Next action

Email dev@guardedpaypro.com, since Slack no longer reaches them: ask straight whether they are still integrating, and offer a slot to put the embedded box on bestpeptidelab.com with you watching, once tomorrow's Apex switch is out of the way.

app_uHyTgAc1QXxFQKBW (coreresearchpeptides.com) was under review from 1 Sep. As of the 15 Sep read, channels appear at approval: Synergy, Vyal and Halo Labs USA each had one while still only approved. His current status is not in any readable source today, DB is down again. REV-214 (verify callback, activate, then send portal credentials) was touched again in today's Linear pull, still [Todo] p1.

New today, and a caution for this exact pattern: REV-258 "Sache's stores: Vyal Labs and Halo Labs USA are still inactive with zero sessions" ([Todo] p2 @tim, filed 16 Sep, still open today). Two merchants approved 11-13 days ago and still idle is precisely the shape that produced Apex's missed payout.

Next action

onboarding-check.sh app_uHyTgAc1QXxFQKBW once the DB is reachable. If he is live, confirm banking_approved before his first balance matures; if only approved, set him live with banking verified first (REV-144 now gates this by default).

#kiyora-peptide-llc, 13 Sep 15:30Z, Andrew: "We confirm receipt of Kiyora Peptide, LLC's notice of termination dated September 13, 2026... As Kiyora did not process any transactions through the Revion platform, there are no processed transactions, settlements, chargebacks, refunds, transaction-related losses, or termination reserve to reconcile." 15 Sep DB read: mrc_zinhzQp6eyBC status=active, 0 sessions. Why a working merchant left without trying a single sale is in no source, and the DB is down again today to check whether the row changed.

Next action

Close the account (keys off), send the effective date Andrew promised, and ask one question: what stopped Kiyora switching Revion on. The same reason may be sitting with Best Peptide and RHP.

Whether the ticket is resolved is still unverified, today's read has no billing-inquiry rows either. As of the 15 Sep read: the 14 Sep run listed Narboto inc at $0.09 to a test bank, Andrew refused to send it, Aadil asked Nur to remove all test accounts from payouts, and Nur agreed.

Next action

revioncaps.com/admin/billing-inquiries, Resolve, note "QA daily test, no action". Locally: source ~/RevionCaps/creds.sh && python3 ~/RevionCaps/linear_cleanup_rev60.py (idempotent; it also comments on REV-170).

#halo-peptides, 24 Aug 14:36Z: "done and live. Every new order now gets a private order note 'Revion payment link: <url>' plus an order meta field _revion_checkout_url that Sufyan can read programmatically... Already active on your store (plugin 1.2.27)." REV-127 is still [In Progress] p2 @tim in today's Linear pull, untouched since 2 Sep.

New today: Nur shipped a substantial payment-links rework (PR #484, guarded catalogue prices, a durable-email fix, a shared cooldown mailbox for plus-tagged recipients). It does not touch REV-127 directly, but it is more activity in the same payment-links area while this specific ticket sits untouched.

Next action

Close REV-127 with the 24 Aug message as proof, or write on it what is left. A shipped ticket left In Progress makes the open list lie.

REV-252 "Backend reviewer: hire, or interim AI review on every PR" ([Todo] p3 @tim) is unchanged in today's Linear pull. Today's git alone carries 10 merged PRs (#472 through #484) plus 17 direct commits, one engineer on all of them, into a codebase now handling live payouts and a live checkout incident (Synergy, REV-254) on the same day.

Next action

Pick a direction, hire or an AI-review gate on every PR, and file which one under REV-252.

As of the 15 Sep read, #ach-payouts-production: Andrew 16:19Z, "when do you show payouts starting for apex peptide supply they said they had transactions sept 4-7?"; 16:22Z, "peptide 911 wants to know there status as well". Nur, TG 17:48Z: "Two merchants transacted with matured, payable balances but no payout went out because their banking verification step had not been run. Both are now verified." Apex Peptide Supply $2,267.28 (19 orders settled 3-10 Sep); Peptide911 $262.79. The payout message went up at 18:06Z ("Pay on or after: Sep 16"), Tim gave the green light at 18:29Z. None of this has been re-checked in two days, Slack is down again.

New today, and it directly undercuts the assumption that this is settled: REV-256 "Close out sent payouts: bank reference and sent date, not stuck in processing" ([Todo] p1 @nur), filed today. If the platform has a class of payouts that show as sent but never get a bank reference, Apex and Peptide911's catch-up run needs re-checking specifically against that, not just assumed clean because the green light was given two days ago.

Next action

Ask Nur directly: does REV-256 include the Apex/Peptide911 catch-up run? Then confirm with Andrew that both ACH transfers have an actual bank reference recorded, not just a "sent" status. Call Matthew Jensen (Apex) and James Votraw (Peptide911) once that is confirmed, not before.

The wall was measured on 2 Sep: $380 and $361 non-Visa declines in five days. As of the 15 Sep read, 10 production attempts across merchants, 5 authorized, and card declines returned "Your card was declined. Please use another Visa card or contact your card issuer." No brand-enablement ticket is in today's Linear pull.

New today: PR #480 "Align REV-233 embedded Visa checkout with approved box spec" merged, part of a ten-PR batch of fixes to the same box (see Tim's and Nur's sections). Whether the "approved box spec" itself changed to allow other brands, or just hardened the Visa-only flow, is not stated in any commit message. REV-255 (turn the payment chooser popup off for every live merchant) also shipped today's Linear pull as new, separate from the brand question.

Next action

With Andrew/Ignacio: what enables Mastercard, Amex and Discover on the NMI MID, and by when. Ask Nur directly whether today's spec-conformance pass touched brand support at all before assuming it did not.

As of the 15 Sep read: "Synergy Research, LLC" (synergy-labs.uswholesalepeptides.com, mrc_LLEYN7Q4l9fC) applied 10 Sep, approved, live since 15 Sep; "Vyal Labs LLC" (vyallabs.com, mrc_PA2TX_ACHQq5) approved 12 Sep; "Halo Labs USA LLC" (halolabsusa.com, mrc_f4LFsn8VaAaJ, contact Alice Rewoldt) approved 14 Sep. Halo Labs USA is a different business from Halo Peptides, keep the two apart in payouts and in REV-231.

New today, and this is now the most urgent thing on the board: REV-245 ("watch Synergy's first real order") has been closed as a Duplicate of REV-254 "Synergy Labs live: buyers see 'Card processing is temporarily unavailable'" ([Todo] p1 @nur, filed today). A merchant that went live three days ago is actively failing to take real buyers' cards. Separately, REV-258 "Sache's stores: Vyal Labs and Halo Labs USA are still inactive with zero sessions" ([Todo] p2 @tim) is unchanged since 16 Sep, so the other two approved merchants remain idle.

Next action

Push Nur for Synergy's root cause today, not this week, this is a live merchant actively losing sales. Separately, for Vyal and Halo Labs USA: banking verified, fee confirmed, set live, welcome posted, first test order watched, before either becomes the next stalled onboarding.

As of the 15 Sep read: Jarrod's copy ends at 8.4 (31 Aug 23:48Z). Tim promised on 1 Sep to discuss it with you that day; the channel had been silent since. Tim's 31 Aug message told him "Revion is registered in Florida today" and tagged you to review Washington registration timing. None of that has been re-checked in two days, Slack is down again.

REV-196 (the Florida suppression code, merged 15 Sep) is unchanged in today's Linear pull, still [In Progress]. That is the tax-collection half of Tim's question answered from the code side; the registration fact and the executed agreement are still only yours to give him.

Next action

Send Tim the executed RHP agreement and one line on Florida, registered or not, plus your call on an addendum or accepting Jarrod's position.

As of the 15 Sep read: Kiyora terminated (Andrew acknowledged 13 Sep 15:30Z, "did not process any transactions"); Best Peptide's team removed themselves from #best-peptide-lab 11 Sep 09:44Z, 0 sessions since 13 Sep; Biopep had four checkouts since 13 Sep and none reached a card; RHP had 0 sessions since 13 Sep. None of it has been re-checked in two days, Slack is down again, so treat all four as still open until proven otherwise.

New today: add Synergy to this list, but for a different reason, they are live and actively failing (REV-254), not silent. That one needs an engineering answer before a phone call helps.

Next action

By phone this week: Best Peptide (are they still in?), Biopep's Casey (with Tim), Jarrod (after the Florida answer), one call to Kiyora to ask why they left. Synergy goes to Nur first, then a call once there is something concrete to tell them.

Open since 28 Aug; Nur asked again on the morning of 29 Aug. Whether his payment went out is still unverified, TG is down today so the thread cannot be checked.

Today alone, from git: 10 more PRs merged (#472 through #484, the embedded-box spec-conformance pass, a cluster of postmerge P1 fixes, three REV-146 follow-ups plus a plugin repackage, IPv4/PAN log-scrubbing, an alert-secrets allowlist, and the payment-links rework), plus 17 direct commits. Busiest single day in the read so far, all one engineer.

Next action

Send it, confirm in the thread.

As of the 15 Sep read, VAPI_PRIVATE_KEY etc. were set on revioncaps-prod; calls were held off only by VAPI_OUTBOUND_ENABLED=false, and vapi-outbound.ts had no calling-window, DNC or consent gates. No VAPI ticket appears in today's Linear pull either. The buyer base behind it keeps growing with more merchants live.

Next action

Either unset the prod keys or commission the TCPA gates, and file whichever it is.

As of the 15 Sep read: Hudaifa rejoined #halo-peptides on 31 Aug, no messages from Halo since; Andrew confirmed the 14 Sep run went out ("others got paid"); the 27 Aug $1,139.16 had no visible bank reference. REV-163 is still [Todo] p2 @aadil in today's Linear pull, untouched since 2 Sep.

Next action

Once Andrew confirms the references (and once REV-256's stuck-in-processing question is answered generally), a short note or call to Hudaifa on what was paid and when; then close REV-163.

REV-164 sits below today's top-50 Linear window too (last seen updated 27 Aug), so its state is unverified rather than closed. TG is down today so whether the message was deleted cannot be checked.

REV-247 (rotate the separate "GuardedPay" leaked credential) is also still open, unchanged today. Two live credential leaks in the same channel in three weeks is worth a word to the team about not pasting secrets there at all.

Next action

Rotate it, delete the message, close the ticket.

Decided in TG on 31 Aug: DocuSeal replaces DocuSign seats, filed as REV-187 ([Backlog] p3 @unassigned), unchanged in today's Linear pull. REV-87 (move e-sign to DocuSign) is also still open, unchanged. REV-144 (banking verified as a gate to LIVE) shipped 15 Sep, closing the question by default before REV-187 or REV-87 ever got an answer.

Next action

Say whether DocuSign-by-default is fine to keep, or whether REV-187 still needs doing properly. Then chase Planet, Fit Aminos and Sports Tech yourself.

Variants live in the "Revion Home Variants" artifact (REV-101, [In Progress] @tim, unchanged today). No letter in any readable source.

Next action

Reply with a letter in Core Engineering, or say the redesign is parked so REV-174 and REV-101 can close.

REV-254 "Synergy Labs live: buyers see 'Card processing is temporarily unavailable'" ([Todo] p1 @nur), filed today. Synergy Research, LLC (synergy-labs.uswholesalepeptides.com, mrc_LLEYN7Q4l9fC) applied 10 Sep and went live 15 Sep; REV-245, which asked you to watch its first real order end to end, is now marked [Duplicate] of this ticket as of today. REV-257 "QA: reproduce the Synergy checkout failure and capture the exact error we return" ([Todo] p1 @narbotokerimov) is filed alongside it. No detail on whether this is a gateway timeout, a config error, or something specific to Synergy's catalogue is in any readable source today; Slack and the DB are both down, so there is no session-level evidence to work from yet, only the ticket title.

This lands the same day as a ten-PR fix batch to the embedded Visa box (see below); whether Synergy runs through that same box or the older redirect flow is not stated anywhere today, worth ruling in or out first since a shared root cause would change how urgently the Friday Apex switch needs re-examining.

Next action

Get the actual error from logs today, not just the buyer-facing message. Confirm whether Synergy's checkout path overlaps with the embedded box's postmerge fixes. Tell Aadil the moment you have a cause, this is a live merchant losing real sales every hour it is broken.

As of the 15 Sep read: your TG 17:48Z, matured balances, "no payout went out because their banking verification step had not been run"; REV-144 shipped 15 Sep to gate future Set-live on banking verification. That closed the cause for NEW merchants; it does not by itself prove every already-live merchant's balance is actually paid out.

New today: REV-256 "Close out sent payouts: bank reference and sent date, not stuck in processing" ([Todo] p1 @nur), filed today. This is a different failure mode from the one REV-144 fixed: not "no payout was triggered" but "a payout was triggered and is not completing cleanly." It directly touches Apex and Peptide911's catch-up run, Halo's 14 Sep $358.16, and Zen's overlapping-window runs, all still open questions on this board.

Next action

Post one list in #ach-payouts-production: every payout marked sent in the last 30 days, with or without a bank reference. Anything without one is not actually confirmed paid regardless of status. Prioritise Apex and Peptide911 given Aadil is about to call both merchants.

REV-233 (build the box, live paid order Wed, Apex switched by Fri 18 Sep) no longer appears in today's Linear open-issues pull. Today's git: PR #480 "Align REV-233 embedded Visa checkout with approved box spec", PR #481 (recovery failure now keeps the box locked as review instead of silently proceeding, plus a fix keeping the recovery-catch comment inside the lifecycle source-assertion window), PR #482/#483 (a box that expired silently instead of showing the notice, plus IPv4 addresses staying readable through the scrubber), a standalone fix recovering embedded payment retries and restoring the iframe startup watchdog, a checkout fix protecting the confirmation URL and applying a renewed expiry, and PR #477 off a codex-assisted branch fixing the WooCommerce embedding configuration. REV-239 (Apple Pay in the box) is newly filed today too.

Read together, this looks like a real batch of P1 fixes following Narboto's M1 QA pass, not routine polish. Whether M2 has run against tonight's build, and whether REV-254 (Synergy's card-processing failure, above) shares any of these code paths, are both open questions.

Next action

Give Narboto and Tim a clear list of what changed since M1 so M2 tests the right things. Rule out or confirm any overlap with REV-254 before tomorrow's Apex switch goes ahead on schedule.

REV-231 ("Check: Halo still shows what they sell with product names hidden; confirm Biopep's BAC Water refusals") no longer appears in today's Linear pull; it may be closed, or it may simply have aged out of the top-50 recency window given how much else moved today. Neither is confirmed. Biopep (mrc_roNy1mlK9Ij5) had four expired sessions and zero payment intents as of the 15 Sep read, none of it re-checked since, the DB is down again.

REV-232 "Test: product-name alias on every screen, restricted items still refused with it on" ([Todo] p1 @narbotokerimov) is unchanged in today's Linear pull, still open, still not reconciled with REV-241's "allow prohibited products by default" change from 15 Sep.

Next action

Say plainly whether REV-231 closed and what it concluded. Until REV-232 is reconciled, do not treat "restricted items are refused" as true for any merchant.

REV-244 "Seven Sigma and Bioscience: Cloudflare blocks our webhook, callbacks never arrive" ([Todo] p2 @nur) is unchanged in today's Linear pull. Neither merchant's order state can be trusted while their callbacks never land, the same mechanism REV-226 already found cancelling paid Apex orders.

Next action

Find what Cloudflare is blocking and get an allowlist or bypass in today, before tomorrow's Seven Sigma payout deadline arrives with unverified order state behind it.

REV-247 "Delete the credentials and bank details posted in Core Engineering, rotate the GuardedPay password" ([Todo] p1 @nur) is unchanged in today's Linear pull. No detail on how long it was exposed or who posted it is in any readable source; TG is down today so the message itself cannot be checked.

For clarity: today's PR #484 branch "nur/payment-links-guardedpay" reworks merchant payment links (guarded catalogue prices, durable email, a shared cooldown mailbox for plus-tagged recipients). That is a different, unrelated use of the word "guarded"; it does not touch this credential-rotation ticket.

Next action

Delete the message, rotate the password, and check whether anything was accessed with it while it was live.

REV-196 "Turn OFF Florida sales-tax collection until registered" ([In Progress] p1 @nur) is unchanged in today's Linear pull. PR #465 (merged 15 Sep) covers the "$0 FL quotes" half; the refund and TaxJar-purge halves are still not named in any commit today either.

Next action

Confirm a fresh Florida quote comes back $0. Then either refund what was already collected and purge the TaxJar test transactions, or get the registration fact from Aadil first if the suppression turns out to be wrong.

REV-214 ("verify callback, activate, then send portal credentials") shows upd 2026-09-17 in today's Linear pull, meaning something on it changed today, but what is not stated; it is still [Todo] p1. REV-144 ("banking verified + agreement signed as gates to LIVE") shipped 15 Sep, closing the specific gap today's missed payouts came from.

Next action

Find out what changed on REV-214 today and whether it is now actually done. Add the standing Slack alert for any live merchant without banking_approved, since REV-144 gates new merchants but does not retroactively flag old ones.

REV-226 ("Webhook timeouts cancel PAID Woo orders") had two merges through 15 Sep: #455 (ack-then-process) and #457 (bound delivery lifetime within outbox lease). It does not appear in today's Linear pull either way. Today's git adds more to the same theme: "recover embedded payment retries and restore iframe startup watchdog" and "recovery failure keeps the box locked as review" (PR #481), both about what happens when a payment attempt fails partway through, the same class of bug REV-226 first found. The reconcile sweep for orders already cancelled by the original bug is still not named in any commit.

Next action

Confirm #455 and #457 are promoted to production, then run the one-off reconcile of Apex orders Revion shows AUTHORIZED and Woo shows cancelled. Give Aadil the result before his call to Apex.

REV-189 remains missing from the open list, and no commit today names fee rates. At the last code read: zod locks feeRate to 12|14 in three places, sandbox-provisioning-client.ts:66 refuses other values, and settlement.ts guards fee_rate IN (12, 14) twice. REV-246 (Pura's NMI batch cutoff time, blocked item from REV-236) is unchanged in today's Linear pull, still open.

Next action

Check Pura's merchant row: if it went live at 12 or 14 against an 8.5 contract, tell Aadil before its first payout; if 8.5 is stored, prove it passes both settlement guards.

emails.ts:368 carried the "processing is disabled" line at the 2 Sep read. New today: REV-169 "Fix the merchant credentials email copy" flipped from [Backlog] to [Duplicate] in today's Linear pull. No commit today touches emails.ts, and no readable source names which ticket it is a duplicate of. REV-214 (onboarding activation sequence, touched today, see above) is the most likely candidate given it covers the same send path.

Next action

Find the canonical ticket REV-169 now points to and confirm the email copy itself actually changed, a status flip alone is not proof the lie is fixed.

As of the 15 Sep read, Biopep now reads https://biopepusa.com. Application websites: Research Chemical LLC https://www.researchchemical.com; Veri 7 labs https://veri7labs.com followed by a zero-width U+2060 character. Whether either row carries the application value is unverified, the DB is down again today.

Next action

Read both merchant rows once the DB is back and fix by single-field update if needed; then normalise domains at registration so the next merchant cannot arrive broken.

support_admin_alert emails to support@send.revioncaps.com showed [failed] repeatedly from about 28 Aug. REV-146 was [Todo] p2 as of the 16 Sep read.

New today: three commits reference REV-146 directly ("test follow-up2", "test follow-up3", "align plugin release hash, lint const, after REV-146 packaging"), plus a separate "Repackage unreleased 1.3.1 plugin after upstream error log fixes" and two lint/regression fixes in the error-log test. REV-146 no longer appears in today's Linear open-issues pull. That is a reasonable circumstantial case for closure, but the bundle only pulls open issues, so closure itself is not directly confirmed by anything readable today.

Next action

Confirm REV-146's actual Linear status, then check a real support_admin_alert delivers before calling the sending-domain question closed.

As of the 15 Sep read: 10 attempts, 5 authorized, 3 card_declined, 1 insufficient funds, 1 in review; Biopep 4 sessions and 0 intents since 13 Sep. Still open in today's Linear pull: REV-165 funnel/decline report (p2), REV-142 silent-merchant alert (p2), REV-145 plugins page (p2), REV-173 telemetry null (p4), REV-104 operator payment links (p2).

New today: REV-254 (Synergy's live buyers seeing "Card processing is temporarily unavailable") is exactly the kind of thing REV-165's daily report would surface automatically instead of needing a ticket filed after buyers already hit it.

Next action

REV-165 first: a daily per-merchant line of sessions, intents, authorizations and decline reasons. It would also settle the REV-231/REV-241/REV-232 question with real decline reasons instead of guesswork.

As of the 15 Sep read: opt-in NMI reversal reconciliation "and atomic accounting" (#443), linked reversals held before reporting to the ACH generation fence (#445), external refund parent and original payment verified (#448), an exception review queue with opt-in Slack alerts (#452). At the last code read settlement.ts deducted refunded_cents but never recalculated fee_cents down, and MFSA 16.4 argues it should.

Next action

One line: does #443's accounting reduce the fee share on a partial refund? If not, add it before reconciliation is switched on for real merchants.

slack_provisioning_status/_error exist on the merchant row but nothing shows them. Departures are just as invisible: Halo's consultancy left #halo-peptides on 23 Aug, Best Peptide's team left #best-peptide-lab on 11 Sep.

Next action

Show invite state and external-member count per merchant in admin, and post to Slack when a merchant's last external member leaves.

Asked in Core Engineering 31 Aug 13:48Z: "Would be sick if we had the customers number ready for anyone/me/andrew/pat to call them right away too." The buyer's phone is collected at checkout; the billing-inquiry queue and its alert email do not surface it. No such ticket is in today's Linear pull either.

Next action

Show the buyer's phone on the billing-inquiry admin view and in the alert email; file it in Linear with the LLM pre-check block.

REV-174 does not appear in today's Linear pull (was [Todo] p4 @nur as of 16 Sep). REV-101 (the variants, Tim) is unchanged, still [In Progress]. No letter in any readable source.

Next action

Nothing before Aadil's letter; if p4 means parked, say so on REV-174 so REV-101 can close too.

REV-257 "QA: reproduce the Synergy checkout failure and capture the exact error we return" ([Todo] p1 @narbotokerimov), filed today, paired with Nur's REV-254. Synergy Research, LLC went live 15 Sep; REV-245 (watch their first real order) has been closed as a duplicate of REV-254 now that there is an actual failure to chase instead of just a first order to watch.

Next action

Run a real checkout on Synergy's store today, capture the exact response body and status code, and get it to Nur before end of day, this is blocking a live merchant's sales right now.

REV-234 "QA: embedded Visa box on WooCommerce (REV-233) - plan now, run M1 Wed + M2 Thu with Tim" ([Todo] p1) is unchanged in today's Linear pull. REV-233 itself has dropped off the open list; today's git shows a large batch of postmerge P1 fixes on the same box (see Nur's section), consistent with M1 having found real defects that got fixed today.

New today, and worth checking before you run anything further: REV-249's 10 manual QA cases were written against "plugin 1.2.34," but today's git includes "Repackage unreleased 1.3.1 plugin after upstream error log fixes" and a commit noting "backend release metadata follows plugin 1.3.3." If the live plugin has moved past 1.2.34, REV-249's cases may now be testing a build that no longer exists.

Next action

Confirm which plugin version is actually live before running REV-249's cases. Run M2 with Tim today if it has not happened yet, tomorrow is the Apex switch.

As of the 15 Sep read: Tim estimated about 9 of 20 real buyers reached the page and never submitted a card, and replay review of those sessions was the next step; no result was visible in any source. Targets: Biopep cs_EZO-PKMQnMyecR0VfwTx $3,277.87, cs_RVasVZH_AAxR1qMea1PK $109.00, cs_ZK_B_CCbydE0g6S43ljT and cs_xzPaO8-h-7F5c3TwHr1C (both $69.99). None of it has been re-checked in two days, the DB is down again.

Next action

Watch the four Biopep replays once Synergy's live incident (REV-257) is handled first, that one is actively losing sales today. One line each on Biopep to Nur for REV-231 and to Tim.

REV-232 "Test: product-name alias on every screen, restricted items still refused with it on" ([Todo] p1) is unchanged in today's Linear pull. Halo runs with names hidden and was converting as of the 15 Sep read. REV-231, Nur's paired ticket on the same question, no longer appears in today's Linear pull either, closed or just aged out is not stated anywhere.

Next action

Before testing anything: ask Nur whether REV-241 was meant to replace this ticket's assumption, and what happened to REV-231. If refusal is still the rule for some merchants, get the per-merchant PROHIBITED_PRODUCTS_MODE values first.

REV-235 [Todo] p1 @narbotokerimov is unchanged in today's Linear pull. REV-104 (operators create payment links) remains open, and #446 shows authorized payments in the merchant dashboard before settlement.

New today: PR #484 reworked merchant payment links (guarded catalogue prices, a durable-email fix, a shared cooldown mailbox for plus-tagged recipients) plus a separate fix guarding link creation and refreshing the no-popup plugin. None of this has been tested end to end by anyone yet as far as any readable source shows.

Next action

Run it on your own test merchant, not Halo: Send Link, pay with a Visa, check the dashboard shows it, mark it fulfilled, refund. Specifically test a plus-tagged recipient address given today's cooldown-mailbox fix.

As of the 15 Sep read: 14 Sep payout run, Narboto inc $0.09 to a test bank account, Andrew refused to send it, Aadil asked for test accounts to be removed from payouts, Nur promised the next run leaves them out. Halo orders RC-2026-1000228, -232, -233, -235, -236 and -242 (all $0.50) were unrefunded at the 2 Sep read; whether a refund landed since is unverified, the DB is down again.

Next action

Refund the six from admin, confirm with Nur that test merchants are flagged out of payout runs (and specifically out of whatever REV-256 is finding stuck), and move $-tests to your own store.

Unchanged in today's Linear pull: REV-93 scanned PDFs ([Todo] p2), REV-92 duplicate applications ([In Review]), REV-90 mobile wizard defects ([In Review]), REV-91 guest upload-session defects ([Todo]). REV-240 "Automate deploy regression checks inside the existing Checkout E2E gate" ([Todo] p2 @narbotokerimov) is also in today's pull, an approved CI plan not previously tracked here.

Next action

Finish the REV-90 and REV-92 reviews this week; for REV-93, reproduce with a phone-scanned PDF and post the CDR rejection code for REV-186.

REV-216's title was updated today to "Build real WooCommerce and custom QA stores and test adversarial onboarding daily" ([Todo] p2), an expansion from its prior scope. Test traffic keeps landing in production money: the $0.09 Narboto inc payout, the six $0.50 Halo orders, and now a QA case set written against a plugin version that has since moved.

Next action

One Woo store on your own account, so REV-234, REV-232 and REV-235 run there instead of on a merchant, and so plugin-version QA cases stay pinned to what you control.

Open: REV-215 (11 Sep, p1), REV-209 (7 Sep), REV-207 (6 Sep), REV-206 (5 Sep), REV-202 (3 Sep), REV-181 (30 Aug), REV-180 (29 Aug). REV-98 (validate merchant dashboard release 5565719) has been [In Review] since 2 Sep. REV-253 (yesterday's daily) no longer appears in today's pull, closed or aged out is not stated. REV-260 ("QA daily - 2026-09-17", [Backlog] p0) is today's instance, filed the same way as the last several.

Next action

Close or mark-skipped every daily older than REV-260, one line each, and keep closing each daily the same day.

Today's 13:07Z launchd collection came back blind again: Slack (channel list and all 8 channels), the prod DB (all six tracked merchants, plus the same JSON decode error on the raw read) and TG Core Engineering all read SECTION UNAVAILABLE, and nobody re-collected by hand, so this board carries the 15 Sep 18:32Z read forward for a second straight day wherever those three sources are the only evidence. This is the same PATH gap flagged on 2, 7, 8, 9, 10, 12, 14 and 16 Sep, eight prior occurrences, with the fix named explicitly yesterday: export PATH at the top of collect.sh and generate.sh. It was not applied before today's run either. git and Linear, which do not depend on that PATH, answered clean both days, and today Linear and git carried real signal that this board would otherwise have missed entirely (REV-254's Synergy incident, REV-256's stuck payouts).

Next action

Export the PATH fix for real this time, in the actual committed script, not just named in a board again. Confirm tomorrow's run comes back with Slack, the DB and TG all answering before calling this done a third time.

As of the 15 Sep read, live merchants included Apex Peptide Supply mrc_Jj7KJ7lPbJSh, Bioscience Peptides mrc_gUkKa0d4TClA, Veri 7 labs mrc_7RFYJXz5hHPT, Epic Wholesalers mrc_i1ZcMuL8KlKJ, Research Chemical mrc_Vhs6nzY0_j-c, Peptide911 mrc_PCV1-S_xcogf, Viltrumite Lab mrc_4oOU2meLCons; none of the seven is in the collector's channel list, plus Seven Sigma and Pura named only in Linear.

New today: same gap, no fix applied. Synergy Labs (live since 15 Sep, now the subject of REV-254) is a further example, it is not clear the collector's merchant list even includes it given the DB read has been failing since before it went live.

Next action

Add the nine named merchants to MERCHANTS and their channels to CHANNELS in collect.sh (drop Kiyora once closed), then derive both lists from the DB so the next go-live is tracked automatically, once the PATH fix restores DB access at all.

Sandbox-to-production merges through 16 Sep: #373 through #465 (tracked across prior boards). Today's git adds 10 more merged PRs: #472 (delivery-skill-merge), #475 (alert-secrets-allowlist), #477 (codex/woo-embedding-config), #478 and #479 (REV-146 test follow-ups), #480 (REV-233 box-spec-conformance), #481 (postmerge-p1-fixes), #482 (scrubber-ipv4), #483 (box-silent-expiry-guard), #484 (payment-links-guardedpay). Whether any of them are actually running on revioncaps-prod is unverified; flyctl was unreachable today, the same PATH gap as the Slack/DB/TG collector (see the top Claude item).

Next action

Once the PATH fix lands, run flyctl releases per app plus the release tag for all ten of today's merges, then the Playwright checkout E2E gate on the live sandbox channel. Never place a payment on sandbox.revioncaps.com: prod keys.

REV-245, which assigned watching Synergy's first real order, is now [Duplicate] of REV-254 (buyers seeing "Card processing is temporarily unavailable"), so that piece of this task has changed character entirely, from a routine first-order watch to an active incident already owned by Nur and Narboto. Still open: the embedded box's next live paid order once tomorrow's fixes are confirmed, and Biopep's next attempt (none of four has reached a card as of the 15 Sep read). watch-merchant.sh could not be tested today, node and flyctl were both off PATH again.

Next action

Stay out of Nur's and Narboto's way on REV-254/REV-257 today. Once the PATH fix lands, watch the embedded box's next live order, confirm charge, receipt and Woo order state, and post the result on REV-234.

File one labelled Charge inquiry via the sandbox public support endpoint and confirm the alert email carries both admin links. (Claude's live POST was classifier-blocked, so it needs a human-run curl or Tim's go.) It pairs with Nur's failing support_admin_alert item, now possibly closed by REV-146, same send path either way.

Slack, the DB and TG all read SECTION UNAVAILABLE today, so there is no fresh merchant-channel signal to sweep; every item on this board sourced from those three still carries over from the 15 Sep 18:32Z read. What did move came from git and Linear: 10 PRs shipped, REV-254 (Synergy card-processing failure), REV-256 (payouts stuck in processing), REV-146 apparently closed, and REV-169/REV-245 flipped to Duplicate. Drafts go to the owner on this board; nothing is sent from here.