Documentation

Q: The Rapyd app has two components, does it matter which one is loaded first into a terminal?

A: Yes. It is recommended to install the Rapyd App first and then the Rapyd Core. The Core contains parameters and triggers a terminal restart after installation, so it should be installed last.

Q: What is the planned Rapyd Core and Rapyd App release schedule?

A: A new version is typically released every 6-8 weeks.

Q: When a new version is released, is it enough to push the latest version, or are additional actions required (e.g., merchant restart)? Will configurations such as multi-merchant setup or custom themes remain unchanged?

A: All new versions are backward compatible with existing parameters, so you only need to push the latest version. The terminal will automatically restart when the Core is updated. It is recommended to update the front-end app at the same time. Existing configurations (e.g., multi-merchant, custom themes) remain unchanged.

Q: In a multi-merchant setup, can a new merchant be added later, or only during the initial configuration?

A: Both are possible. You can push the Core app again and update the parameters file to add or remove merchants.

Q: Can refunds be made to any card, or only to the original card used for the transaction?

A: Refunds can be made to any card and for any amount. Limits (e.g., maximum refund amount or maximum refunds within 24 hours) can be configured in the terminal parameters.

Q: When integrating a third-party app with the Rapyd Core app, who manages the card interface screens and the actual payment processing?

A: The third-party app sends commands to the Rapyd Core app via app-to-app communication. Once the transaction proceeds to card reading, control moves to the Rapyd Core app. The Rapyd Core app manages card reading, payload encryption, SSL communication with Rapyd backend, and printing. Rapyd provides documentation, a demo app, and source code examples. All Rapyd front-end apps (Standalone, CloudLink, LocalLink) use the same Rapyd Core interface.

Q: Can an ISV send a product receipt to the Rapyd app for printing on the terminal?

A: Yes. Your app can send a print command to the Core app. This feature was added to support LocalLink and CloudLink integrations. The print format follows the same layout as Core-generated receipts.

Q: Is it possible to process refunds directly on the terminal and protect the function with a PIN?

A: Yes. All refunds are processed online and require chip-and-PIN, similar to sales transactions.

Q: Are unreferenced refunds possible (enter amount, tap card, process refund without linked sale)?

A: Yes. Refunds are not linked to a previous sale and can be processed on any card, even if no original transaction exists on the terminal.

Q: Do you support daily closing (“X/Z report”) and resetting totals?

A: Yes. You can run an “End of Day” report, which resets totals. Running it is not required for clearing, as transactions are settled automatically, but it is recommended for reconciliation.

Q: Are MOTO (Mail Order / Telephone Order) payments supported?

A: Yes. Note: CVV2 is optional when processing a MOTO transaction

Q: Can receipts be reprinted?

A: Yes. You can reprint any transaction from the last 1,000 transactions stored on the terminal.

Q: Can certain card brands be blocked?

A: Yes. For example, AMEX acceptance can be disabled.

Q: Are digital merchant receipts supported?

A: Yes. Email receipts are supported for both merchants and cardholders. End-of-Day reports can also be sent via email.

Q: Is SIM card functionality supported?

A: Yes, this is part of Android and is not a problem.

Q: Is WLAN (Wi-Fi) supported?

A: Yes. All terminal hardware includes Wi-Fi capability.

Q: Can terminal settings be configured or updated via API?

A: Yes. The MAX Store provides a comprehensive API for terminal management. Manual configuration via MAX Store is also possible.

Q: Can customer receipt printing be enabled or disabled?

A: Yes. This can be configured in terminal settings. If paper runs out, the receipt will be displayed on-screen instead.

Q: Can receipt language be customized?

A: Yes. The merchant can select the terminal language in settings, which updates both screen prompts and receipts. We can also support additional language adjustments if needed.

Q: Are tip suggestions (e.g., 10%, 15%) supported directly on the device?

A: Yes. Three customizable tip buttons are available.

Q: Can customers enter an email address directly on the terminal for receipt delivery? Is QR-code receipt delivery supported?

A: Email receipts are supported for both merchants and cardholders. QR code receipt delivery is not currently available but is on the product backlog.

Q: Is it possible to install additional apps on the terminal?

A: Yes. Many partners integrate with the Rapyd Core app. We provide documentation and a test app with source code to support integrations.

Q: Does the terminal support OPI (Open Payment Initiative) or ZVT (ZahlungsVerkehrsTerminal)?

A: No. However, our CloudLink and LocalLink integrations are straightforward, and we provide documentation, examples, and direct Slack access to our development team for integrators.