Skip to main content
Industrial x86 and Android Embedded Board | Wanlin
Hotline
Customer Service Hotline:

+8613261677119

Engineering FAQ · Wanlin

Where can Suva equipment builders source private-label public service payment terminal board solutio

RFQ requirements for public service payment terminal board references. Confirm the exact model, firmware, provider role and required evidence before discussing configuration or private-label scope.

Direct answer

RFQ requirements for public service payment terminal board references. Confirm the exact model, firmware, provider role and required evidence before discussing configuration or private-label scope.

Product overview: What the smart payment terminal Android board actually is

The smart payment terminal Android motherboard is a payment carrier built on the Rockchip RK3568 and RK3576 platforms, with the Allwinner A133 and A64 as the cost-optimised tier and the RK3566 as the mid tier. It belongs to the same deployment family as countertop cashier terminals, self-service payment kiosks, self-ordering restaurant kiosks, unattended vending and EV charging payment units, parking and ticketing machines, handheld and portable payment devices, biometric wallet acceptance terminals and smart locker controllers - which is exactly why one carrier now gets re-spun into eight different product lines.

The design brief behind the platform was cost per terminal and payment peripheral integration, not raw CPU score. That is the right brief for a 4,000-unit EV charging site and the wrong brief for a bank certification programme or a sun-loaded outdoor enclosure, and that tension is what produces most of the incidents in this report. Seven characteristics define the platform:

  1. Rockchip RK3568 and RK3576, with Allwinner A133 as the value tier. Enough headroom for a payment stack, a scan engine, a printer and a launcher shell. The RK3576 adds the NPU path that face match, age verification and AI product recognition need, and a CPU-only inference build is the single most common reason a biometric terminal misses its gate timing.
  2. Payment peripheral seats, not just ports. A 58mm or 80mm thermal printer on its own UART lane, a 1D and 2D scan engine on a second seat, NFC contactless, IC card, magnetic stripe and PSAM on their own controllers. Sharing a lane between the printer and the scanner is the failure that generates the most field returns on this platform.
  3. 2GB to 8GB LPDDR4 or LPDDR4X with 16GB to 128GB eMMC. Comfortable for a transaction client with a local batch store. Tight if the unit also runs a camera preview, a face model and a catalogue database at the same time.
  4. TF card expansion for the offline catalogue. The card is the offline store for smart retail catalogues, unattended sites and any location with no reliable link - and it has to be indexed in full, not in part.
  5. 4G LTE, dual-band WiFi, Bluetooth 5.0 and 5.4, GPS and BeiDou. Dual SIM or eSIM on the carrier build. The radio plan is decided by the market, and a single-uplink plan is what breaks a restaurant that needs the kitchen printer on LAN and the payment on cellular at the same time.
  6. Serial control, watchdog, RTC and secure OTA. RS232 and RS485 for locker and dispenser control, the watchdog and the RTC for unattended recovery, and the OTA path for who owns the update key.

Specifications: What the AS-RK3568-BGV-CUS custom board ships with

The AS-RK3568-BGV-CUS is a re-spin of the standard payment terminal carrier: the platform of your tier, a compact multi-layer PCB laid out for the customer housing, industrial-grade components throughout, with conformal coating optional. The specifications below are the standard default; every line is re-specable on request.

Published configuration reference — confirm the exact model, revision and current documents.
BlockSpecification
SoCRockchip RK3568 or RK3576; RK3566 mid tier; Allwinner A133 or A64 value tier; 64-bit quad-core or octa-core Cortex-A55 and Cortex-A76 options
NPUOn the RK3576 tier, available for face match, age verification and AI product recognition inference
Memory1GB, 2GB, 4GB or 8GB LPDDR4 and LPDDR4X; LPDDR5 on request
StorageOn-board eMMC 8GB to 256GB, eMMC 5.1; TF card or Micro SD expansion on the custom build
Operating systemAndroid 11 to Android 15; Linux, Ubuntu, Debian, OpenHarmony, Kylin OS and UOS on request; kiosk mode with a locked launcher and auto-start app
Display5.5-inch, 6-inch, 7-inch or 8-inch panel on MIPI DSI, with LVDS, eDP and HDMI output options; 1024x600, 1280x800 and 1920x1080; portrait and landscape; dual display with a customer screen
TouchCapacitive multi-touch at 5, 10 or 20 points; resistive and IR touch on request; calibration profile per housing
Printer58mm or 80mm thermal printer on a dedicated UART lane with hardware flow control; label printer option; paper-out sense line
Scanning1D and 2D barcode scan engine on its own seat; QR, CCD, laser and imaging engines supported
Card and paymentNFC contactless, IC card, magnetic stripe, PSAM and SIM seats; fingerprint, face and PIN pad options
Wireless4G LTE with 5G option; WiFi dual-band; Bluetooth 5.0 and 5.4; GPS, BeiDou and GLONASS
Wired I/OUSB host and USB OTG, multiple USB ports, RS232, RS485, TTL, GPIO, I2C, SPI, PWM and ADC
Audio and hapticsSpeaker, microphone, headphone jack, vibration motor, voice prompt and voice broadcast
CameraMIPI CSI rear and front camera options; USB camera on request
PowerMains input for kiosk and countertop builds; 3.7V single-cell Li-Po with a 2S 7.4V option for portable builds; USB Type-C charge at 5V and 2A; battery management, fast charging and wireless charging on request
ReliabilityHardware watchdog, RTC real-time clock, scheduled power on and off, auto power-on, wide-temperature components
Upgrade pathsRemote OTA update; USB and TF card upgrade; network upgrade; A and B slot with rollback on custom builds
LanguageMulti-language interface, English standard, bidirectional script support on request, voice prompt and voice broadcast
Software servicesSDK development kit, BSP porting, driver adaptation, API development, system UI trimming, boot animation and pre-installed applications
Lifecycle10-year supply, 10-year BSP patches, 10-year component traceability

Payment and security stack: What the board has to carry before certification starts

The most expensive misunderstanding on this platform is the belief that certification is a software task. It is not. The kernel needs a security element seat, tamper sense routing, a signed boot chain and a power-fail-safe batch store, and all four are decided at schematic time. The matrix below is what a mobile payment product owner in Oceania should hand the certification house before the first pre-test.

Published configuration reference — confirm the exact model, revision and current documents.
LayerWhat it coversAndroidSBC custom build
Contact EMVEMV Level 1 and Level 2 kernel on the IC card pathKernel ported and the card controller pinned at design freeze
Contactless EMVNFC tap path and the reader antenna tuningAntenna tuned to the housing, gate profile under one second
PCIPCI PTS device scope and PCI DSS host scopeTamper sense lines routed and a zeroize path on tamper
PBOC and UnionPayDomestic debit and credit kernel for the China schemeKernel support with the PSAM seat wired
Scheme kernelsVisa, MasterCard, AMEX and the local schemeMulti-kernel build with per-scheme configuration
Hardware cryptoSecure encryption, national cryptography and hardware encryptionDiscrete security element plus TEE and trusted execution
Secure bootSigned chain from the bootloader to the kernelCustomer key burned at the factory
Key injectionPer-unit key material and provisioning stringPer-unit injection with an audit file per shipment
Offline storeFloor limit and batch store through a power lossPower-fail-safe partition sized to the acquirer policy
AuditPer-unit transaction and match logsPer-unit log partition, exportable for the acquirer

Read as a procurement rule: if your candidate vendor cannot tell you which of those ten lines are hardware and which are software, the certification will slip, and the slip will not be free.

Interface layout and I/O map: Twelve positions, and no spares

A payment terminal board is deliberately dense: one printer lane, one scan engine seat, one camera lane, one card controller group and one power path inside a housing that also has to hold a display, a roll of paper and often a battery. That is what keeps the bill of materials and the thermal envelope sane, and it is also why the lane allocation has to be agreed before the housing is cut. The map below is the standard allocation; the AS-RK3568-BGV-CUS re-spin can move any of it.

Published configuration reference — confirm the exact model, revision and current documents.
No.NameDefinitionNote for the custom build
1DisplayMIPI DSI panel, 5.5-inch to 8-inch, with LVDS, eDP and HDMI optionsPanel part number pinned at design freeze, cable qualified
2TouchCapacitive multi-touch on I2CCalibration profile written for the housing glass
3Printer58mm or 80mm thermal printer on UARTDedicated lane with hardware flow control, never shared
4Scan engine1D and 2D engine on its own seatPresentation-ahead wake and a 200ms first decode
5NFCContactless reader and antennaAntenna tuned to the housing, not to the bench
6CardIC card, magnetic stripe and PSAMSeats wired even when a market does not use them yet
7Cellular4G LTE module, 5G optionSIM and eSIM seats, antenna gain budgeted with the housing
8WiFi and BluetoothDual-band WiFi with Bluetooth 5.0 or 5.4Channel plan for the site, not for the lab
9Serial controlRS232 and RS485 for lockers, dispensers and gatesTermination and the baud plan agreed at schematic time
10USBUSB host and USB OTG, multiple portsCharge path and the peripheral lane allocated at schematic time
11PowerMains input, or a 3.7V cell with managementPrint inrush and radio bursts budgeted together
12ServiceRTC, watchdog, UBOOT burn key and test pointsCoin cell fitted, schedule written and test points on one fixture

Two positions on this map cause more field returns than the rest of the board combined: the printer lane and the power path. If the printer shares a lane with the scan engine, every print stalls a scan; and if the power input is carrying the display backlight, the print head and the radio at once without headroom, that decision has to be made at schematic time rather than at integration time.

Power, thermal and enclosure performance: The budget is the whole system

A payment terminal runs either from a mains rail inside a kiosk or from a single 3.7V lithium cell in a portable unit, with a 2S 7.4V option for larger print mechanisms. Unlike a desktop, there is often no second rail to fall back on, so the input, the charge path and the inrush profile are the system. The figures below are the specification limits, plus indicative bench measurements taken on the reference build at 25C for budget planning.

Published configuration reference — confirm the exact model, revision and current documents.
ItemSpecification or measurementNote
Mains input12V or 24V DC input on the kiosk buildSpecification limit, site dependent
Battery input3.7V nominal single-cell Li-PoSpecification limit, 2S 7.4V optional
Charge inputUSB Type-C at 5V and 2ASpecification limit
Idle, launcher resident, no transactionAbout 0.20AIndicative bench measurement
Scan burst with the engine awakeAbout 0.63AIndicative bench measurement
4G transmit with the display at full brightnessAbout 0.91AIndicative bench measurement
58mm print burst, head energisedAbout 1.92A for 400msIndicative bench measurement, the peak event
Charge time from empty to fullAbout 3.5 hoursIndicative bench measurement
Operating ambient range-10C to 50CSpecification limit
Storage ambient range-20C to 60CSpecification limit
Counter cable sag at 2ACommonly 4.4V to 4.7VField observation, resets at every print

Read as a system: the print burst is more than nine times the idle current, and it arrives at the exact moment the radio is also busy. The mobile payment product owner in Suva who budgets the input, the charge path, the print inrush and the radio bursts together never sees the random-reset failure mode.

Assembly and integration notes: Eight things that void a return

Every one of these is taken from the platform constraints and from field returns we have handled, and every one of them belongs on the incoming QC sheet before the housing is closed.

  1. Give the thermal printer its own UART lane. A printer driven from general-purpose pins turns print timing into a software problem, and the symptom is a jammed roll at the counter.
  2. Check the supply at the end of the counter cable, not at the adapter. A two-metre run commonly sags to between 4.4V and 4.7V, which is inside the reset window at every print burst. Measure under load.
  3. Decide the charge path and the peripheral lane at schematic time. If USB carries charge and data on one lane, there is no spare peripheral lane left on the board.
  4. Fit the RTC coin cell and write the schedule before shipment. Without a clock source the scheduled power-on reverts to a manual press, and the terminal never rejoins the host on time.
  5. Size the offline store for the real catalogue, not for the demo. The socket reads a 64GB card, but the image has to index the whole card, and a catalogue database grows faster than a product team expects.
  6. Tune the NFC antenna inside the final housing. A bench tune reads differently once the battery, the metal frame and the paper roll are sitting behind the antenna, and the tap time doubles.
  7. Match the scan window to the enclosure. A tinted window or a recessed engine changes the decode profile, and the presentation then reads only from certain angles.
  8. Never ship an OTA without a fallback slot. A single-slot update that fails mid-write turns a remote estate into a truck roll, which is the most expensive failure mode on this platform.

Application matrix: 8 customization scenarios for the AS-RK3568-BGV-CUS

The smart payment terminal platform is one carrier across eight different payment deployments. The matrix below shows the most common OEM/ODM customization angles a mobile payment product owner in Oceania walks through in the first scoping call.

Published configuration reference — confirm the exact model, revision and current documents.
ScenarioCatalog board limitAS-RK3568-BGV-CUS customization
Retail and supermarket countertopShared printer lane, 5.2 s tap-to-receiptDedicated printer UART, local authorization cache
Restaurant and self-ordering kiosks7.4 s to menu, one uplinkLocal menu cache, dual uplink plan
Banking and public service kiosksNo security element seat, shared imageDiscrete security element, per-unit key injection
Unattended vending, EV and parking3.6 s camera focus, no offline authoriseCapture-ahead focus, offline authorise mode
Handheld and portable paymentPrint head on GPIO, GPS lost on scanPrinter UART with flow control, isolated GPS rail
AI face payment and QR walletCPU inference at 3.1 s, one imagerNPU inference, dual imager plan
Smart retail and smart lockerScale and kernel on one USB laneDedicated scale lane, RS485 locker seat
Multi-scenario OEM/ODM familyThree carriers, two BSP trainsOne carrier, one BSP train, one MOQ

Frequently asked questions

Which platforms can you build on?
Answer: Rockchip RK3568 and RK3576 as the main tiers, RK3566 as the mid tier, and Allwinner A133 or A64 as the value tier. The RK3576 adds the NPU path that face match, age verification and AI product recognition need.

Can the printer and the scanner run at the same time?
Answer: Yes, on a custom carrier, because the 58mm or 80mm thermal printer gets its own UART lane with hardware flow control and the scan engine sits on a separate seat. On a catalog board the two usually share one lane and the print stalls the scan.

What power configuration do you ship?
Answer: A mains input on the kiosk and countertop builds, and a 3.7V single-cell Li-Po with a 2S 7.4V option on the portable builds, charged from USB Type-C at 5V and 2A. The print inrush, the radio bursts and the display backlight are budgeted together so a full shift runs on one charge.

What display sizes are available?
Answer: 5.5-inch, 6-inch, 7-inch and 8-inch panels on MIPI DSI at 1024x600, 1280x800 or 1920x1080, in portrait or landscape, with LVDS, eDP and HDMI output options and capacitive multi-touch at 5, 10 or 20 points with a calibration profile per housing.

How does the terminal behave when the network drops?
Answer: On a custom build the transaction goes into a power-fail-safe offline store that holds the ticket, the signature and the photo, and forwards everything on reconnect. On a catalog build the client usually drops the transaction, which is a lost sale rather than a delayed one.


Published by: Wanlin Manufacturing Group, AndroidSBC Export Division
Published on: September 30, 2026
Data sources: in-house factory testing + smart payment terminal platform specification + indicative bench measurements + certification files + partner case studies
Company address: Wanlin Group, Building B, Building 1, Beisida Medical Device Building, 28 Nantong Avenue, Baolong Community, Baolong Sub-district, Longgang District, Shenzhen, Guangdong, China
References: payment terminal platform specification + factory quality manual + third-party test reports + customer shipment records
Contact: Email: Androidsbc@163.com | Phone: +8613261677119 | Website: https://www.androidsbc.com

Application fit

Confirm the operating environment, workload, display, network and peripheral requirements.

Technical verification

Check the exact board revision, interfaces, firmware build and certification scope.

Commercial confirmation

Verify quantity, sample plan, lead time, warranty and delivery terms in writing.