Payment Processing & Acquiring · Use case

Enable in-store and unattended payments

Scope this use caseTalk to us

Short answer

One provider can acquire online and in person, so all sales land in one settlement and one set of reports. Choose between dedicated terminals, SoftPOS on phones, and unattended devices based on where and how customers pay, and check certification per market.

What this use case is

One provider can acquire online and in person, so all sales land in one settlement and one set of reports. Choose between dedicated terminals, SoftPOS on phones, and unattended devices based on where and how customers pay, and check certification per market.

Who builds this

Omnichannel retailers
Hospitality
Mobility and parking
Vending and EV charging
Field-service businesses

What your customer sees

  1. 1Taps a card or phone at a terminal or on a staff member's phone
  2. 2Or scans a QR code
  3. 3Gets a receipt
  4. 4Online and in-store purchases appear consistently

How Payment Processing & Acquiring solves it

1

Terminal, phone or unattended reader captures the payment

Terminal, phone or unattended reader captures the payment

2

Transaction encrypted end to end

Transaction encrypted end to end

3

Authorisation via the acquirer

Authorisation via the acquirer

4

Approval shown at the device

Approval shown at the device

5

Settlement combined with online sales

Settlement combined with online sales

6

Unified reporting across channels

Unified reporting across channels

Want to have

  1. Certified terminals or SoftPOS in your markets
  2. Contactless and wallets
  3. Unified online and in-store reporting
  4. Terminal management
  5. Offline or fallback handling
  6. Refunds across channels

Optional

  1. QR payments
  2. Tipping
  3. Pre-authorisation for hospitality and mobility
  4. Integration with your till or ordering system

Design decisions

Hardware

Dedicated terminals
SoftPOS
Unattended readers

durability and features versus cost and flexibility.

Channel model

One provider for all channels
Separate in-store provider

unified data versus specialist features.

What to put in your RFP

Devices

  • models
  • certification per market
  • management

Channels

  • online plus in-store
  • unified tokens

Operations

  • offline handling
  • refunds
  • support and replacement

Commercials

  • hardware purchase or rental
  • transaction pricing
Add these to an RFP

How to evaluate providers for this use case

  1. 1Device availability and certification in your markets
  2. 2Unified reporting
  3. 3Hardware logistics and support
  4. 4Pricing across channels

Pitfalls

  • Devices not certified in a new market
  • Separate providers leading to split reporting
  • Ignoring pre-authorisation needs
  • Underestimating device logistics

What providers will ask you

  1. Locations and markets
  2. Number of devices
  3. Channels and volumes
  4. Existing point-of-sale systems

Other Finlane categories that cover parts of this

This use case is solved mainly with Payment Processing & Acquiring. These categories cover specific parts of it and can be tendered alongside it.

Fraud & AML Monitoring

Fraud controls across channels

Banking-as-a-Service

An account for combined settlement

Frequently asked questions

Other Payment Processing & Acquiring use cases

Accept online card payments

Add hosted checkout, drop-in or a fully custom card form with 3D Secure, wallets and stored credentials.

Run marketplace split payments

Split a single buyer payment across multiple sellers with automated payouts and reconciliation.

Reduce checkout friction internationally

Route transactions to local acquirers to lift authorization rates and unlock local payment methods.

Scope enable in-store or unattended payments with Payment Processing & Acquiring providers

Scope this use case