Sample Apps

Last updated: 2026-05-19

Sample Apps

The sample applications exist to help integrators validate terminal connectivity, login, transaction flows, callbacks, receipts, and diagnostics without first building a complete ECR integration.

For most partner-facing documentation, it is usually enough to provide:

  • a short explanation of what each sample demonstrates
  • where the sample source code can be obtained
  • which wrapper or platform the sample belongs to

Detailed class-by-class sample documentation is usually more useful as internal support material than as top-level public navigation.

In this portal, the deep Java sample pages can remain in the content tree as support or agent material without being shown in the normal EPAS navigation.

Available Samples

SamplePurposeSource location in repository
.NET Sample ECRWindows-oriented sample for validating the .NET wrapper and terminal flows.SampleECR/
Java Sample ECRJava or JavaFX-oriented sample for validating the Java wrapper and terminal flows.java/sampleECR/
Apple Sample ECRmacOS sample app for validating the Swift wrapper, callbacks, XML trace, receipts, and terminal display mirroring.apple/Sources/AppleSampleECR/

Recommended Partner Delivery

For partner-facing delivery, the cleanest pattern is:

  1. publish the sample source packages or repositories through the normal release channel
  2. keep this page as the single public entry point
  3. avoid exposing deep implementation pages unless there is a specific support need

If partners need the fuller wrapper deliveries, send them to Library Downloads.

Why the Samples Exist

The sample apps are useful because they:

  • verify wrapper parity during development
  • expose terminal callbacks and receipts without a full POS implementation
  • provide a support and troubleshooting baseline
  • demonstrate UI patterns for prompts such as signature, VAT, voice referral, and DCC checks

Internal Note

If deeper sample documentation is still useful for support tooling or an assistant agent, those pages can remain in the repository but be hidden from the main navigation.