Skip to content
stratamize_

Merchant Portal

Share your public pay page and try sample checkout

Understand the general payment link, its QR code, and the customer checkout simulation.

Menus and available actions depend on your role and enabled services. In the local demos, use sample records only; no real payments or messages are sent.

Your public pay page lets customers pay your business without signing into the Merchant Portal. When enabled for your account, find Your public pay page under Invoices. The general payment link and an invoice-specific link serve different purposes: use the invoice's own link when collecting its balance.

  1. Open Invoices and find Your public pay page.
  2. Choose Copy link, or use Open page to inspect the customer experience.
  3. Confirm the merchant name and the purpose of the payment before sharing a live link.
  4. The QR code opens the same address as the displayed link.

A general payment should not be assumed to settle a particular invoice automatically. Check the payment and invoice records in your configured account. If clipboard access is unavailable, select and copy the displayed address manually.

What the customer needs to do

The available payment methods and charges depend on your merchant configuration. The customer does not need a Merchant Portal login.

  1. Check the business and amount. The general page asks for an amount. An invoice link may show the invoice number, items, due date and amount due.
  2. Provide billing details. Enter the billing name, receipt email and address. The current payment form requires a name, email, street and ZIP. City, state and an optional phone field are also available.
  3. Enter a payment method. For a card, enter the card information requested by the payment form. Bank payments appear only when enabled for the merchant and allowed for that invoice; they request the account holder, routing/account information and account type. Do not assume every merchant can accept both methods.
  4. Choose whether to save the method. Read the authorization before opting in. Saving a method places it with the merchant for future authorized charges. It does not create a customer login or a customer dashboard.
  5. Review the amount and authorization. Check the subtotal, any configured tax or payment-method fee, and the final amount. Correct errors before submitting.
  6. Submit once and wait for the result. Processing may take a moment. Avoid submitting again while the first request is still being handled.
  7. Read the result and retain the confirmation. Card approval and a bank payment submitted for processing are different outcomes. A bank submission should not be treated as settled funds.

Corrections, declines and uncertain results

If a field is incomplete, correct the indicated information before continuing. If a card is declined, the customer can correct the method or use an available alternative and make a new attempt. A decline is not a paid invoice.

An uncertain result needs a different response. If the page says the payment result could not be confirmed, or that payment succeeded but recording the receipt failed, the customer should contact the merchant before trying again. Check the transaction record and any confirmation reference first; a missing receipt does not establish that no charge occurred.

See payment statuses for the merchant-side interpretation. Receipt email behavior depends on the live payment result and configuration.

Practice the checkout demo

Open page now opens a standalone Juniper Market customer page. The copied link and QR point to that same page. This is a sample checkout for the design preview, not a live merchant payment link.

Enter made-up billing and payment details, or use the sample-fill buttons as a shortcut. Continue through payment entry, review, processing and the confirmation. The review shows the name, email, amount and masked payment details you entered. The bank option demonstrates a pending submission. Everything runs as a disconnected simulation in the page.

The separate demo controls let you practice success, decline and an uncertain result. Work through the form as a customer, review the masked payment details and authorization, then submit. Use the correction controls to go back and change details before paying. After success, inspect the sample confirmation and receipt; after a decline, correct the method and retry. For an uncertain result, follow the contact guidance rather than making a second payment.

The saved-method choice is part of the review. It is a simulation of permission for the merchant to retain the method, not registration for a customer account. A sample receipt or receipt-email preview demonstrates the information the customer would receive; no email is actually sent.

Understand the demo session

All customer activity stays in memory in the current page. Reloading, resetting or leaving clears it. A copied link in another tab starts fresh samples. Returning to the Merchant Portal opens its own fresh sample session; the customer page does not transfer its records into that separate document.

Use Reset sample checkout to start over. The demo does not move money, send messages, store payment credentials or contact a processor. Particle animation respects the device's reduced-motion preference; there are no particle pause controls.

For live saved-method management, see customer payment methods.

← All merchant portal user guideNeed help? Contact Stratamize →