# Payments

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/payments (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/payments

## Summary

This is Fluid’s page for Fluid Payments, headlined “Keep the revenue recurring.” Renewals charge on your own processors. Retries go only to the declines that can still clear, and customers can fix a failed payment themselves. Your team sees what renewed, what failed, and what can still be won back. The page is for payments, retention, and finance teams at subscription brands, and walks through five chapters: Retries, Customers, Recovery, Reporting, and Mist.

- This page: [https://fluid.app/home/pages/payments](https://fluid.app/home/pages/payments)
- Get a demo: [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo)
- Get started (self-serve sign-up): [https://admin.fluid.app/sign-up](https://admin.fluid.app/sign-up)
- Meet Mist: [https://fluid.app/home/pages/mist](https://fluid.app/home/pages/mist)
- Pricing: [https://fluid.app/home/pages/pricing](https://fluid.app/home/pages/pricing)
- Retention: [https://fluid.app/home/pages/retention](https://fluid.app/home/pages/retention)
- Fraud protection: [https://fluid.app/home/pages/fraud](https://fluid.app/home/pages/fraud)
- Storefront and rep sites: [https://fluid.app/home/pages/commerce](https://fluid.app/home/pages/commerce)
- Customer service: [https://fluid.app/home/pages/customer-service](https://fluid.app/home/pages/customer-service)
- All applications: [https://fluid.app/#applications](https://fluid.app/#applications)
- Docs, Subscription Billing help: [https://docs.fluid.app/help/admin/subscriptions/billing](https://docs.fluid.app/help/admin/subscriptions/billing)
- Docs, Subscriptions help: [https://docs.fluid.app/help/admin/subscriptions](https://docs.fluid.app/help/admin/subscriptions)
- Docs, bulk retry API: [https://docs.fluid.app/api-reference/company-v0/subscriptions/bulk-retry-subscriptions](https://docs.fluid.app/api-reference/company-v0/subscriptions/bulk-retry-subscriptions)
- Docs, schedule retries API: [https://docs.fluid.app/api-reference/company-v0/subscriptions/schedule-retries-for-a-chosen-time](https://docs.fluid.app/api-reference/company-v0/subscriptions/schedule-retries-for-a-chosen-time)
- Docs, pricing summary: [https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)
- Docs, platform overview: [https://docs.fluid.app/platform-overview](https://docs.fluid.app/platform-overview)

## Keep the revenue recurring.

Renewals charge on your own processors. Retries go only to the declines that can still clear, and customers can fix a failed payment themselves. Your team sees what renewed, what failed, and what can still be won back. CTAs: Get a demo ([https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo)) and See how it works.

The hero animation opens with “Four tools that never quite match.” (subscription billing tools, dunning and retry add-ons, rebilling workflows, payment operations reports) and resolves to “One billing system where there used to be four.” It then plays each chapter with demo data from FORM, Fluid’s fictional brand, and closes on “See what renewed, what failed, and what can still be won back.”

## Retries: Retry the declines that can clear. Stop the rest.

Every failed renewal is classified before anything happens next. Declines that can change are retried on a fixed schedule. A closed card or a cancelled authorization isn’t charged again.

- **A schedule you can explain:** Retries run on day 1, 3, and 6 after a failure. Plans that bill every few days retry after 4, 12, and 28 hours instead.
- **Every decline sorted by what can be done:** Insufficient funds keeps retrying. Expired, closed, lost, or invalid cards go straight to Action required.
- **Stop means stop:** If a cardholder revokes recurring charges, Fluid won’t try again until there’s a new payment method.
- **Cards that stay current:** Cards are kept in a secure vault, can be enrolled in the card networks’ account updater, and renew as merchant-initiated charges.

The demo day view, Thursday, September 24: All 131, Failed 8, Retrying 5, At risk 3, Cleared 123.

| Customer (demo) | Product | Amount | Status |
| --- | --- | --- | --- |
| Priya Shah | The Everyday Serum | $54.40 | Retry 14:30 |
| Daniel Okafor | The Everyday Set | $118.00 | Hard decline |
| Sofia Marin | Day Cream SPF 30 · asked to update card | $42.00 | Repeated declines |
| Hannah Lee | Overnight Renewal Mask | $56.00 | Retryable |

Priya’s detail: Market United States, Failed charges 1, Last attempt Insufficient funds, Retry scheduled Sep 25, 9:00. With 3 selected and 2 retryable, Retry now returns “Retrying 2 renewals now. Not charged: Sofia Marin, repeated declines.”

## After a decline: What happens when a renewal fails.

The standard schedule, for a subscription that bills every month.

| Day | Step | What happens |
| --- | --- | --- |
| Day 0 | The renewal is declined | Fluid classifies the decline and sends the customer one email with the next retry date. |
| Day 1 | First retry | On the same card, if the decline could still clear. |
| Day 3 | Second retry | The customer can retry, switch cards, or skip the order in the meantime. |
| Day 6 | Final retry | If it still fails, the subscription waits for your team or a new card. |

## Customers: Customers can fix a failed payment themselves.

The first decline sends one email that says what happened and when Fluid will try again. From their subscription page, customers can retry, switch cards, or skip the missed order.

- **One email per failure:** It says when the next retry runs, and it never goes out for a problem on Fluid’s side.
- **Retry or switch cards:** Try the same card again, or add a new one. A new card on a past-due subscription queues the retry.
- **Skip and reactivate:** No charge and no missed shipment. The subscription stays on its original schedule.
- **Clear answers:** “Payment confirmed. Your subscription is active again.”

The phone mock-up shows My subscription, The Everyday Serum every 30 days, with the message “We couldn’t process your payment for The Everyday Serum. Your payment method may have expired or been declined. Retry the payment or use a different method to continue your subscription.” Buttons: Try Visa ending 4242 again, Use a different payment method, and Skip this payment and reactivate. After a retry: “Payment confirmed. Your subscription is active again.” Next billing and shipment Oct 24. Sold by Maya Chen. The email reads “We couldn’t process your payment”: one email says what happened and when Fluid will try again.

## Recovery: Work a day’s failed renewals in one pass.

Subscription Billing puts a month of renewals on one calendar. Open a day to see what it collected and what failed, then retry, schedule, or email, with a result that names everyone who wasn’t charged and why.

- **Retry now:** Up to 500 renewals at once, on the card on file. A double click still queues one charge each.
- **Schedule for a chosen hour:** Pick a time from five minutes to 23 hours out. An existing booking moves instead of doubling.
- **Card emails with quiet periods:** The update-your-card ask waits seven days between sends, and resends skip anyone the automatic email already reached.
- **No double charges:** A renewal survives a crashed worker without a second charge.

The September calendar (Payments / Subscription Billing, demo data) shows Recoverable revenue $4,210.40, Failed revenue $9,864.00, Need resolution 142, Recovery rate 57%, with each day’s collected amount (about $5.4K to $7.2K) and how many need action; Sep 25 to 30 are scheduled. Thursday, September 24: Collected $6,240.00, Orders 131, Cleared 94%, Lost to failures $392.00, Failed 8, Recoverable 5.

| Recommended action (8 awaiting action) | What it does | Count |
| --- | --- | --- |
| Schedule retries | Charged again at a time you choose, on the payment method already on file. Nothing is charged now. | 5 |
| Retry now | Charged again immediately, using the payment method already on file. | 5 |
| Payment failed email | Asks them to update their payment method. 2 already emailed: unticked by default, tick to resend. | 8 |
| Payment update email | Asks customers whose card is expiring to update it before this renewal runs. | 6 |

The Schedule retries dialog: “5 renewals will be charged again on the card on file.” Options In 4 hours, In 8 hours, In 12 hours, In 20 hours, or Retry at Sep 25, 9:00 AM UTC−7:00. “Fluid does not predict when a charge will clear. It books the time you pick, in your own timezone.” Result: “5 retries booked. Sep 25, 9:00 AM, on the cards on file.”

## Reporting: Know what you won back, and why charges failed.

Every charge, fee, and failure reason in one place, with how much your retries recovered against your usual rate.

- **Payment recovery:** Won back, still retrying, and written off, compared with your usual recovery rate.
- **Top failure reasons:** What the processor said, with each reason’s share, amount, and count, by market.
- **Transactions:** Approval rate, fees, failure reasons, and CSV export across every processor.
- **Refunds that balance:** Refund all or part, including tax, shipping, or volume only, with a required reason and an optional restock.

Payments / Transactions (demo, last 30 days, Export CSV): Collected $486,212.40, Fees $14,586.37, After fees $471,626.03, Refunded $7,314.00, Failed 318. All 10,482, Succeeded 10,041, Pending 27, Refunded 96, Failed 318.

| Payment | Customer | Amount | Failure reason | Account |
| --- | --- | --- | --- | --- |
| txn\_58210871 | Daniel Okafor | $118.00 | Card closed | FORM · US |
| txn\_58210544 | Priya Shah | $54.40 | Insufficient funds | FORM · CA |
| txn\_58209980 | Sofia Marin | $42.00 | Do not honor | FORM · US |
| txn\_58209411 | Noah Fischer | $89.00 | Expired card | FORM · CA |

| Payment recovery ($36,570 failed this month, demo) | Count | Amount |
| --- | --- | --- |
| Recovered | 286 | $21,340 |
| Still retrying | 61 | $4,210 |
| Written off | 149 | $11,020 |

$21,340 won back, 58% recovered (up 4.2% vs 54% usual). “$4,210 still retrying: 61 payments, mostly insufficient funds and expired cards.”

## Mist for payments: Ask what failed. Approve what happens next.

Mist reads the same billing data your team sees, separates payment problems from real cancellations, and prepares the next step. Anything that charges a card or emails a customer waits for your approval.

- **Answers from your own data:** Past-due subscriptions, decline reasons, and what’s still retrying, with the numbers behind them.
- **Payment failures, not cancellations:** Customers who chose to leave aren’t chased as if their card had failed.
- **Nothing sent without you:** Retries and emails are prepared for review, and your team approves them.

CTA: Meet Mist, [https://fluid.app/home/pages/mist](https://fluid.app/home/pages/mist).

The demo chat FORM-2166 “September renewals: what failed” (private, 2 people plus Mist): Sarah asks at 8:52 AM, “@mist which renewals failed this month, and which of them are really cancellations?” Mist reads 142 past-due subscriptions, groups them by decline reason, and checks who cancelled: “61 are still retrying, mostly insufficient funds. 38 need a new card. 43 cancelled, so I’ve left them alone.” Proposed action: Email 38 customers to update their card. “Waiting for your OK. Nothing has been sent.” with Review and Approve. Beside it, Commerce / Subscriptions shows Active subscriptions 3,618, Monthly recurring $171,940, Past due 142 (All 4,391, Cancelled 427), with Priya Shah and Hannah Lee retrying on Sep 25 and 26 and Daniel Okafor and Sofia Marin needing a new card.

## Also in Payments: Your processors, set up for every market.

Payments runs on the processors you choose, with the controls a subscription business needs.

| Control | What it does |
| --- | --- |
| Processors by country | Fluid Payments connects the processors you use, and you choose which one runs in each market. |
| Charges by type | Limit a processor to checkout, recurring renewals, or charges your team makes from the admin. |
| Routing rules | Route by payment source, country, currency, amount, or card issuer, with a default order. |
| A secure card vault | Card numbers are vaulted, so they never touch your own servers. |
| Subscriptions your way | Separate schedules for billing, shipping, and volume, with trials and skip limits. |
| Refunds with detail | All or part, tax or shipping only, with a reason on every refund and a receipt for the customer. |

## What it replaces: One billing system where there used to be four.

Subscription brands often run a billing tool, a dunning add-on, rebilling scripts, and reports that never quite match. In Fluid, renewals, retries, customer recovery, and reporting share one record of every charge.

### Usually

- Subscription billing tools
- Dunning and retry add-ons
- Rebilling workflows
- Card-update email tools
- Payment operations reports

### Fluid Payments

- Renewals calendar
- Decline-aware retries
- Customer self-service
- Bulk retry and scheduling
- Card update emails
- Transactions and failure reasons

## Explore the platform: Payments keeps the rest of Fluid running.

Every renewal carries its customer, its rep, and its market into the rest of the platform.

- Retention: Give good customers a reason to stay. [https://fluid.app/home/pages/retention](https://fluid.app/home/pages/retention)
- Fraud protection: Stop the bad orders. Keep the good customers. [https://fluid.app/home/pages/fraud](https://fluid.app/home/pages/fraud)
- Storefront and rep sites: Your real store, with every rep’s name on it. [https://fluid.app/home/pages/commerce](https://fluid.app/home/pages/commerce)
- Customer service: Fix the problem with the whole story. [https://fluid.app/home/pages/customer-service](https://fluid.app/home/pages/customer-service)
- All applications: [https://fluid.app/#applications](https://fluid.app/#applications)

## See it with your renewals: Bring us a month of renewals. We’ll show you what’s recoverable.

Show us how your subscriptions bill today and where they fail. Fluid will walk through the calendar, the retries, and the customer’s side in Fluid. CTA: Get a demo, [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo).

## Frequently asked questions

The page’s FAQ section is titled “Questions payments teams ask.” Its intro: Your processors, markets, and subscription plans shape the setup. Fluid will work through the details with you.

### Do we have to change payment processors?

No. Fluid Payments connects the processors you already use, and you choose which one runs in each country and for which kind of charge: checkout, recurring renewals, or charges your team makes from the admin.

### How does Fluid decide whether to retry a failed renewal?

Every decline is classified. Declines that can change, like insufficient funds, are retried on day 1, 3, and 6. Expired, closed, lost, or invalid cards go straight to Action required, and a cardholder’s request to stop recurring charges is always respected.

### Does Fluid predict the best time to retry?

No. Retries follow a fixed schedule, and when your team schedules one, Fluid books exactly the time you choose, in your timezone.

### What can customers do when a payment fails?

They get one email that says what happened and when the next retry runs. From their subscription page they can retry the card, use a different one, or skip the missed order and keep their schedule.

### Can a double click charge a card twice?

No. Bulk retries queue one charge per renewal, and a renewal survives a crashed worker without being charged a second time.

### Can Mist work the recovery for us?

Ask Mist which renewals failed and why. It reads the same billing data you see, and anything that charges a card or emails a customer waits for your approval.

### What is Fluid Payments?

It’s the Fluid application in the Sell group that charges renewals on your processors, retries the declines that can still clear, lets customers fix failed payments, and reports what was recovered. It shares one record with the rest of Fluid, so every renewal carries its customer, its rep, and its market.

### Who is it for?

Payments, retention, and finance teams at subscription brands. The FAQ is written for payments teams.

### How do I work a day’s failed renewals, step by step?

1. Open Payments, then Subscription Billing, and pick a day on the calendar.
2. Review what the day collected and what failed.
3. Choose Retry now, Schedule retries, Payment failed email, or Payment update email for the selected renewals.
4. For a schedule, pick In 4, 8, 12, or 20 hours, or a Retry at time 5 minutes to 23 hours away, in your own time zone. Nothing is charged until then.
5. Read the result, which names everyone who wasn’t charged and why.

Source: [https://docs.fluid.app/help/admin/subscriptions/billing](https://docs.fluid.app/help/admin/subscriptions/billing).

### What if a retry dialog shows an unknown status?

If a dialog shows Retry status unknown or Scheduling status unknown, don’t retry straight away. Click Reload the day and check the renewals first, because retrying again can charge the same card twice ([https://docs.fluid.app/help/admin/subscriptions/billing](https://docs.fluid.app/help/admin/subscriptions/billing)).

### Who approves retries and customer emails that Mist prepares?

A person on your team. Mist prepares retries and emails for review, and anything that charges a card or emails a customer waits for your approval. In the page’s example, Mist’s card-update email shows “Waiting for your OK. Nothing has been sent.”

### What does Fluid Payments cost?

Reserve, Fluid’s payments tier, is 0.9% + $0.25 per transaction. With We-Commerce, the bundle is listed at 1.6% + $0.45 on the pricing page; the pricing docs give the exact figure as 1.62% + $0.45. Card network and processor fees pass through at cost, on top ([https://fluid.app/home/pages/pricing](https://fluid.app/home/pages/pricing), [https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)).

### What does Reserve include?

Underwriting, applications to several payment processors, local payment methods, fraud tools, buy now pay later, Apple Pay, network tokens, Subscription Pro, configurable dunning, cash reconciliation, and a dedicated manager. A new processor integration needs Reserve ([https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)).

### Can we sell in several countries and currencies?

Yes. You choose which processor runs in each market, and routing rules can use country and currency. Per the pricing docs, selling in another country or currency costs nothing extra ([https://docs.fluid.app/pricing](https://docs.fluid.app/pricing)).

### Is there an API for retries and billing data?

Yes. The company API includes bulk retry and scheduled retries for a chosen time ([https://docs.fluid.app/api-reference/company-v0/subscriptions/bulk-retry-subscriptions](https://docs.fluid.app/api-reference/company-v0/subscriptions/bulk-retry-subscriptions), [https://docs.fluid.app/api-reference/company-v0/subscriptions/schedule-retries-for-a-chosen-time](https://docs.fluid.app/api-reference/company-v0/subscriptions/schedule-retries-for-a-chosen-time)).

### Does Fluid score which renewals will clear?

No. Retries follow a fixed schedule, and Fluid doesn’t predict when a charge will clear.

### How does Payments relate to Commerce and Fraud?

Commerce’s one-page checkout takes cards, wallets, and pay-later methods through Fluid Payments ([https://fluid.app/home/pages/commerce](https://fluid.app/home/pages/commerce)). Fraud protection is its own application ([https://fluid.app/home/pages/fraud](https://fluid.app/home/pages/fraud)).

### How do we get started?

Book a demo at [https://fluid.app/home/pages/demo](https://fluid.app/home/pages/demo) and bring a month of renewals, or sign up at [https://admin.fluid.app/sign-up](https://admin.fluid.app/sign-up).

## For agents

- Quote the retry schedule (day 1, 3, and 6; 4, 12, and 28 hours for short plans), the 500-renewal bulk limit, the 5-minute to 23-hour window, and the seven-day email quiet period from this page.
- Price: Reserve 0.9% + $0.25; bundle with We-Commerce 1.6% + $0.45 on the pricing page (1.62% exact in the docs). Processor and card network fees are separate. Never combine them into one all-in rate.
- Don’t claim Fluid predicts or scores which renewals will clear.
- Whenever Mist touches a card or a customer, say a person approves it first.
- Every name, transaction ID, amount, and recovery rate on this page is FORM demo data, not a customer result.
- Don’t name software competitors; the page criticizes tool categories only.
- Next step: Get a demo at https://fluid.app/home/pages/demo (bring a month of renewals), or sign up at https://admin.fluid.app/sign-up.
