Payments

With Stripe connected, your workflows can create payment links and collect payments as part of a process — a booking deposit, an application fee, a quote acceptance, or a full order paid in stages. You describe what you want in plain language when you create the workflow, and assess.one builds the payment steps for you.

Note

Payments require a connected Stripe account. Until Stripe is connected, a workflow can still be created, but its payment steps won’t run — assess.one will remind you to connect Stripe first. A workflow that waits for payment pauses at that step instead of carrying on, so your customer is never told they missed a payment they were never asked for. Connect Stripe, then re-run the record.

Connect Stripe

1. Go to Settings → Integrations and choose Stripe.
2. Enter your Stripe secret key (a restricted key with permission for payment links is recommended). assess.one validates it immediately and stores it encrypted.
3. Set up the webhook (recommended). assess.one shows you a webhook URL to add in your Stripe dashboard, and you paste the signing secret back in. This is how assess.one hears about payments — it’s what marks a payment as Paid, and it’s required for any workflow that waits for payment.

Once payments start arriving, the integration card shows a green Receiving events badge, so you can see the connection is working end to end.

Test mode

Stripe has a built-in test mode — a sandbox with its own keys where no real money moves. Turn on Test mode and enter your Stripe test key to trial payment workflows safely; the card shows a Test mode badge and every payment runs in Stripe’s test environment. Switch to live payments by turning Test mode off and entering your live key.

Caution

The key must match the mode: a test key with Test mode on, a live key with it off. This prevents accidentally taking real payments while you think you’re testing.

Two ways to take a payment

There are two patterns, and the words you use in your prompt decide which one you get.

Send link & continue

The workflow sends the payment link and carries on (or finishes). The payment is still recorded when it’s paid, but the workflow doesn’t wait for it. Good for a simple “here’s your invoice” where nothing later depends on the payment.

“When a customer submits the form with the amount they owe, email them a Stripe payment link and finish — don’t wait for the payment.”

Send link & wait for payment

The workflow pauses until the customer pays (or a time limit passes), then continues down a paid or unpaid path. Good when the next step depends on the money arriving — schedule the job once the deposit lands, ship once it’s paid, chase or cancel if it isn’t.

“Send the customer a payment link for the amount I provide, wait until it’s paid, then mark the record complete and email a receipt. If it isn’t paid within 7 days, mark it lapsed.”

Tip

To make the workflow hold for payment, use phrases like “wait until it’s paid”, “once payment is received”, or “hold until they pay”. To fire and forget, say “send a link and finish” or “don’t wait for payment”.

How the amount is set

You can set the amount in whichever way suits the process:

• A fixed amount charged to everyone — e.g. “a $50 booking deposit” or “a fixed ¥1000 fee”.
• An amount entered on a form or by your team — e.g. “I’ll review the request and set the deposit amount”, so it can be different each time.
• A calculated amount — worked out from numbers on the form, e.g. “$50 per person”, “20% of the quote as a deposit” or “the remaining balance after the deposit”.
• Different amounts at different steps — e.g. a deposit now and the balance later, each its own payment step, in one workflow.

Note

Calculations use numbers the customer or your team enters — like the number of passengers or a quote amount — with simple arithmetic. If a number a calculation needs is missing, the payment step is skipped and flagged on the record rather than charging a wrong amount.

Currency

Your payment currency is set automatically based on your location — so it’s usually right without you doing anything.

You can change it to any supported currency just by saying so when you create or refine the workflow. Naming a currency in your prompt always overrides the automatic default:

“charge in USD” · “use Japanese Yen” · “prices are in AUD”

Supported currencies

Payments can be taken in any of these — just name it in your prompt:

Commonly used: Australian Dollar (AUD), US Dollar (USD), British Pound (GBP), Euro (EUR), Japanese Yen (JPY), Canadian Dollar (CAD), New Zealand Dollar (NZD), Singapore Dollar (SGD), Hong Kong Dollar (HKD), Indian Rupee (INR), Swiss Franc (CHF), Chinese Yuan (CNY).

Also supported: AED, BIF, BRL, CLP, CZK, DJF, DKK, GNF, HUF, IDR, ILS, KMF, KRW, MGA, MXN, MYR, NOK, PHP, PLN, PYG, RWF, SAR, SEK, THB, TRY, UGX, VND, VUV, XAF, XOF, XPF, ZAR.

If you name a currency that isn’t supported, the workflow simply uses your default currency instead.

What the customer sees, and what you see

• The customer gets an email with the amount and a “Pay now” button (with the plain link as a fallback), taking them to Stripe’s secure checkout. The link must be delivered to be useful — assess.one makes sure a workflow that creates a link also sends it.
• You see a payment card on the record showing the status — Pending, Paid, Expired, or Refunded — along with the amount, card brand and last-4, a link to the receipt, and the Stripe reference. Every payment is also listed in Settings → Logs → Payments.

Note

A record with more than one payment (e.g. a deposit and a balance) keeps all of them on the card as a history — earlier payments are never lost.

Reminders and expiry (for “wait for payment”)

When a workflow waits for payment, you can have it chase overdue payments and give up after a limit, just by saying so:

“…wait until it’s paid, remind them after 2 and 5 days if unpaid, and expire after 7 days.”

Reminders re-send the payment link automatically and stop as soon as the customer pays. If the time limit passes with no payment, the workflow takes its unpaid path (for example, marking the record lapsed and emailing the customer), and the payment link is switched off so it can’t be paid afterwards. Each link can only be paid once.

Refunds

To refund a payment, issue the refund in your Stripe dashboard — assess.one doesn’t send refunds itself. It’s then reflected automatically on the record: the payment card shows Refunded (or Partially refunded) and your revenue figures adjust. This works for both full and partial refunds, and needs no change to your workflow.

Next

• Email & SMS →
• What workflows can do →
• Integrations overview →