NearPay

nearpay.io ↗

Embed contactless collection and payment-state handling in merchant software

SI Score
80/100
Pricing
Contact for Pricing AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Required AI reading, not confirmed

Ask SI about NearPay

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the NearPay homepage

What it does

NearPay provides payment infrastructure for software platforms and payment providers building merchant acceptance. Its software development kit adds contactless card collection to an app, while an alternative POS application can carry the business’s branding. Getting started involves the NearPay team; commercial terms and production access are arranged for the implementation.

The Saudi developer guide starts with a sandbox request using an email address, phone number and Android package name. In the dashboard, add the package under Apps, then create a terminal and assign it to a merchant. An unregistered application package cannot connect.

The app signs the user in with a one-time code, retrieves the available terminals and connects to the selected one. A purchase request includes the amount and a unique intent identifier, with an optional customer reference. Run it on a physical NFC-capable Android device with the required permissions.

Treat the card-read callback as an intermediate event. The completed purchase response determines whether the payment was approved or declined and provides transaction and receipt information. Keep that result tied to the order so a read card is not mistaken for a completed sale.

NearPay separates sandbox, a testing environment for Saudi payment approval, from production. Confirm the acquiring arrangement, supported market, compatible devices and settlement responsibilities with NearPay before planning a rollout. The free integration offer covers connecting the software; confirm live-processing charges separately.

Strengths

  • Dashboard roles can restrict users and assign or revoke access to particular terminals.
  • Transaction, reconciliation and terminal reports can be exported.
  • Remote integration supports communication with a payment device over Bluetooth or Wi-Fi.

Watch out for

  • On-device iPhone acceptance is still marked as coming soon on the features page.
  • Location access is required for the documented Android payment flow.

Best for

  • Software teams adding card acceptance to a merchant app
  • Payment providers deploying branded acceptance across a terminal fleet

Sources