Source: https://billingmart.com/payment-links # Get paid with a link, no invoice needed Make a link or a QR code for a service, a deposit, a class or a ticket, share it anywhere, and take card payments on your own branded page. Fixed prices, a range the payer chooses, or tiers that rise as they sell, with a limit that never oversells. [How it works](https://billingmart.com/payment-links#how) [For developers](https://billingmart.com/payment-links#developers) Harbor Dance Studio Spring showcase · Saturday Ticket, current price $35.00 7 of 20 left Price includes all fees. Pay $35.00 A link, or an invoice? ## Two ways to ask for a payment An invoice is for one customer and one bill. A payment link is for anyone who should be able to pay, without an invoice. Both open the same secure pay page. Pricing ## Three ways to price a link One currency per link, and the amount is always worked out on BillingMart’s server, never trusted from the browser. ### Fixed price One amount for everyone: a consultation, a class, a service call, a deposit. The payer sees the price and pays it. Lawn service · $85.00 ### Payer chooses, within a range The payer enters the amount, between the minimum you set and an optional maximum. Useful for tips, contributions and pay-what-you-want. From $10.00 to $500.00 ### Tiers that rise as they sell Prices by payment sequence, the way early-bird tickets work. The price shown is always the current tier’s, and a payer is never charged a higher tier without confirming it. First 10 at $25.00 · next 10 at $35.00 Capacity ## Sell exactly as many as you have Reusable links take payment after payment; one-time links take one. Either way, the limit holds. ### A limit, if you want one Cap the number of payments. A seat is held while a payer checks out and released if they do not finish, so the link never sells more than you set. ### Sold out, then completed At the limit the link shows Sold out on its own and takes no more payments. A one-time link takes exactly one payment and then reads Completed. ### Show what remains, or not Turn on “show availability” and the page tells payers how many are left. Leave it off and nobody sees your numbers. ### An end date Give a link an expiry and it stops taking payments at that moment, with a clear message for anyone who opens it late. In the console ## Create, change and share from one page Payment Links sits in the console beside invoices and payments. Create Pick a preset (services, ticket or custom), a name, the currency, the pricing and an optional limit. The link and its QR code are ready at once. Edit Change the name, price, tiers, limit or expiry. The pay page follows the next time it is opened. Disable and reactivate Stop a link without deleting it, and switch it back on later. A disabled link tells payers it is not taking payments. New link Replace the address: the old link stops working immediately and a new one takes its place, with the same settings and history. Share Copy the link, or download the QR code for a flyer, a counter, an invoice footer or a slide. Audit Only an owner or admin can create or change a link. Every change is in the audit log, under the person who made it. For the payer ## A page that is easy to pay Everything the payer needs, and nothing they should not see: no counts unless you show them, and no internal settings. ### No account, no app The link opens your branded page on pay.billingmart.com: your name and logo, what they are paying for, and the price or the range. ### Pay by card Card details are entered on BillingMart’s payment page and pass through BillingMart’s payment function to the payment gateway. BillingMart does not store them, and they never reach your console, your staff or an assistant. ### A receipt by email When the payer enters an email address, they get a receipt with a PDF, and every payment lands in your console like any other, linked to the link that took it. ### Clear when it is closed Sold out, disabled, expired or replaced: the page says so in a plain sentence instead of an error. Fees ## An optional service fee, disclosed up front - An optional service fee on card payments, shown before the customer pays: a flat amount, a percentage, or both. - Itemised on the receipt, beside what was paid for. - Set per link, and only on a workspace BillingMart has enabled for fees. - Ticket links show the all-in price first, with every mandatory fee already included. More ## Donations, testing and your plan **Donations.** The Donation preset is available to workspaces verified as nonprofits, through their approved merchant application. **Test first.** In a sandbox workspace a link takes test payments end to end, and no money moves. **Every plan.** Payment links are on every plan. Each successful link payment counts as one send toward your plan’s monthly allowance. At the limit you cannot create or reactivate a link, but payers are never turned away: existing links keep taking payments. [See the plans](https://billingmart.com/pricing) . **Protected.** Payer calls are rate-limited, and a link that collects repeated declines is paused automatically, so it cannot be used to test stolen cards. Developers and assistants ## Read your links from the API, MCP and the Agent Links are read-only outside the console: creating, editing, disabling and replacing a link is done in the console, by an owner or admin. `GET /v1/payment-links` Every link in the workspace, newest first, with its pricing, limit, counts and status. Filter with status = active, disabled, soldOut or completed; page with limit (up to 50) and cursor. Scope `payments:read` · MCP tool `list_payment_links` (read-only) · [Reference](https://billingmart.com/developers/api/payments#paymentLinks-list) `GET /v1/payment-links/{linkId}` One link: its pricing, limit, counts, fee and status. Scope `payments:read` · MCP tool `get_payment_link` (read-only) · [Reference](https://billingmart.com/developers/api/payments#paymentLinks-get) `GET /v1/payment-links/{linkId}/summary` What one link has done: views, checkouts started, paid and abandoned, money collected (gross and after refunds), conversion, last activity and a 30-day series. Scope `payments:read` · MCP tool `get_payment_link_summary` (read-only) · [Reference](https://billingmart.com/developers/api/payments#paymentLinks-summary) `GET /v1/payment-links/{linkId}/views` Who opened one link: when, country, region and browser family, newest first, a page at a time. No address or browser string is ever returned. Scope `payments:read` · MCP tool `list_payment_link_views` (read-only) · [Reference](https://billingmart.com/developers/api/payments#paymentLinks-views) List the active links Sample ``` curl "https://api.billingmart.com/v1/payment-links?status=active&limit=20" \ -H "Authorization: Bearer $BILLINGMART_API_KEY" ``` Both routes are in the OpenAPI document and the API reference. An API key or an assistant connection needs the `payments:read` scope. A link’s custom name is the workspace’s own text, so it comes back inside the untrusted-data envelope, never as an instruction. Assistants connected through the BillingMart MCP server get `list_payment_links` and `get_payment_link`, and the built-in BillingMart Agent can answer “which links sold out this week?” from the same data. Next ## The whole API, route by route Payments, payment links and everything else the console does, with scopes and examples. [Open the Payments reference →](https://billingmart.com/developers/api/payments) ## Make your first payment link Create a link in the console, try it in a sandbox, and share it when you are ready. [Start free](https://app.billingmart.com/sign-up) [The MCP server](https://billingmart.com/developers/mcp) --- This is the Markdown copy of https://billingmart.com/payment-links. Live plans, prices and limits are published as JSON at https://billingmart.com/plans.json and https://billingmart.com/agent-info.json.