Browse the guide
Payment links, widget & checkout
Let customers pay you without an invoice.
Ways to get paid online without writing an invoice: a payment link you send by email or text, a hosted pay page and Pay widget you put on your website, Pay Now buttons, and checkout sessions your developer creates through the API. Every payment runs on your Merchant360 account and lands in your transactions.
Businesses that take deposits, one-off amounts, donations or subscriptions by message or on their own website, and the developers who build checkout for them.
- Your card processing is approved and active. The Pay widget cannot be turned on until it is.
- For texting a link, the customer's mobile number. For emailing it, their email address.
- For API keys and webhooks, sign in as the account owner. Only the owner can create or revoke them.
On this page
Send a payment link
Create a link, send it by email or text, and the customer pays on any device.
Payment links
A payment link is the fastest way to collect money without an invoice. You create a link, send it by email, text, or chat, and the customer pays on a secure hosted page on any device. Use it for a deposit, a quote the customer accepted by phone, a tip jar, or any one-off amount.
- 1Go to Accept Payments → Payment links and click New payment link. The New payment link form opens above your list.

New payment link opens the form above your links. - 2Optional: type a Link name (only you see it, for example March deposit).
- 3Enter the Amount. Leave it at $0.00 to let the customer choose the amount.
- 4Optional: add an Invoice #, change Expires in (days) (30 by default; leave it blank and the link never expires), and type a Description.
- 5Type the Customer name, Customer email and Customer phone. When the email is valid, the box Email the link to the customer appears with the address, already ticked. Untick it if you will send the link another way.
- 6If you use custom payment fields, choose what this link asks under Custom fields on this link: All fields, Choose fields or None.
- 7Click Create link. The green box Payment link created – share the URL below shows the address with a Copy button, and Emailed to with the address when the email went out.
- 8To send the link later or again, use its row: Copy URL, Email (check the address and click Send) or Text (type the mobile number and click Send). These show only while the link is PENDING.
- 9Watch the Status column: PENDING, PAID (with the card brand and last four), CANCELLED or EXPIRED. To stop a link, click Cancel on its row and confirm.

Each pending link has Copy URL, Email, Text and Cancel.
Each link is single-use: it locks after the first successful payment so it cannot be paid twice. Links can expire on a schedule (30 days by default), carry an invoice number and description for your records, and ask for any custom payment fields you enable.
A link is paid when its row shows Paid. The payment appears on Money → Transactions with the description and invoice number, the customer gets a receipt, and your payment alert goes out if Email me when a payment comes in is on. A bank payment on a link shows as paid once the debit is initiated and settles on the bank schedule.
If a customer says the link does not open, check the row: Expired links need a new link, Cancelled links were stopped on purpose, and a Paid link has already been used. If the customer's phone number is missing, Text is unavailable; add the number to the customer or paste the URL into your own message.
| On this screen | What it does |
|---|---|
| New payment link | Opens the form to create a link. |
| Amount * | The amount the customer pays. Leave it at $0.00 to let the customer choose the amount. |
| Invoice # (optional) | A reference that prints on the pay page, the receipt, and the transaction. |
| Expires in (days) | How long the link stays payable. Default 30; blank means never. |
| Description (optional) | What the payment is for, shown to the customer and saved on the transaction. |
| Link name (optional) | A private label for your board, for example March deposit. |
| Customer name / email / phone (optional) | Ties the link to a customer and enables Text to the phone number. |
| Custom fields on this link | All fields, Choose fields, or None: which of your custom payment fields the pay page asks. |
| Create link | Creates the link and shows the URL banner. |
| Copy URL | Puts the pay URL on your clipboard. |
| Text | Sends the link by SMS to the customer's mobile number. STOP-compliant like every Merchant360 text. |
| Cancel | Stops a link so it can no longer be paid. The row shows Cancelled. |
| Filter links | Narrows the board by amount, customer, invoice #, or status as you type. |
| Created, Amount, For, Customer, Status, Pay URL | The board columns. Status is Pending, Paid, Cancelled, or Expired. |
- Enter a valid amount.
- Type the amount as a number, or leave it at $0.00 for an open amount.
- Amount must be under $999,999.99.
- Split the amount across more than one link, or send an invoice.
- Enter a valid mobile number.
- Type all 10 digits of the customer's mobile number, then click Send.
- This number has opted out of texts (replied STOP).
- The customer stopped texts from your business. Send the link with Email, or Copy URL and send it yourself.
- The email was not sent
- Check the address. Then click Email on the link's row and send it again.
- Link is PAID – only a pending link can be texted.
- A paid, cancelled or expired link cannot be sent again. Create a new link.
- The row has no Copy URL, Email or Text
- Those show only for PENDING links. The link was paid, cancelled or expired.
Do this with the API:Payment links
Take payments on your website
Turn on the Pay widget, choose what it accepts, and add it or a Pay Now button to your site.
The pay widget & your hosted pay page
The pay widget gives you two things: a hosted pay page at your own link that you can share, print as a QR code, or preview, and an embeddable form you paste into your own website so customers pay without leaving your site. Both use the same settings.
- Your card processing is active. Until it is, the page shows Set up payment processing first.
- 1Go to Accept Payments → Pay widget. The first time, click Turn on the pay widget. The widget starts with one-time fixed-amount payments, a $1 floor and a $10,000 ceiling.

The first time: Turn on the pay widget. - 2The next screen reads Pay widget is live and shows Your API key once. Copy it if a developer will use it, then click I've saved it →.
- 3At the top of the page, check the status pill reads Live. Copy URL copies your pay page address; Preview opens it the way a customer sees it.
- 4Master switch: click the switch. ON means customers can pay through your hosted page and embed. OFF means they see Payments aren't available. The switch saves when you click it.

The status pill, your pay page address, and the Master switch. - 5Payment types: click the switch on each type you want ON. Each change saves on its own and shows Saved. A type that is ON (other than Fixed amount) shows its own Preview and Copy link.

Payment types: turn on the ones you want. - 6Amount range: type the Minimum and Maximum, then click Save. Save shows once you change a value.
- 7Branding: pick a Brand color and click Save. The logo is the one in Billing Settings → Business profile.
- 8Allowed return domains: list the domains, one per line, where the pay page may send a payer after paying, then click Save. Your website domain is always allowed.
- 9Receipts: optional From email (so receipts are branded as you) and BCC email (a copy of every receipt), then click Save.
- 10Embed snippet: pick the Payment type (and the Amount for Fixed amount), add a Description if you want, click Copy and paste the code into your website where the form should appear.
Go to Accept Payments → Pay widget. The first time, click Turn on the Pay widget; this needs card processing to be active. The widget starts with one-time fixed-amount payments, a $1 floor, and a $10,000 ceiling, all of which you can change.
You are done when the status pill reads Live and the Master switch is On. Copy URL gives you the public pay page address, and Preview shows exactly what a customer sees. Every payment through the page or the embed lands on Money → Transactions and in the widget's Recent activity list.
If customers report that payments are unavailable, the Master switch is Off. If a payment is refused for its amount, it is outside the Amount range. If your logo is missing on the page, upload it on the Business profile card in Settings.
| On this screen | What it does |
|---|---|
| Turn on the pay widget | Shown once, before the widget exists. Sets up the widget and issues your first API key. |
| Live / Off / Revoked / Not configured | The status pill at the top of the page. |
| Copy URL / Preview | Copy the address of your hosted pay page, or open it as a customer sees it. |
| Master switch | ON accepts payments on the hosted page and the embed. OFF shows Payments aren't available on both. |
| Payment types | One switch per type: Fixed amount, Donations, Save card on file, Pay external invoice, Pay Merchant360 invoice, Subscriptions. Each saves on its own. |
| Amount range: Minimum / Maximum | Limits for every one-time payment and donation, checked on the server. |
| Branding: Brand color | The color of your pay page. The logo comes from Billing Settings → Business profile. |
| Allowed return domains | The only domains the pay page may send a payer to after paying. Your website domain is always allowed. |
| Receipts: From email / BCC email | From brands the receipt as you; BCC sends you a copy of every receipt. |
| Embed snippet: Payment type, Copy | The code to paste into your website for the chosen type. |
| Recent activity | The last 50 events on your widget with When, Mode, Amount, Customer, Card and Outcome, and Refund on each charge. Partial refunds are supported. |
- Set up card payment processing first – the pay widget needs active processing to be enabled.
- Your processing is not active yet. Click Set up billing tools, or ask Electronic Payments.
- Minimum can't be below $1.00. / Maximum can't be above $1,000,000. / Minimum must be less than maximum.
- Change the Amount range so the minimum is at least $1.00 and lower than the maximum.
- Brand color must be a 6-digit hex code like #1e293b.
- Pick the color with the color picker, or type a code such as #1e293b.
- From address isn't a valid email. / BCC address isn't a valid email.
- Check the address for typos, or clear the field.
- Customers see Payments aren't available
- The Master switch is OFF. Turn it ON.
- A snippet's type is refused
- That type is OFF under Payment types. Turn it ON.
Do this with the API:Pay widget
What your pay page can accept
The Pay widget is one tool that changes shape based on which payment types you turn on. Each type is a different way to collect. Mix and match them, or run just one; the page shows only what fits the link a customer opens.
- The Pay widget is turned on (see The pay widget & your hosted pay page).
- 1Fixed amount: you set the price (through the embed's amount or the Pay Now button) and the customer pays it. Best for a product, a booking, or a set fee.

Each type has its own switch and description. - 2Donations: the giver picks the amount from preset chips or types a custom value. Best for nonprofits, tips, and pay-what-you-want.
- 3Save card on file: no charge; the customer's card is vaulted for a future invoice or subscription.
- 4Pay external invoice: the customer types your own invoice number and the amount, and pays it. Best when your invoices live in QuickBooks, Xero, or another system.
- 5Pay Merchant360 invoice: the customer looks up an invoice you sent from Merchant360 by their email and customer code, sees the balance, and pays it. No link needed.
- 6Subscriptions: the customer enrolls in a plan you set up (daily to yearly) and the card is billed automatically.
Subscriptions need plans. On the Subscriptions page (linked from the widget, and listed under Recurring & plans in the Accept Payments menu) create each plan with a name, amount, billing period, and optional trial, setup fee, number of payments, and terms. Customers pick a plan on your pay page, the first payment is charged immediately, and the card is kept on file for the rest. The Subscribers list shows every enrollment with its status and next charge, and lets you pause, resume, retry a failed charge, or cancel.
The page also accepts what your Payment methods card allows: card, and bank when bank payments are enabled. Under dual pricing both prices are shown and the customer's choice sets the total.
If a customer cannot sign up for a plan, the Subscriptions payment type is off or the plan is archived. If a type the snippet asks for is not ticked under Payment types, the widget refuses it, so tick the type first.
| On this screen | What it does |
|---|---|
| Payment types | The six checkboxes that decide what the widget offers. Coming soon marks a type not yet available on your account. |
| New plan | Opens the New subscription plan form: Plan name, Description, What's included, Amount, Billing period (Daily, Weekly, Every 2 weeks, Monthly, Bi-monthly, Quarterly, Every 6 months, Yearly), Number of payments, Free trial (days), One-time setup fee, Terms, Create plan. |
| Archive (plan) | Hides a plan from new sign-ups. Existing subscribers keep billing. |
| Subscribers: All / Active / Paused / Failed / Cancelled | Filters the enrollment list. Each row shows the plan, payment count, and Next charge. |
| Pause / Resume / Retry now / Cancel | Per-subscriber actions. Retry now re-runs a failed charge once the customer updated their card. |
| Enable the Subscriptions payment type above | The warning shown on the plans card until Subscriptions is ticked. |
- Enable the "Subscriptions" payment type above before customers can sign up.
- Turn on Subscriptions under Payment types on the Pay widget page.
- Plan name is required.
- Type a Plan name in the New subscription plan form.
- Amount must be at least $1.00.
- Plans start at $1.00.
- Number of payments must be between 1 and 999, or left blank for open-ended.
- Type a number from 1 to 999, or leave it blank so the plan bills until it is cancelled.
Do this with the API:Subscriptions
What your customer sees
The secure pay page behind links, checkout sessions, WooCommerce and the extension.
What your customer sees on the hosted checkout
Every checkout session opens the same secure page: your logo and business name up top, the order summary on the left, and the payment form on the right. It is the page behind the Payment Extension's Open secure checkout, API-created sessions, WooCommerce's redirect and popup modes, and LeadConnector payments.
Where Apple Pay is available, an Apple Pay button appears above the card form automatically. On an iPhone or Mac the customer confirms with Face ID or Touch ID; in other browsers they scan a quick code with their iPhone. Nothing to set up on your side, and your pricing rules (surcharge or dual pricing) show on the Apple Pay sheet. The same button appears on your e-invoices' pay page.
On the card form, the card number masks its middle digits the moment the customer moves to the next field, the brand chip (Visa, Mastercard, Amex, Discover, and Credit or Debit) appears from the first digits, and expiry is picked from dropdowns, never typed. Mobile keychains can autofill the customer's own saved card. The Pay with Vault bar sits above the form for returning customers, and the Save my card with Vault box under it lets a new customer save their card for next time.
Sessions created with a Test key show a test-mode banner and never move money. Any custom payment fields enabled for Checkout are asked on the form, and the receipt is emailed the moment the payment succeeds.
If the Apple Pay button is missing, the customer's device or browser does not support it; the card form works as normal. If a customer's card is refused with an address error, the ZIP did not match the card's billing address.

| On this screen | What it does |
|---|---|
| Logo and business name | Pulled from your Business profile in Settings. |
| Order summary | The amount, description, and line items your session passed in. |
| Apple Pay | One-tap wallet payment where supported. Shows your surcharge or dual pricing on the sheet. |
| Pay with Vault | The bar returning customers use to pay with a card saved anywhere on Merchant360, verified by a texted code. |
| Card number, Exp month, Exp year, CVV, Billing ZIP | The secure card form. Number masks on blur; expiry is picked from dropdowns. |
| Brand chip | Visa, Mastercard, Amex, or Discover plus Credit or Debit, shown from the first digits. |
| Save my card with Vault to check out faster everywhere | Unchecked by default. Saves the card on success, tied to the customer's mobile number. |
| Custom payment fields | Any field you enabled for Checkout in Settings, asked before Pay. |
| Pay $X | The button always shows the exact total the card will be charged. |
| Test mode banner | Shown on sessions created with a Test key. No money moves. |
Do this with the API:Checkout sessions
Payment methods on the hosted checkout
The hosted checkout adapts to how the customer pays and to what your Payment methods card allows. Card is always there. Pay by bank appears when bank payments are enabled, and the session then shows BANK PAYMENT PROCESSING until the debit settles. Under dual pricing the customer sees the card price and the cash price and the total follows their choice.
The payment is done when the page shows the paid confirmation and the customer is sent to your success page. Card payments appear on Money → Transactions at once; bank payments appear on Money → ACH Transactions and settle on the bank schedule.
If Pay by bank is missing, switch on Bank (ACH / eCheck) on the Payment methods card. If the gift card box is missing, your eGift program is not on. If a split payment's card portion declines, the gift redemption is reversed automatically so the balance never strands.
- 1Card: the standard flow with masked number entry, brand chip, dropdown expiry, CVV, and ZIP, with the Pay button always showing the exact total. If your account runs a credit-card surcharge, the itemized Subtotal / Surcharge / Total box appears above Pay on credit cards.
- 2Pay by bank: the customer connects their bank or types the routing and account numbers, accepts the debit authorization on the page, and the payment shows the cash price under dual pricing. It settles in a few business days.
- 3Gift card, partial: when your eGift program is on, Have a Merchant360 gift card? appears above the card fields. Applying a card shows exactly what it covers and what remains; the customer's card pays the remainder, and any surcharge is computed on the card portion only.
- 4Gift card, full: a gift card covering the whole amount removes the card fields entirely and the button becomes Pay with gift card.

| On this screen | What it does |
|---|---|
| Card / Pay by bank | The tender choice at the top of the form. Pay by bank shows only when bank payments are on. |
| Subtotal / Surcharge / Total | The itemized box shown on credit cards when a surcharge program is active. |
| Card price / Cash price | Both totals under dual pricing; the tender sets which one is charged. |
| Have a Merchant360 gift card? | Opens the gift card entry when your eGift program is on. Apply shows what the card covers and what remains. |
| Pay with gift card | The button when a gift card covers the whole amount; no card is needed. |
| Apple Pay | One-tap wallet payment where supported. |
Do this with the API:Checkout sessions
For developers
API keys, checkout sessions and webhooks.
API keys for developers
If you build your own website or app, the API key card on the Pay widget page issues a key for server-to-server charges and for verifying payments. Issue a key, Re-issue to rotate it, or Revoke it. The full key is shown only once, so save it when it is created.
- 1On the Pay widget page, scroll to the API key card.
- 2Click Issue key (or Re-issue to replace the key you have).
- 3The box New key issued – save this now shows the full key. Click Show to read it or Copy to copy it, and store it on your server.
- 4To turn a key off, click Revoke and confirm. Any server that uses it stops working.
The embedded widget and hosted pay page do not need the key: they authenticate through the snippet itself. The key is only for direct calls from your server. Anyone with the key can run charges against your account, so treat it like a password.
Verify a payment on your thank-you page: when a Pay Now button sends the customer to your Success URL, we add ?m360_ref=... to the address. From your server (never the browser), call GET /api/cygma/v1/verify?reference=<that value> with your API key in the Authorization header. It replies whether the payment truly cleared, with the amount and card last four, so you can confirm the order before you fulfil it.
You are done when the card shows the key prefix with its issued date. For scoped keys, webhooks, and Test versus Live keys, use the Developers page instead; it is the fuller developer console.
If a key leaks, click Re-issue: the old key stops working immediately and the new one is shown once. If Revoke is used by mistake, any integration using the key breaks until you issue a new one and update your server.
| On this screen | What it does |
|---|---|
| Issue key / Re-issue | Creates a key or replaces the current one. The old key stops verifying at once. |
| New key issued, save this now | The one-time display of the full key with Copy and Show / Hide. After you close the card only the prefix remains. |
| Revoke | Disables the key. Any server-to-server integration using it stops working. |
| No key on file | Shown until you issue a key. The widget and hosted page work without one. |
- The card shows No key on file.
- No key has been issued. The widget and hosted page work without one; click Issue key only if a developer needs it.
- The full key is gone
- It is shown only once. Click Re-issue for a new key and update your server.
Do this with the API:Authentication
Developer checkout (hosted sessions)
Checkout (Accept Payments → Checkout) is for developers building payments into their own site or app. Instead of a drag-and-drop page, your code creates a secure checkout session through the Merchant360 API and sends the customer to a hosted pay page, or opens it as a popup with the Checkout Button. Card details never touch your site, and we redirect the customer back and notify your webhook when they pay.
- 1Go to Accept Payments → Checkout.
- 2Click Get API keys to open Developers & API and create a key, API docs for the developer reference, or Try the demo to see a sample checkout.
- 3Your developer creates checkout sessions through the API. Each one appears under Checkout sessions with its amount, description and customer email.
- 4Read the status on each row: OPEN, BANK PAYMENT PROCESSING, COMPLETE or EXPIRED. A test badge marks sessions made with a Test key. Click view payment to open the transaction behind a paid session.

Checkout: the buttons for developers and every checkout session.
The page gives you Get API keys, the API docs, and Try the demo, plus a list of every checkout session with its amount, description, customer, and status. Custom payment fields you enable for Checkout in Settings appear on the hosted page too.
A session is done when its status reads COMPLETE and view payment opens the transaction. Sessions created with a Test key carry a test badge and never move money.
If you just want a no-code way to collect a payment, use a payment link or the pay widget instead. If a session shows EXPIRED, the customer did not pay in time; create a new session. BANK PAYMENT PROCESSING means the customer chose Pay by bank and the debit is settling.
| On this screen | What it does |
|---|---|
| Get API keys | Opens the Developers page to create a Test or Live key with the checkout scope. |
| API docs | The developer documentation for creating sessions and handling webhooks. |
| Try the demo | Opens a sample checkout so you can see the hosted page before you integrate. |
| Checkout sessions (N) | Every session created on your account, newest first, with a count of how many are paid. |
| OPEN / BANK PAYMENT PROCESSING / COMPLETE / EXPIRED | The session status. OPEN is awaiting the customer; COMPLETE is paid; EXPIRED was not paid in time. |
| test | Badge on sessions created with a Test key. |
| view payment | Opens the transaction behind a completed session. |
- No checkout sessions yet. Create one through the API to see it here.
- Sessions appear only after your website or app creates them through the API.
- A session shows EXPIRED
- The customer did not pay in time. Create a new session.
Do this with the API:Checkout sessions
Developers: API keys & webhooks
The Developers page (in the Merchant360 menu, owner-only) is home base for building on Merchant360. It has two parts: scoped API keys and a signed-webhooks console with a delivery log. Only the account owner can create or revoke keys and endpoints.
- You are signed in as the account owner. Other logins see Owner access required.
- 1Go to Accept Payments → Developers & API.
- 2Under Create an API key, type a Name (for example Production server) and pick the Mode: Test or Live.
- 3Under Scopes, tick read and write for each area the key needs, or click a preset: Payments, Read-only or Everything.

Create an API key: name, mode and scopes. - 4Click Create key and type the code texted to you. Copy the key from Key created – copy it now; it is not shown again.
- 5Your keys lists each key with its scope count and when it was last used. Click Revoke on a key, or tick several and click Revoke selected keys.
- 6Under Webhooks, click Add endpoint. Type the Endpoint URL (https), keep All events (recommended) or untick it and pick events, then click Create.

Add endpoint: the URL and the events to send. - 7Copy the Signing secret – shown once and store it. Your server uses it to check the M360-Signature header.
- 8On each endpoint, the icons are Send test event, Rotate secret, Disable (or Enable) and Delete.
- 9Recent deliveries lists Event, Status, Attempts, Code and When. Click Retry on a FAILED delivery, or Refresh to reload the list.
API keys: each key has a name, a Test or Live mode, and the scopes it is allowed. Presets cover Payments, Read-only, or Everything, or tick scopes one by one. Test keys hit the sandbox and land on Test mode; Live keys move real money. The full key is shown once at creation. The same API charges cards and bank (ACH) alike.
Webhooks: add your https endpoint and choose which events to receive: all events, or specific ones such as invoice paid, payment succeeded or refunded, and ach settled or returned. Every delivery carries an M360-Signature header your server verifies with the signing secret, which is shown once and can be rotated.
You are done when the key appears under Your keys with its scope count and last-used date, and the endpoint shows Enabled with deliveries in the Recent deliveries log. Send test event proves the wiring before real events arrive.
If a delivery shows a failed status, check the Code column (your server's HTTP response) and click Retry; failed deliveries also retry on their own with backoff. If a key was exposed, Revoke it and create a new one. If you cannot see the page, you are signed in as a team member; it is owner-only.
| On this screen | What it does |
|---|---|
| Create an API key: Name, Mode, Scopes | Name labels the key (e.g. Production server). Mode is Test or Live. Scopes limit what the key can do; presets are Payments, Read-only, Everything. |
| Create key | Mints the key after a texted security code. The Key created banner shows it once with Copy. |
| Your keys | Every key with its scope count, last used date (or never used), and Revoke. |
| Revoke / Revoke N selected keys | Disables one key or every ticked key. Apps using them stop working immediately. |
| Add endpoint | Opens the form: Endpoint URL (https), Events (All events, or specific ones), Cancel. |
| Signing secret, shown once | The secret used to verify the M360-Signature header. Store it now; rotate the endpoint if you lose it. |
| Enabled / Disabled | Whether the endpoint currently receives deliveries. |
| Send test event | Posts a sample event to the endpoint so you can confirm your receiver. |
| Rotate secret | Issues a new signing secret. The old one stops verifying immediately. |
| Disable / Delete | Pauses deliveries, or removes the endpoint. Deliveries stop immediately. |
| Recent deliveries: When, Event, Status, Attempts, Code | The delivery log per endpoint. Code is your server's HTTP response. Refresh reloads it. |
| Retry | Re-sends a failed delivery now. |
- Only the account owner can manage API keys.
- Sign in as the owner, or ask the owner to create the key.
- Grant at least one scope.
- Tick at least one scope, or click a preset.
- Enter an https URL.
- Type the full endpoint address, starting with https://.
- A delivery shows FAILED
- Code is the answer your server sent. Fix the receiver, then click Retry. Failed deliveries are also retried on their own.
- A key or signing secret was exposed
- Revoke the key and create a new one, or click Rotate secret on the endpoint. The old secret stops working at once.
Do this with the API:Webhooks
Developers can do the same with the Merchant360 API.
