Solutions

PhonePOS - contactless payment acceptance via your smartphone

Rubean implements classic card readers (mPOS terminals) as a pure software (SoftPOS) app that runs on practically any NFC-enabled device for accepting contactless card payments. The corresponding PhonePOS solution has all the necessary certifications, in particular PCI MPoC software certification.

How PhonePOS Works

Step 1

The merchant enters the amount into his device.

Step 2

Consumer taps payment card on merchants device.

Step 3

PhonePOS processes the payment securely and quickly.

The future of cashless payment

Without extra hardware
Your payment terminal as an app, quickly installed from the Google Play Store. Complicated was yesterday. 
Contactless and secure
Certified by the Payment Card Industry (MasterCard, Visa, American Express, Discover Financial Services) according to PCI MPoC and approved by the German Banking Industry Committee for processing girocard transactions. 
The right solution for everyone 
PhonePOS on Android phones, handhelds, touchscreens; in merchant apps, mobile cash registers and self-checkout tills; with little to no user interaction to get started. 

PhonePOS MPoC SDK

Our PhonePOS MPoC SDK is an isolated SoftPOS SDK certified for Android 8+ devices. It is designed to ensure the highest level of security and seamless integration with customer POS solutions, banking applications or other payment applications.
In contrast to non-isolated SoftPOS SDKs, which are based on shared environments and would cause a significant certification effort on the integrator’s side, an isolated SoftPOS SDK like Rubean’s runs in a dedicated, secure environment that is completely separated from other app processes. This ensures maximum protection for sensitive payment data while minimizing the compliance effort on the integrator’s side.

PhonePOS MPoC APP

The PhonePOS MPoC APP integrates the PhonePOS SDK and forms it into an easily installable Android APP. The PhonePOS APP supports App2App communication with a higher-level electronic cash register, enterpris app or banking app in two modes: „hidden app” without displaying a PhonePOS icon on the device or a “visible app”.

Rubean Pay APP

The Rubean Pay APP extends the PhonePOS APP with a) a display for entering the payment amount and b) options for issuing a customer receipt (QR code, e-mail, SMS) and thus serves as a checkout app, especially for retailers who are looking for a simple solution for accepting contactless card payments on their smartphone.

PhonePOS Features

Our certifications

•⁠ ⁠Products: PCI MPoC Software (Isolated SDK for Android 8+), PCI MPoC Solution, GBIC girocard approval
•⁠ ⁠Operation: PCI DSS, PCI PIN, PCI SLC, PCI SSS.
•⁠ ⁠PCI MPoC isolated SDK certified
•⁠ ⁠PCI MPoC Software certified
•⁠ ⁠PCI MPoC Application certified
•⁠ ⁠PCI MPoC Solution certified
•⁠ German DK (Deutsch Kreditwirtschaft) certified for processing girocard transactions

Accepting payments has never been easier

Supported Android devices:

Minimum requirements:
  • Lumni8 Inari8C

  • Alcatel S1
  • Alcatel 3X
  • asus Zenfone 6
  • asus Zenfone 7
  • asus Zenfone 8
  • Blackview BV5200
  • Blackview BV5200 Pro
  • Bluebird EF501R
  • bq Aquaris X
  • bq Aquaris X Pro
  • bq Aquaris V Plus
  • Cat S62 Pro
  • Cat S62 Pro
  • Wingtech T Phone Pro
  • DOOGEE S41Pro
  • DOOGEE S100
  • DOOGEE S61
  • DOOGEE S97Pro
  • Elo M50C
  • Elo M50
  • Google Pixel 8, 8a, 8 Pro (or newer)
  • Google Pixel 7, 7a, 7 Pro
  • Google Pixel 6, 6a, 6 Pro
  • Google Pixel 4, 4a
  • Google Pixel 3, 3a
  • Honeywell CT40
  • Honeywell CT45
  • Honeywell CT60
  • Honeywell EDA5S
  • Honeywell EDA51
  • Honeywell EDA52
  • IMPORTANT INFORMATION: based on current information, HUAWEI devices do not get any further Android updates. Huawei handles thes updates over EMU operating system – currently only the below mentioned list is therefore supported:
  • HUAWEI Mate 40 Pro (or higher)
  • HUAWEI Mate Xs 2 (or higher)
  • HUAWEI Nova 9 (or higher)
  • HUAWEI Nova 9 Pro (or higher)
  • HUAWEI Nova Y90 (or higher)
  • HUAWEI P50 (or higher)
  • HUAWEI P50 Pro (or higher)
  • iHunt S60 Discovery Pro
  • SWIFT 1 PRO
  • SWIFT 2 PRO
  • SWAN 1 PRO (Dual Screen Support)
  • ITOS IC_51_EEA
  • DX-A400GE (NFC overlay Icon needs to be deactivated for PIN entry)
  • M20
  • C20 Pro (Dual Screen Support)
  • LGE LG G8S ThinQ
  • LGE LG Velvet
  • LGE LG V50 ThinQ
  • LGE LG K61
  • LGE LG Wing
  • Mobile Go 2+
  • MobiPrint 5
  • Motorola moto e22
  • Motorola moto E32
  • Motorola moto g 5G Plus
  • Motorola moto g7 power
  • Motorola moto g9 play
  • Motorola moto g9 plus
  • Motorola moto g10
  • Motorola moto G13
  • Motorola moto g13
  • Motorola moto g22
  • Motorola moto g30
  • Motorola moto g31(w)
  • Motorola moto g32
  • Motorola moto g41
  • Motorola moto g50
  • Motorola moto g51 5G
  • Motorola motto G53
  • Motorola moto g60
  • Motorola moto g62 5G
  • Motorola moto x4
  • Motorola edge 20
  • Motorola edge 20 litte
  • Motorola edge 30
  • Motorola edge 30 neo
  • Motorola edge 40+
  • Motorola one
  • Motorola Defy
  • Ordermann 9
  • NOKIA 3.1
  • NOKIA 3.4
  • NOKIA 4.2
  • NOKIA 5
  • NOKIA 5.1
  • NOKIA 5.3
  • NOKIA 5.4
  • NOKIA 6.1
  • NOKIA 9
  • NOKIA 7 Plus
  • NOKIA 8
  • NOKIA G21
  • NOKIA X10
  • NOKIA X30

OnePlus 7
OnePlus 8
OnePlus 9
OnePlus 11
OnePlus 5T
OnePlus 6T
OnePlus 7Pro
OnePlus 7T
OnePlus 8Pro
OnePlus 8T
OnePlus 9Pro
OnePlus 9R
OnePlus 10Pro
OnePlus 10Ttt
OnePlus Nord 2
OnePlus Nord 5G
OnePlus Nord CE 5G
OnePlus Nord N10 5G
OnePlus Nord N200
OnePlus Nord N300

  • oona 22
  • OPPO A 16 s
  • OPPO A 53
  • OPPO A 53 s
  • OPPO A 54 s
  • OPPO A 73
  • OPPO A 77
  • OPPO A 78
  • OPPO A 96
  • OPPO A 98
  • OPPO A 5
  • OPPO A 9
  • OPPO A 52
  • OPPO A 54
  • OPPO A 72
  • OPPO A 74
  • OPPO A 91
  • OPPO A 94
  • OPPO Find X2 Litttle
  • OPPO Find X2 Neo 
  • OPPO Find X2 Pro
  • OPPO Find X3 Neo
  • OPPO Find X3 Pro
  • OPPO Find X5
  • OPPO Find X5 Lite
  • OPPO Find X5 Pro
  • OPPO Reno
  • OPPO Reno 2
  • OPPO Reno 4
  • OPPO Reno 4 Pro
  • OPPO Reno 5
  • OPPO Reno 6
  • OPPO Reno 6 Pro
  • OPPO Reno 7 Z
  • OPPO Reno 8
  • OPPO Reno 8 Pro
  • Orderman 9 (only with additional Rubean attestation mechanism, as GMS is not supported)
  • Orderman 10 OSR
  • MT-6635 Rev. 3 (Note: This device requires Rubean PhonePOS 3.14 or higher)
  • PM 95 TP (Device does not support Google Play Integrity Attestation and therefore only works with special security verification, provided by Rubean. If you plan to use this type of device, please contact your Rubean sales representative).
  • Realme 6
  • Realme 7
  • Realme 8
  • Realme 9
  • Realme 11
  • Realme 6i
  • Realme 8i
  • Realme 9i
  • Realme C 21
  • Realme C 25s
  • Realme C31
  • Realme C35
  • Realme C51
  • Realme C55
  • Realme GT
  • Realme GT2
  • Realme GT Neo 3
  • Realme Narzo 50
  • Realme Narzo 60
  • Realme X50
  • Samsung Galaxy A03
  • Samsung Galaxy A04
  • Samsung Galaxy A12
  • Samsung Galaxy A13
  • Samsung Galaxy A14
  • Samsung Galaxy A20
  • Samsung Galaxy A21
  • Samsung Galaxy A22
  • Samsung Galaxy A23
  • Samsung Galaxy A30
  • Samsung Galaxy A31
  • Samsung Galaxy A32
  • Samsung Galaxy A33
  • Samsung Galaxy A34
  • Samsung Galaxy A40
  • Samsung Galaxy A41
  • Samsung Galaxy A42
  • Samsung Galaxy A50
  • Samsung Galaxy A51
  • Samsung Galaxy A52
  • Samsung Galaxy A53
  • Samsung Galaxy A54
  • Samsung Galaxy A70
  • Samsung Galaxy A71
  • Samsung Galaxy A72
  • Samsung Galaxy A75
  • Samsung Galaxy A8
  • Samsung Galaxy A80
  • Samsung Galaxy A9
  • Samsung Galaxy A90
  • Samsung Galaxy A92
  • Samsung Galaxy M31
  • Samsung Galaxy M32
  • Samsung Galaxy M33
  • Samsung Galaxy M51
  • Samsung Galaxy M53
  • Samsung Galaxy M12
  • Samsung Galaxy M20
  • Samsung Galaxy M21
  • Samsung Galaxy Note 10
  • Samsung Galaxy Note 10 Lite
  • Samsung Galaxy Note 20
  • Samsung Galaxy Note 8 SM
  • Samsung Galaxy Note 9
  • Samsung Galaxy S20
  • Samsung Galaxy S21
  • Samsung Galaxy S22
  • Samsung Galaxy S23
  • Samsung Galaxy S24
  • Samsung Galaxy S25
  • Samsung Galaxy S7
  • Samsung Galaxy S9
  • Samsung Galaxy S10
  • Samsung Galaxy S10 Lite
  • Samsung Galaxy Tab Active 3
  • Samsung Galaxy Tab Active 4 Pro
  • Samsung Galaxy Tab Active 5
  • Samsung Galaxy Tab S8
  • Samsung Galaxy XCover 4
  • Samsung Galaxy XCover 6
  • Samsung Galaxy XCover Pro
  • Samsung Galaxy Z Flip
  • Samsung Galaxy Z Flip 3
  • Samsung Galaxy Z Flip 4
  • Samsung Galaxy Z Flip 5
  • Samsung Galaxy Z Fold 2
  • Samsung Galaxy Z Fold 3
  • Samsung Galaxy Z Fold 4
  • Samsung Galaxy Z Fo
  • Sony Xperia XA 1
  • Sony Xperia XZ
  • Sony Xperia XZ 1
  • Sony Xperia XZ 3
  • Sony Xperia 10
  • Sony Xperia 1
  • Sony Xperia 1 II
  • Sony Xperia 10 IV
  • Note: Only GMS certified SUNMI devices are supported! For some devices, a request to SUNMI to activate GMS might be needed. Please contact Rubean support in case you need help to connect to SUNMI.
  • Note: SUNMI provides an active list of security patches and an overview of how long security patches will provided by SUNMI on the respective devices. Please see: https://developer.sunmi.com/docs/read/en-US/immeghjk546 for details.
  • SUNMI L2Ks_EEA (GMS)
  • SUNMI V2sNC_EEA (GMS)
  • SUNMI L2H (GMS)
  • SUNMI P2SE (GMS)
  • SUNMI V2s PRO (GMS)
  • SUNMI D2 mini (GMS)
  • SUNMI L2s PRO (GMS)
  • SUNMI V3 Mix (GMS)
  • SUNMI D3 Pro (GMS) (Dual Screen Support)
  • SUNMI T3 Pro (GMS) (Dual Screen Support)
  • TCL 6025H_EEA
  • TCL 5061K_EEA
  • TCL 5028Y_EEAULEPHONE
  • TORMAXX TX 600 LT
  • Ulefone Armor 7E
  • Ulefone Armor 8 Pro
  • Ulefone Armor X10 Pro
  • Ulefone Armor X6 Pro
  • Ulefone Armor X8
  • Ulefone Note 13P
  • Ulefone Power Armor 14 Pro
  • Ulefone Power Aroma X11 Pro
  • Ulefone Armor X7 Pro
  • Urovo i 6310
  • Vivo V 20 SE
  • Vivo V21
  • Vivo V23
  • Vivo Y21s
  • Vivo Y33s
  • Vivo Y52
  • Vivo Y72
  • Vivo Y76
  • XIAOMI 13
  • XIAOMI 11 Lite
  • XIAOMI 11 T
  • XIAOMI 11 T Pro
  • XIAOMI 12 C
  • XIAOMI 12 Lite
  • XIAOMI 12 Pro
  • XIAOMI 12 T
  • XIAOMI 12 T Pro
  • XIAOMI 13 Pro
  • XIAOMI MI 8
  • XIAOMI MI 8 Pro
  • XIAOMI MI 9
  • XIAOMI MI 9 Lite
  • XIAOMI MI 9 SE
  • XIAOMI MI 9 T
  • XIAOMI MI 9 T Pro
  • XIAOMI Mi 10
  • XIAOMI Mi 10 T
  • XIAOMI Mi 10 T Lite
  • XIAOMI Mi 10 T Pro
  • XIAOMI Mi 11
  • XIAOMI Mi 11 i 
  • XIAOMI Mi MIX 2
  • XIAOMI Mi MIX 2 S
  • XIAOMI Mi Note 3
  • XIAOMI POCO F2 Pro
  • XIAOMI POCO F3
  • XIAOMI POCO F4 GT
  • XIAOMI POCO M3
  • XIAOMI POCO M5
  • XIAOMI POCO X3
  • XIAOMI POCO X3 Pro
  • XIAOMI POCO X4 Pro
  • XIAOMI POCO X5
  • XIAOMI POCO X5 Pro
  • XIAOMI POCO X4 GT
  • XIAOMI Redmi 12 C
  • XIAOMI Redmi Note 8 Pro
  • XIAOMI Redmi Note 8T
  • XIAOMI Redmi Note 9
  • XIAOMI Redmi Note 9 Pro
  • XIAOMI Redmi Note 9 T
  • XIAOMI Redmi Note 10 
  • XIAOMI Redmi Note 10 C
  • XIAOMI Redmi Note 10 Pro
  • XIAOMI Redmi Note 10 Lite
  • XIAOMI Redmi Note 10 S
  • XIAOMI Redmi Note 11
  • XIAOMI Redmi Note 11 Pro
  • XIAOMI Redmi Note 11 s
  • XIAOMI Redmi Note 11 SE
  • XIAOMI Redmi Note 12
  • XIAOMI Redmi Note 12 Pro
  • XIAOMI Redmi Note 12 s
  • Zebra Technologies EC500K
  • Zebra Technologies EC55BK
  • Zebra Technologies EM45
  • Zebra Technologies ET56
  • Zebra Technologies MC2700
  • Zebra Technologies PS30
  • Zebra Technologies TC21
  • Zebra Technologies TC22
  • Zebra Technologies TC26
  • Zebra Technologies TC27
  • Zebra Technologies TC26BK
  • Zebra Technologies TC52AX
  • Zebra Technologies TC57
  • Zebra Technologies TC58
  • Zebra Technologies TC57HO
  • Zebra Technologies TC57X
  • Zebra Technologies TC77
  • ZTE Blade V40 Vita
  • ZTE Blade A72

Dec. 2024 statistics

0
Patent Families
0
Active Dealers
0
Transactions Dec 2024
0
Transaction Volume Dec 24

Frequently asked Questions

Basic Summary

PhonePOS transforms smartphones and tablets with NFC interface into point-of-sale (POS) terminals. It allows merchants to securely accept contactless payments – including NFC cards and mobile wallets – directly on their devices. PhonePOS eliminates the need for separate card readers. This offers businesses a convenient and flexible payment solution. It’s particularly beneficial for small or mobile enterprises, which can now accept payments anytime, anywhere.

That’s typically all you need, as the NFC-enabled device itself acts as the payment terminal.

Smartphone or Tablet: A device with NFC (Near Field Communication) capability to read contactless cards and mobile wallets.

Internet Connection: Wi-Fi or mobile data to process transactions and communicate with the payment gateway.

Software/App: A compatible PhonePOS application provided by Your payment service provider or acquirer. Usually, users can download from Google Play Store which is an online platform for digital content for Android devices.

To install and run PhonePOS app on your device, the minimum requirements are needed:

  • 64-bit Chipset / Operating System
  • Android Version 9+ (Android 12 recommended)
  • Google Play Services
  • NFC Support

Your payment service provider or acquirer will provide you with your individual contact information for your solution.

·      If you need general help with Rubean PhonePOS solution our support team at support@rubean.com will assist you.

·      If you need help integrating the PhonePOS solution, please contact SDK Integration Support. (sdk-integration-support@rubean.com)

Yes, PhonePOS can be used by small businesses, retailers, service providers, delivery drivers, freelancers, and more. It’s especially popular among businesses that need to accept payments on the go or in environments where traditional POS hardware isn’t practical.
Fees vary by provider and may include setup fees, transaction fees, or monthly service charges. It’s important to check with your PhonePOS provider for details specific to their offerings.
Yes, most PhonePOS solutions support international transactions, but it depends on the payment provider and the currencies they support. Always check with your provider about country-specific capabilities.

Setting up the PhonePOS app on your device typically involves a few straightforward steps, though specifics may vary slightly depending on the app and your device’s operating system. Here’s a general guide that should help you get started:

 

APK version SETUP:

  • Download/Get “PhonePOS” app with official name from your payment service provider or acquirer account or public on Google Playstore to be downloaded.

  • Tap on the app and then tap “Install”.

  • Initial Setup: Upon opening the app for the first time, you may be prompted to set up your individual account. This typically involves providing some basic information such as your Terminal ID and password. Please refer to your Account Manager from payment service provider or acquirer side for detailed information.

 

SDK version SETUP:

  • The PhonePOS app is integrated into the Partner’s ECR (Electronic Cash Register) app and is available for download through official channels.

  • To install, simply tap the app icon and select “Install.”

  • Initial Setup: When launching the app for the first time, you’ll be prompted to configure your account by entering the credentials provided under your contractual agreement. For further details, please contact your Account Manager.

Rubean offers a feature of additionally returning the receipt in a format that supports individual branded and designed receipt.
PhonePOS solution is distributed as an SDK & APK to be integrated with various ECR applications & different platforms such as MDM management tool.

There are strong security measures that are placed when using PhonePOS. The Mobile Payments on Commercial Off-The-Shelf (MPoC) standard is a framework developed by the Payment Card Industry Security Standards Council (PCI SSC).

It is designed to facilitate secure mobile payment acceptance using Commercial Off-The-Shelf (COTS) devices, such as smartphones and tablets.

Key Features of MPoC:

  • Security: Ensures that mobile devices used for payments are secure, protecting cardholder data and minimizing fraud.

  • Flexibility: Allows various types of payment acceptance methods, including PIN entry and contactless payments, on the same device.

  • Compliance: Helps merchants and payment solution providers meet PCI DSS requirements while using mobile devices.

  • The MPoC standard helps make sure that paying with your smartphone or tablet is as secure as using a traditional card reader.

  • Our MPOC apps require mandatory updates every three months to maintain security and address potential vulnerabilities.

For comprehensive information, resources, and documents related to MPoC, you can visit the PCI Security Standards Council’s official site at: https://www.pcisecuritystandards.org/

The measurements that need to be taken into consideration are listed below.

·      USB-Debugging must be turned off

·      ADB should be disabled

·      Device must not be rooted

·      Magisk must not be installed

·      Frida must not be installed

No additional hardware is required. PhonePOS operates entirely on your mobile device, eliminating the need for traditional payment terminals or card readers.

Troubleshooting

Please make sure the security points that are mentioned on the web page are fulfilled to operate PhonePOS app in a secure manner.
Please check if there are any whitespace characters in data field terminal id. There are no Whitespace characters before and after the terminal ID accepted. A regular terminal id is 8 characters/digits long. No space is allowed.
Wrongly inserted Terminal ID or Password or Mismatch of Environment (PROD or TEST) from Terminal ID with PhonePOS App or Terminal does not exist or was not onboarded yet. First, please check if you have entered the Terminal ID and Password correctly without the whitespaces (as explained in the previous answer). If you are sure that credentials are correct, please contact the customer support service of your payment provider or support@rubean.com to conduct further investigation.
The Authentication process has been cancelled and cannot be restarted without customer support. Contact Rubean Customer Support via support@rubean.com
The confirmation link in the authentication process expires after 60 minutes. Please request a new code from your service provider.

Check the following steps:

·      Check Internet Connection: PhonePOS requires an internet connection for transaction processing. Ensure your device is connected to Wi-Fi or mobile data.

·      Restart the App: Close and reopen the PhonePOS app to resolve temporary issues.

·      Reboot Your Device: Sometimes a device restart can resolve app launch problems.

·      Update the App: Ensure you are using the latest version of the PhonePOS app. Go to the Google Play Store to check for updates.

·      Clear App Cache (Android): If you’re using an Android device, clearing the app’s cache in Settings > Apps > PhonePOS can help.

Our solution supports contactless, NFC-based POS acceptance for the following card brands and e-wallets. But this can also be restricted by your Payment Service provider and/or acquirer, so please also consult with them

·      Apple Pay

·      Diners

·      Discover

·      Girocard

·      Google Pay

·      Maestro

·      Mastercard

·      Pulse

·      Samsung Pay

·      VISA

·      VISA Electron

·      VPAY

The solution itself has no restrictions. Restrictions may come from the payment service provider, acquirer or the payment method/card type used.

·      Limits on transaction amounts, frequency, types of transactions or currency can differ.

·      The payment service provider or acquirer can help here. If a digital wallet is used, it is also advisable to obtain information from the respective provider.

Usually, payments below CVM limit can be completed without entering PIN. Please note that the issuer bank of the card can still request PIN entry even for payments below the CVM limits, as per Strong Customer Authentication rules, unless a digital wallet is used (more on this in the next answer). 

A contactless payment limit, also known as a cardholder verification method (CVM) limit, is the maximum amount your customers can spend with a contactless card before needing to provide a PIN. These limits help protect against fraud and vary by country or can be set by the issuing or acquiring bank. When customers use a digital wallet on their mobile phone for contactless payments, two-factor authentication is usually required, and there is no contactless payment limit.

Example:
Limits for Germany, France, Italy, Spain 50 EUR
Limits for Hungary are: Plastic cards: 15000,00 HUF, Wallet: 999999,99 HUF (e.g. GooglePay)
Limits for Czech Republic 500 CZK
United Kingdom 100 GBP
PhonePOS app is able (has Payment APIs) to handle the following cancellation transaction types: VOID (Reversals), Referenced refunds and Unreferenced Refunds. Exact types available for your version of the application, as well as additional Rules & restrictions should be checked with your payment service provider or acquirer.
PhonePOS does enforce a minimal battery percentage of 10% to start a transaction. This ensures that no transaction is lost due to an empty battery.
This means that the transaction has not been accepted by the card-issuing bank. There may be various reasons for this, which the customer can only enquire about with their card-issuing bank. You can ask your customer for another card (or contact the authorization department of the respective credit card company).
Please make sure to tap / present the card on the NFC field within 40 seconds approximately, otherwise the payment will be terminated automatically with response code 524. For further information on Rubean Payment Response Codes see list under (online link).
No, this is not allowed per mPoC Security guidelines. Overlay detection will terminate the payment immediately with response code 505 or 560. For further information on Rubean Payment Response Codes see list under (online link).
Not all contactless cards and NFC reader antenna work the same and card placement can affect performance. Some cards are just trickier to read than others.
For example:
 
  • Girocard & Mastercard/Visa (Germany) – Some banks issue cards that function as a Girocard (for local payments) and a Mastercard or Visa (for international payments)
  • Retailer Cobranded Cards – Some major retailers or gas stations issue cobranded Girocard-Mastercard/Visa cards, offering special benefits like cashback or discounts.

If a card hasn’t been read, try these steps:

  • First, ask the customer to place their card flat against the reader for a few seconds.
  • If that doesn’t work, they can try sliding the card slightly while keeping the chip centered at the antenna field of the device.
  • In case there is no response/feedback at all, it could have a damaged NFC field or may not support contactless payments.
  • If the card is damaged, try using another NFC-enabled card or payment method.

Check the following steps:

  • Network Issues: Slow or unstable internet can delay transaction processing. Ensure you have a stable connection (Wi-Fi or mobile data).
  • Reattempt Transaction: If the transaction times out, try restarting the app and reattempting the payment.
  • Payment Processor Delay: Contact your payment processor to check if there’s an issue on their end.
  • Cancel and Retry: If the payment seems stuck, you may need to cancel and retry the transaction, ensuring all details are correctly entered.

This message indicates that the system has detected a potential issue with the device. It could be due to hardware problems, outdated software, or unusual activity.

The mobile device must remain in a secure state. Rooting, ADB debugging, or any methods that compromise security are prohibited. The PhonePOS SDK & APP ensure a secure environment for accepting contactless payments. Processing on devices that do not meet the strict security requirements is halted. Please check if no security compromising processes/methods/permissions are enabled on the device and the application is updated to the latest version. After that please try to:

  • Reboot Your Device, re-start the application and then re-try the payment. This will force-trigger another security check that can confirm if the issue with your device has been resolved.

If these did not help to resolve the issue, please contact the customer support of your Payment Service Provider or support@rubean.com for conducting further investigation.

Check the following steps

  1. Development Best Practices
  • Handle Unknown Status Transactions: If a transaction status is unclear (e.g., timeout or network failure), implement a recovery mechanism to check the actual payment status of “unknown” transaction before trying. Please refer to the online documentation.
  1. Incident Handling
  • Check Transaction History: Review the transaction logs to confirm if a duplicate charge occurred.
  • Wait for Confirmation: Some payments may appear pending in the app but will resolve after a few minutes once processed.
  • Notify Your Payment Processor: If a duplicate charge is confirmed, notify your payment processor immediately to resolve the issue and issue a refund if necessary.
  • Refund the Transaction: If you discover a double charge on your end, you can process a refund through the PhonePOS app or your payment gateway.

Check the following steps:

  • Note the Error Code/Message: Take note of any error codes or messages displayed in the app, as they may provide important information about the issue.
  • Restart the App/Device: Close the app and restart your device.
  • Contact Support: If the error persists, reach out to the customer support team for your PhonePOS solution, providing them with the error details.

Check the following points:

  • If the issue persists after following the troubleshooting steps.
  • If you encounter system outages or failures that prevent you from processing payments.
  • If you have questions regarding your account, merchant profile, or technical limitations.

Glossary

A developer tool that allows an Android device to be controlled from a computer. Must be disabled for PhonePOS usage to ensure security.
A file format used to install Android apps. Some PhonePOS versions can be downloaded as an APK.
The process of verifying a user’s identity, e.g., by entering a password or a one-time password (OTP).
A bank or company that processes card payments for a business, making sure funds move securely from the customer’s bank to the merchant’s account.
Commercially available devices such as smartphones or tablets that can be used for payments with PhonePOS.
A method for verifying cardholder identity during card payments, e.g., by entering a PIN.
A payment method that allows customers to make purchases by tapping their NFC-enabled card or mobile device on a PhonePOS -enabled device. It’s a quick and secure way to process payments without needing physical contact or PIN entry.
An electronic cash register used in stores for payment processing. PhonePOS can be integrated with such systems.
A global standard for credit and debit card payments based on chip technology. PhonePOS solutions may support EMV transactions, particularly for cards with embedded chips or PIN verification.
A system used by organizations to manage, secure, and monitor mobile devices like smartphones and tablets. It helps enforce security policies, deploy apps, and remotely lock or wipe devices if needed.
A digital wallet app (such as Apple Pay, Google Pay, or Samsung Pay) that stores credit or debit card information and allows customers to make contactless payments using their mobile device. PhonePOS can accept payments from mobile wallets.
A security standard that ensures mobile payments via commercially available devices (COTS) are secure.

A technology that enables contactless payments by allowing the chip of a payment card to communicate with a reader over short distances.

A one-time-use code for secure login or authorization.
A technology that securely transmits payment information from the merchant to the payment processor or bank for authorization. In PhonePOS, the payment gateway is responsible for routing transactions and ensuring secure communication.
A company or service that handles the actual transaction process, ensuring the funds are transferred from the customer’s bank to the merchant’s account. The payment processor plays a key role in the PhonePOS payment ecosystem.
A numeric code used to confirm a card payment or login.
A sales location where payments are processed. PhonePOS replaces traditional card readers.
A transaction where the merchant returns funds to a customer after cancelling or reversing a sale. PhonePOS systems often provide functionality to process refunds directly within the app.
A collection of programming tools for integrating PhonePOS into other software applications.
A unique identifier for a payment terminal, necessary for activating PhonePOS.
A security measure requiring two different verification methods (e.g., password and OTP).
A modern smartphone processor that is faster and more powerful than older 32-bit versions. It helps apps run more smoothly and efficiently. Most new devices come with a 64-bit processor.

Almost all new smartphones today come with a 64-bit chipset. Since around 2015, major brands like Samsung, Apple, and Google have switched to 64-bit processors in their devices.

For Android:

  • Nearly 100% of flagship and mid-range phones released in the last 5 years (2020–2025) are 64-bit.
  • Some very low-end budget models (especially in developing markets) might still use 32-bit, but they are rare.

For Apple:

  • 100% of iPhones since 2017 (iPhone 5s and later) are 64-bit.
Are you ready to expand your business?
With our help and expertise, we can develop new strategies together to scale your business and win more customers.
Rubean Logo schwarz

Rubean AG is a multinational fintech company based in Munich, Germany, and the leading provider of pure software point-of-sale solutions for banks, acquirers and merchants.

Support
Contact
Kistlerhofstraße 168 – München