Overview

The ShopBack In-Store Payments API lets you accept ShopBack Pay for in-store and point-of-sale (POS) payments.

That includes classic counter and terminal checkout and in-store / POS payments taken through a customer-facing app or customer-facing website (for example table ordering, order through app, browse-and-pay in store).

If the customer is paying at a physical location or on-premise station, and your system starts the payment, this is the right API — whether the UI is an app, a website, a kiosk, a cashier screen, or a payment terminal.

Who this is for

This API is for merchants and payment partners who want to accept in-store / POS ShopBack Pay on surfaces they already operate, including:

Surface	What we mean	In-store / POS role
Customer-facing app	Shopper-facing mobile or tablet app	Takes in-store or on-premise POS payment inside the merchant app
Customer-facing website	Shopper-facing web experience	Takes in-store or on-premise POS payment in the browser
Kiosk	Self-checkout or self-service ordering	Customer pays at the kiosk as the point of sale
Cashier	Staff-operated counter or register	Staff completes the in-store sale for the customer
Payment terminal	Payment hardware or softPOS	Terminal initiates or confirms the in-store payment

Customer-facing apps and websites are first-class in-store / POS surfaces for this API. Use them when the shopper pays through your digital experience for fulfilment in-store and promotions may take place at specific stores or outlets. When completing a remote online checkout, use the Online Bespoke Integration.

When to use In-Store vs Online

Use In-Store Integrations	Use Online Bespoke Integration
In-store or point-of-sale payment at a physical location or on-premise station	Remote online checkout in a normal e-commerce journey
Payment started from a customer-facing app, customer-facing website, kiosk, cashier, or payment terminal and goods or services are provided in-store	Goods or services are delivered remotely to the customer

How payments work

ShopBack supports three methods for in-store / POS payment. You can offer one or more, depending on the surface.

Method	Best for
Merchant-presented QR	App, website, kiosk, cashier display, or terminal shows a QR
Customer-presented QR	Cashier, scanner, or terminal scans the customer’s ShopBack QR
URL redirect	Customer-facing apps and websites — customer is sent into ShopBack to pay, then returned to your app or site

Merchant-presented and customer-presented QR work across apps, websites, kiosks, cashier flows, and terminals. URL redirect is for customer-facing apps and websites used as the in-store / POS payment UI.

Merchant-presented QR

Your in-store / POS experience displays a ShopBack QR — including on a customer-facing app or website screen, or on a kiosk, cashier display, or terminal. The customer scans it with the ShopBack app and pays.

Best fit when the customer is looking at your screen at the point of sale (app, web, or hardware).

Customer-presented QR

The customer shows a ShopBack QR. Your cashier, scanner, terminal, or assisted in-store flow reads it and submits the payment.

Best fit when staff or a terminal scans the customer during an in-store / POS payment.

URL redirect (customer-facing apps and websites)

For in-store / POS payments through a customer-facing app or website, you can send the customer into ShopBack via a URL redirect to complete payment, then return them to your app or website when done.

Use this when your on-premise app or website should hand the customer to ShopBack’s payment experience (instead of only showing or scanning a QR on your screen).

Best fit for customer-facing apps and websites acting as the in-store / POS checkout UI — not for kiosk-only, cashier-scan, or payment-terminal hardware flows that rely on QR at the device.

Getting started

Confirm you are accepting in-store / point-of-sale payments or payments via a customer-facing app or website where the goods or services are provided on premise and promotions are performed for specific stores
Choose merchant-presented QR, customer-presented QR, or the URL redirect approach.
Follow the Implementation guide for the integration and certification path.
Use API Reference — Getting Started for credentials, base URLs, and endpoint details.

Next steps

Implementation — how to integrate and certify
API Reference — Getting Started — credentials, environments, endpoints
In-Store API Troubleshooting List
Postman Payload Sample