Wrapper Parity Matrix
This page answers a practical question: which wrapper exposes which EPAS function today?
Yes means the wrapper exposes the feature as part of its public API. Partial means the concept exists but is exposed differently or not yet with the same helper surface.
Session and Connection
| Feature | .NET | Java | Swift |
|---|
| Network connect | Yes | Yes | Yes |
| Disconnect | Yes | Yes | Yes |
| Login | Yes | Yes | Yes |
| Logout | Yes | Yes | Yes |
| Status snapshot | Via handlers | Via handlers | Yes |
| Explicit close helper | Yes | Yes | Yes |
| Force reconnect on connect | Yes | Yes | Yes |
Payments and Transaction Control
| Feature | .NET | Java | Swift |
|---|
| Purchase by amount | Yes | Yes | Yes |
| Purchase by amounts model | Yes | Yes | Yes |
| Purchase by full request model | Yes | Yes | Yes |
| Alternative payment method purchase | Yes | Yes | Yes |
| Purchase before amount | Yes | Yes | Yes |
| Send purchase amounts | Yes | Yes | Yes |
| Refund by amount | Yes | Yes | Yes |
| Refund by full request model | Yes | Yes | Yes |
| Alternative method refund helper | Yes | Partial | Yes |
| Cash advance | Yes | Yes | Yes |
| Reversal | Yes | Yes | Yes |
| Last transaction | Yes | Yes | Yes |
| Abort transaction | Yes | Yes | Yes |
Reader, Admin, and Diagnostics
| Feature | .NET | Java | Swift |
|---|
| Enable or disable readers | Yes | Yes | Yes |
| Administrative operation request | Yes | Yes | Yes |
Admin operation ModeSwitch | No | Yes | Yes |
Admin operation StartSwish | No | Yes | Yes |
| Raw XML send | Yes | Yes | Yes |
| Raw XML send with raw terminal result | No | Yes | Yes |
| Structured terminal print request | Yes | Yes | Yes |
| Customer inquiry request | Yes | Yes | Yes |
| Customer inquiry abort | Yes | Yes | Yes |
Callback Surface
| Feature | .NET | Java | Swift |
|---|
| Display callback | Yes | Yes | Yes |
| Receipt callback | Yes | Yes | Yes |
| Report callback | Yes | Yes | Yes |
| Signature callback | Yes | Yes | Yes |
| Force fallback callback | Yes | Yes | Yes |
| Voice referral callback | Yes | Yes | Yes |
| Payment code callback | Yes | Yes | Yes |
| VAT callback | Yes | Yes | Yes |
| Loyalty callback | Yes | Yes | Yes |
| DCC original transaction callback | Yes | Yes | Yes |
| Parameter download callback | Yes | Yes | Yes |
| Log callback | Yes | Yes | Yes |
| Link status callback | Yes | Yes | Yes |
| Busy status callback | Yes | Yes | Yes |
| Card action callback | Yes | Yes | Yes |
| Card accepted callback | Yes | Yes | Yes |
| Raw message callback | Yes | Yes | Yes |
| Callback enablement toggles | No | Yes | Yes |
Logging and Support Helpers
| Feature | .NET | Java | Swift |
|---|
| Storage directory configuration | Yes | Yes | Yes |
| Start new log file | Yes | Yes | Yes |
| Stop log file temporarily | Yes | Yes | Yes |
| Clean all log files | Yes | Yes | Yes |
| Log-part enable or disable controls | No | Yes | Yes |
| Built-in XML debug logging toggle | Yes | Yes | Yes |
ApiResult.ErrorResponseTimeout | No | Yes | Yes |
Interpretation Notes
- The Swift wrapper now covers the main transactional EPAS surface well.
- The largest remaining parity gap is now in deep model completeness and a few helper overloads rather than core purchase, refund, callback, or logging flows.
- The largest remaining Apple parity gaps are now mainly lower-level support conveniences rather than the main terminal, raw XML, or logging flows.
