Store Management

Payment Page for Business: The Complete Guide

Written by The StoreChart team7 min read

In short

A payment page is a secure checkout that opens from a link, so a customer can pay without browsing a store. In StoreChart you choose catalog products or type custom lines, allow up to 36 installments, optionally create an order automatically, and share the link anywhere. Card payments run through the Tranzila terminal connected to your store.

Not every sale starts in a shopping cart. A customer asks about a custom order on WhatsApp, a returning client wants a quote for ten units, and a workshop needs a deposit before the date. Sending people to your storefront and hoping they find the right product adds friction at the exact moment they are ready to pay. A payment page for business removes that friction: one link, the exact items and amount you agreed on, and a card form. This guide explains how payment pages work in StoreChart, what the customer sees, what happens after they pay, and when a full checkout is still the better choice.

What is a payment page

A payment page is a standalone checkout that lives at its own link. It shows only what the customer is paying for: the items, the total, and a form to pay. There is no catalog to browse and no cart to build, which is exactly the point.

Payment pages fit sales where the decision has already been made:

  • Quotes and custom orders. You agreed on a product, a price and maybe a delivery fee in a conversation. The page turns that agreement into a payment.
  • Chat and phone sales. A customer who asks on WhatsApp or calls in can pay from the same phone a minute later.
  • Deposits and bookings. Workshops, events and made-to-order products where you collect money before delivery.
  • Selling without a store. Businesses that sell a handful of products on social media can take card payments without building a website first.

Because a payment page is just a link, you can send it anywhere:

  • Chat: a WhatsApp conversation or any other messaging app.
  • Text and email: straight to the customer, with a short line of context.
  • Social media: the link in your profile or a direct message.

How to create a payment page for business

Payment pages live under Charges → Payment pages. Creating one takes a few decisions:

  1. Choose the store. The store needs an active payment provider. If none is connected, StoreChart refuses to create the page instead of letting you share a link nobody can pay.
  2. Add the items. Pick products from your catalog or type a custom line with a name, price, quantity and optional SKU and description. Prices are VAT-inclusive by default, so the amount you type is the amount the customer pays.
  3. Set the installment cap. Anything from 1 to 36 payments. The customer chooses within that limit.
  4. Decide whether to create an order. Turn this on and every successful payment also creates an order. You choose delivery or pickup, the shipping price (pre-filled from your store's default), the status the order lands in, and which sales channel gets the credit.
  5. Add an expiry date if it makes sense. After that date the link stops accepting payments.
  6. Save and copy the link. You can open it to check exactly what the customer will see.

You can edit a page later or disable it with one click. Payment pages are a plan feature, so check pricing to see which plans include them.

What the customer sees on the page

The page has two parts: a summary of what the customer is paying for, and a short payment form.

Order summary and VAT

  • Branding: your store name and logo.
  • Items: each item with its quantity.
  • Summary: subtotal, shipping (when relevant) and total.
  • VAT: broken out using the store's rate; in Israel that is currently 18%.
  • Price display: depending on your store settings, prices appear including VAT or before VAT with a separate VAT line.

The payment form

  • Required fields: first and last name, email and phone.
  • Optional fields: a second phone number, company name and company number, which help business customers who need the invoice in their company's name.
  • Delivery address: when the page creates a delivery order, city, street and house number are required. Entrance, floor, apartment and notes are optional.
  • Payment details: the card details, an optional ID number, and the number of installments.

After a successful payment the customer sees a confirmation, including the order number when the page created an order.

What happens after payment

A lot happens behind that confirmation screen, and none of it needs manual work:

  • The charge is recorded. Every attempt, successful or declined, appears in Charges with "payment page" as its source, so you can see failed tries as well as payments.
  • The customer is matched. StoreChart looks up the customer by phone in that store and links the payment to the existing record, or creates a new one in your customer CRM.
  • The order is created. If the page is set to create orders, the order appears in orders with its items, shipping, status and sales channel, is marked as paid, and its timeline shows that it came from a payment page. New orders also trigger the in-app notification.
  • SUMIT issues the document. With SUMIT connected to the store and the payment-page switch on, SUMIT issues the invoice or receipt automatically. StoreChart itself does not issue documents.
  • The page counter updates. Each page tracks how many payments it collected and when it was last paid.

Copy the link and paste it into the conversation, in the StoreChart WhatsApp inbox your team already uses or anywhere else. A good message is short and specific:

  • What it's for: in the words you used in the conversation.
  • The amount: exactly as it appears on the page.
  • Validity: until when the link accepts payments.

"Here is the link for the two custom shelves we discussed, 1,450 total, valid until Thursday" converts better than a bare URL. Remember that the link is reusable: for a personal quote, set an expiry date or disable the page once it is paid, so it is not paid twice by accident.

Payment pages that convert: 6 rules

Most of the work happens before the customer opens the link:

  • Name items the way you discussed them. If you agreed on "oak dining table, 180 cm", the page should say exactly that, not an internal SKU.
  • Match the amount to the conversation. Any surprise, such as shipping they did not expect, is a reason to stop and ask questions.
  • Offer installments on bigger tickets. For expensive items, the option to split the payment often decides the sale. Set a cap that your terminal supports.
  • Use expiry dates for honest urgency. A quote that is valid until Thursday is a real deadline, not a fake countdown.
  • Send it while the conversation is warm. A link sent right after a call converts better than one sent the next morning.
  • Check it on your phone first. Most customers will open the link on mobile.

Tracking payment page results

The payment pages screen opens with summary cards:

  • Pages: how many pages you have, and how many are active, disabled or expired.
  • Payments: how many payments they collected in total.
  • Revenue: how much money the pages brought in.
  • Usage: how many pages have been paid at least once.

Each page card shows its own payment count and last payment date, so a quote that was never paid is easy to spot and follow up. For deeper analysis, filter the Charges list by the payment page source, or filter orders by the sales channel you assigned to your pages.

Payment page or full checkout

Payment pages excel when the customer already knows what they want. When they want to browse, your store's checkout is the better tool:

SituationThe right tool
A single product or a custom quotePayment page
A chat-driven sale where the decision is madePayment page
A deposit for a workshop, event or made-to-order itemPayment page
Browsing the catalog and comparing productsStore checkout
A multi-item cart the customer builds themselvesStore checkout

Forcing open-ended browsing through a fixed link creates more friction, not less. Use payment pages to close a specific, already-decided sale fast, and keep your regular storefront checkout for browsing.

A payment page turns an agreed sale into a paid one without asking the customer to find their way through your store. In StoreChart, the same link can create the order, match the customer, pass the payment to SUMIT for the document and record every attempt. The only thing left for you is fulfilling the order.

Frequently asked questions

Which payment providers work with StoreChart payment pages?

Payment pages charge cards through Tranzila, the Israeli payment gateway, connected per store with your own terminal. A page can only be created for a store with an active payment provider, and if the provider is later switched off, the link shows as unavailable instead of accepting a card it cannot charge.

Can customers pay in installments?

Yes. You set a maximum between 1 and 36 on each page, and the customer picks any number up to that cap. Your terminal agreement still has to allow installment transactions, otherwise the gateway declines the charge.

Can the same link be paid more than once?

Yes. A payment page is reusable, and the page card shows how many payments it has collected and when it was last paid. For a one-off quote, set an expiry date or disable the page after the customer pays.

Does the customer get a receipt or invoice?

If your store has SUMIT connected, a document is issued automatically after each successful payment. A per-store switch turns this off for payment pages. StoreChart itself does not issue invoices or receipts.

See StoreChart with your own store data

Open an account, connect your store and see your own numbers.