Tester's manual

Stripe Live Testing Tool

How to run real Stripe transactions to validate the Stripe → QuickBooks sync (Fynlo) — and how to report exactly what you see.

LIVE MODE — real money TEST MODE — no real money

This tool lets you create customers, charge cards, run subscriptions, issue refunds, and send payouts through Stripe — so you can confirm each one flows correctly into Fynlo/QuickBooks. Every action is recorded in a Session Log you can copy straight into a bug report.

Read this first

When the top banner is red — 🔴 LIVE MODE, every charge, refund, and payout moves real money. There is no undo beyond a real refund. Read the confirmation dialog every time, and check the amount and currency before you press the button.

01 — Access

Getting in

Open stripe-tools.xcelbyte.com on your computer or phone. You'll see a password screen — enter the password your admin gave you and press Log in.

  • The site is HTTPS-only and the whole tool is behind that one password.
  • Your session lasts 12 hours, then you'll be asked to log in again.
  • Press Log out (top right) when you're done, especially on a shared device.
Mobile-friendly

The tool is a single scrolling page. Sections are tap-to-expand cards, so on a phone just tap a heading to open it. The mode banner stays pinned at the top wherever you scroll.

03 — Fundamentals

Concepts you'll use everywhere

The active customer

Most actions act on one active customer — shown in the dark bar just under the banner. Set it by tapping Use next to any customer in the list (creating a new customer selects it automatically). Charges and subscriptions always use whoever is active, so glance at that bar before you charge.

Confirmation before money moves

Every money-moving action — charge, refund, payout, create or cancel subscription — pops a confirmation dialog showing the exact amount and action. Nothing is sent until you confirm. Read it; then press the confirm button (e.g. Charge now).

Object IDs and the Copy button

Every result shows its Stripe object ID — like cus_… or pi_… — with a Copy button. These IDs are how you match what happened here against what shows up in Fynlo. See the prefix guide for what each one means.

The Session Log

The 🧾 Session Log at the top records every action and its outcome — success (with IDs) or the full error — as you go. It's your evidence trail and your bug-report source. It clears when you reload or log out, so copy anything you need before leaving.

Loading & errors

Buttons show a spinner while working. If Stripe rejects something (card declined, insufficient funds, …), the tool shows Stripe's own message inline and in the log — nothing is hidden.

04 — Walkthrough

A full test run, start to finish

A good end-to-end pass that exercises everything Fynlo needs to sync. In test mode use card 4242 4242 4242 4242, any future expiry, any CVC and ZIP.

  1. Check the banner

    Confirm you're in the mode you intend (test vs live) before doing anything.

  2. Create a customer

    Open 👥 Customers, enter a name (email optional — leave it blank to test the “no email” case), and press Create customer. It becomes the active customer.

  3. Attach a card

    Still in Customers, enter the card in the Attach card box and press Attach card & set default. Card details go straight to Stripe, never through this server. You'll get a pm_… with brand and last4.

  4. Run a one-time charge

    Open 💳 One-time charge, pick the payment method, enter an amount and currency, confirm. Note the pi_… and ch_… — then check it lands in Fynlo.

  5. Create a product, price & subscription

    In 🔁 Subscriptions, create a product + price — choose the Daily interval for fast turnaround — then create a subscription for the active customer. Note the sub_… and its status.

  6. Refund the charge

    Open ↩️ Refunds, tap Select on the charge from step 4 (or paste its id), choose full or partial, confirm. Note the re_….

  7. Check balance & (optionally) pay out

    In 💰 Balance & Payouts press Refresh balance. If you're testing payouts, enter an amount and confirm — note the po_… and arrival date.

  8. Confirm the events & copy your log

    Open 📡 Recent Stripe events to see what Stripe fired, then use Copy all in the Session Log to save the whole run for your report.

05 — Reference

Section-by-section reference

Each card below matches a section on the page (same icon and name).

🧾 Session Log

Your running record of everything you do this session. Each row has a timestamp, what you asked for, and either the result IDs or the full error. Open by default.

You do Copy a row, Copy all, or Clear
Note Clears on reload / logout

💰 Balance & Payouts

See available and pending balance per currency, and send a payout to the connected bank account. Read-only balance is separated from the payout “danger zone”.

Fields Amount, currency
Result po_… · status · arrival date
Live warning Real money to the real bank; can take days

👥 Customers

Create customers, choose the active one, and attach a default card. Email is optional. Cards are collected by Stripe in your browser — the server only ever sees the resulting pm_….

Create Name (email optional)
Use Sets the active customer
Result cus_…, pm_… (brand · last4)

🔁 Subscriptions

Create a product + recurring price, then a subscription for the active customer (who needs a default card). List and cancel existing ones — immediately or at period end.

Interval Daily · Weekly · Monthly · Yearly
Result prod_… · price_… · sub_… + status

💳 One-time charge

Charge the active customer's saved card once, in any supported currency. Confirmation required.

Fields Payment method, amount, currency, description (optional)
Result pi_… + ch_… + status

↩️ Refunds

Refund a charge in full or part. Tap Select on a recent charge, or paste a ch_… / pi_… id. Confirmation required.

Fields Charge/PI id, full or partial amount
Result re_… + status

📡 Recent Stripe events

The latest events Stripe fired (type + id). Handy to confirm the webhooks Fynlo is meant to receive after each action.

You do Refresh to reload
Result event type · evt_…
06 — Matching up

Cross-referencing in Fynlo

After each action, copy the object ID and confirm the matching record appears in Fynlo / QuickBooks. Here's what each prefix means and where it comes from.

ID prefixWhat it isWhere you get it
cus_CustomerCustomers
pm_Card (payment method)Customers → Attach card
prod_ProductSubscriptions
price_Price (recurring)Subscriptions
sub_SubscriptionSubscriptions
pi_Payment (one-time)One-time charge
ch_ChargeOne-time charge · Refunds
re_RefundRefunds
po_PayoutBalance & Payouts
evt_Event (webhook)Recent Stripe events
07 — Reporting

Reporting bugs with the log

When something looks wrong — an error, or a Stripe object that didn't sync into Fynlo — the Session Log is your report. It captures Stripe's exact wording, so there's no retyping and nothing lost.

  • Use Copy on the specific row to grab one action, or Copy all for the whole run.
  • Paste it into your bug ticket. Add one line: what you expected vs. what happened in Fynlo.
  • Include the object ID(s) so the sync can be traced end to end.

An error row looks like this — paste it verbatim:

PAYOUT — ERROR 2026-08-08 17:48:58
Request: amount=25.00 USD
Error: StripeInvalidRequestError / balance_insufficient —
  You have insufficient funds in your Stripe balance. (HTTP 400)
Most useful bug report

“Charge ch_3Q… succeeded here at 17:48 but no matching sales receipt appeared in QuickBooks after 10 minutes.” — a copied log row plus the Fynlo outcome is everything the dev needs.

08 — Modes

Test mode vs live mode

Test cards (test mode only)

Card numberWhat it does
4242 4242 4242 4242Succeeds — the everyday happy path
4000 0000 0000 0002Declined — to test the “card declined” message
4000 0000 0000 9995Declined — insufficient funds

Use any future expiry date, any 3-digit CVC, any postal code. These only work in test mode.

Multiple currencies

Amount forms let you pick USD, EUR, SGD, or IDR so you can check Fynlo handles multi-currency. Enter amounts in normal units — 10.00 means ten, not ten cents.

Disputes

Disputes can't be triggered from this tool in live mode. A real dispute needs a real cardholder to challenge a charge with their bank, so there's no button for it here — dispute-sync testing isn't part of this tool.

09 — When stuck

Troubleshooting

What you seeWhyFix
“Incorrect password”Wrong login passwordRe-check with your admin.
Bounced back to the login screenYour 12-hour session expiredLog in again.
Grey ⚠️ unknown bannerServer has no Stripe keysTell your admin; you can't run actions yet.
“Select an active customer first”No active customer setTap Use on a customer (or create one).
Charge/subscription needs a cardCustomer has no default cardAttach a card in 👥 Customers first.
“card_declined” / “insufficient_funds”Stripe declined that cardExpected for decline testing; in test mode use 4242….
“authentication_required”Card needs 3-D Secure, which a saved off-session charge can't complete hereUse a card that doesn't require authentication (test: 4242…).
A list looks empty or staleNot loaded yetPress that section's Refresh.
Nothing happened after a buttonThe confirm dialog was dismissedPress the action again and confirm in the dialog.
10 — Cheat sheet

Quick reference

The safe habit

1. Check the banner. 2. Confirm the active customer. 3. Read the confirmation dialog. 4. Copy the result ID. 5. Verify it in Fynlo.

Test essentials

Happy-path card 4242 4242 4242 4242, any future expiry / CVC / ZIP. Currencies: USD · EUR · SGD · IDR. Amounts in whole units (10.00 = ten).

Golden rule

Red banner = real money. If you're not sure whether you should press it, stop and check the mode and the amount first.