Payments

Six providers, a product catalogue, payment links, embeddable widgets and transactions.

Payments is how money reaches you: six payment providers, a product catalogue, shareable payment links, embeddable checkout widgets, and a transaction ledger.

Payments is available on every plan, and needs the manage_finance capability on your role.

In this guide

  • Getting to the page
  • Overview
  • Providers
  • Products
  • Links
  • Widgets
  • Transactions
  • Payments from calls
  • Troubleshooting

1. Getting to the page

Click Payments in the Finance section, at /client/payments. Six tabs: Overview · Providers · Products · Links · Widgets · Transactions.

Deep links work: ?tab=links&new=1 opens the Links tab with a new link ready.


2. Overview

Money taken in the period, by provider and by product; recent transactions; failed payments; and links that have been opened but not paid.


3. Providers

Six providers are supported:

ProviderNotes
StripeCards, wallets, subscriptions.
PayPalPayPal balance and cards.
SquareCards, in person and online.
RedsysSpanish bank card gateway.
MollieEuropean methods — iDEAL, Bancontact, SEPA.
RazorpayIndian methods — UPI, netbanking, cards.

Connect a provider with its own credentials. More than one can be live at once — you might take euro card payments through Mollie and everything else through Stripe.

Each provider tile shows what it needs and whether it is connected.


4. Products

Your sellable catalogue: name, description, price, currency, tax treatment and whether it recurs.

Products are what payment links, widgets and quotes are built from, so a price change lands everywhere at once.


A payment link is a URL you can send to anyone. It carries a product or an ad-hoc amount, your branding, and the providers you have connected.

  • Create — pick products or set an amount and a title.
  • Copy / open — the public checkout page.
  • Track — opened, paid, expired.
  • Expiry and single-use options.

Payment links can be issued automatically from a call by the Call Actions Payment link action, which waits for your approval before it reaches the caller.


6. Widgets

Embeddable checkout you drop into your own website with a snippet of HTML. The widget uses the same products, providers and branding as your links, so your site checkout and your emailed link cannot drift apart.

Embeddable payment widgets are on every plan.


7. Transactions

Every payment attempt: when, how much, which provider, which product, which customer, and the outcome. Refunds are recorded against the original.

On Command, settled transactions post through to the Finance ledger.


8. Payments from calls

Because payment links are a Call Action, a caller who agrees to pay on a call can be sent a link the moment it is approved — with the amount and the product taken from what was discussed.

The action needs a parameter before it can do anything: either link_id or slug of an existing link, or an amount, e.g. {"amount": 4500, "title": "Deposit"}.


9. Troubleshooting

SymptomCauseFix
Payments isn't in the navYour role lacks manage_financeTeam
A link shows no payment methodsNo provider connectedProviders tab
Payments succeed but don't reach FinanceFinance is Command-onlySee Plans & Subscriptions
The widget doesn't render on my siteThe snippet is incomplete, or the domain isn't allowedRe-copy the snippet
A Call Action payment link did nothingNo parameters set on the actionCall Actions
Wrong currency at checkoutThe product's currency, or the provider's supported currenciesCheck both

Was this page helpful?
Open Dashboard →