Scan-to-Pay powers payment experiences across both in-store and remote selling scenarios, built on an integration with Stripe Checkout. This enables device-independent payment acceptance — customers pay on their own phone, tablet, or laptop rather than interacting with a physical payment terminal.
In-store, customers can pay at the point of sale or by scanning a QR code displayed in the Associate App. To initiate this, the associate selects the Scan-to-Pay payment option during checkout, which generates a QR code the customer scans to open a payment page on their own device.
Scan-to-Pay In-Store Transaction Warning
If the contents of the cart change while using the
Scan-to-Paypayment method , the associate must issue a NEW QR code. Once a new QR code has been generated via the Associate App, have the customer re-scan the QR code to invalidate the original payment link and pickup the corresponding changes in the cart value.
When using the QR code and Scan-to-Pay option, keep in mind associates are using an in-store checkout flow (even though the payment is treated as a card not present transaction), and as such, once the store associate sends the payment request to the customer, the associate MUST remain on the payment screen until the customer completes the payment. The store associate should not go back into the cart once a payment request has been made nor should they navigate off of the payment screen until the payment has successfully been completed.
Clienteling with remote selling, associates can initiate a shared cart session and send a payment link directly to the customer via SMS or WhatsApp. The customer reviews their remote shopping cart, and when ready selects the option to pay - directing them to a hosted Stripe payment page, where the shopper can complete the payment independently — no physical interaction required. Retailers must have Scan-to-Pay configured to enable this flow. Retailers must first enable clienteling for their NewStore account - checkout Engage Your Customers for more information.
Remote Carts and Remote Payment Links
When working with remote carts as part of Clienteling transactions, changes to the cart will be reflected in the underlying cart page URL. If the store associate makes a change to the cart (by adding or removing items) the cart page should be re-shared with the customer. This will also update the associated payment link so that it reflects changes in the total cart value.
Transaction handling: Scan-to-Pay transactions are processed by Stripe as Card-Not-Present (CNP) transactions, regardless of whether the customer is physically in-store. They appear in the retailers Connect account dashboard under the Payment Links section, as well as listed with all other payment transactions within that view. When the details of the payment are viewed, users will see additional information under the Checkout Summary - which will contain additional information captured during the remote payment link process - such as address information.
Fraud considerations: Because the customer is not physically present — particularly in remote selling and clienteling scenarios — these transactions carry a higher fraud risk profile, similar to standard eCommerce. It is highly recommended that retailers make use of anti-fraud tools such as Radar to guard against fraudulent activity. NewStore recommends working with your NewStore account manager to configure Stripe Checkout and risk settings appropriately.
Getting Started
Scan-to-Pay enables store associates to offer customers an innovative payment method where the customer can pay via a payment link URL. Since Scan-to-Pay follows an e-commerce, card not present flow, this also means payment methods not yet available via in-store payment terminals may be offered to customers via the payment link page. TO configured payment methods for Scan-to-Pay using Stripe Checkout - please review How Checkout Works. NewStore leverages the Full Hosted Page configuration - therefore, customization of the Payment Links pages may be limited.
To configure the Payment Link experience you will need to access your Connect Account dashboard and visit the Payment section of your Products Settings. Retailers have the ability to customize the following areas of the Stripe Checkout and payment link experience:
Address Auto-complete (leverages Google Maps for address accuracy). -
Toggle On/OffAdaptive Pricing Settings (used for real-time currency conversions to the shopper currency - if the need to support multiple currencies is needed).
Public information ( the specific public details - information displayed as the business name or on the statement descriptor for the shopper).
Appearance Go to the Branding Settings to upload your logo, icon, or to set your brand color scheme for the payment page.
Store Policies - Set communication preferences for displaying Refund and Return Policy, Legal Policies, of Contact Information
Caution:
Domain, Pricing Display, Subscriptions, Promotional Emails, are NOT currently supported via NewStore Scan-to-Pay and Stripe Checkout.
Completing the Scan-to-Pay configuration in NewStore Payments
After you have set up and configured the Stripe Checkout and Payment Link settings in the Connect dashboard, you will need to make sure the specific scan_to_pay payment option is added to your store configuration. Review your store configuration settings using the Update Payment Options Configuration API. Configure each store that will be setup to use either the in-store payment option for Scan-to-Pay or clienteling remote/ shared carts with payment links.
Using Stripe Checkout and Payment Links with NewStore Clienteling
Any store using NewStore clienteling MUST have the
scan_to_paypayment option added to the store level payment options configuration.