EIS Bridge™ — trademark application pending · IPOPHL Class 42 · Ref EFPH202600003850268
Integration Testing
Validate your POS integration against the QA Suite v1.0 before production certification. Run all tests against Sandbox first. See the Certification Playbook for EIS CERT, PTT, and go-live steps.
Test case summary
Basic Connectivity
| ID | Name | Pass criteria |
|---|
| TC-01 | Valid API Key | HTTP 200/201; no auth errors |
| TC-02 | Invalid API Key | HTTP 401; error: unauthorized |
Single Transaction
| ID | Name | Pass criteria |
|---|
| TC-10 | Minimum Required Fields | status: accepted; bridge_transaction_id returned |
| TC-11 | Full Sale Object | Accepted; optional fields preserved |
| TC-12 | Multiple Items | All line items processed; totals align |
| TC-13 | Different Payment Methods | CASH, CARD, E-WALLET, SPLIT each accepted |
Validation & Error Handling
| ID | Name | Pass criteria |
|---|
| TC-20 | Missing Required Field | HTTP 400; validation_error; fields array |
| TC-21 | Invalid Date Format | HTTP 400; date format validation error |
| TC-22 | Negative Quantity | Rejected; validation error on qty |
| TC-23 | Zero or Negative Price | Rejected; validation error on unit_price |
| TC-24 | Invalid Merchant/Branch Code | HTTP 403; merchant not found |
Duplicate Handling
| ID | Name | Pass criteria |
|---|
| TC-30 | Same transaction_id sent twice | status: duplicate; same bridge_transaction_id |
| TC-31 | Same ID, different data | HTTP 409; transaction_conflict |
Batch Submission
| ID | Name | Pass criteria |
|---|
| TC-40 | Valid Batch | All transactions accepted; summary counts correct |
| TC-41 | Batch with 1 invalid transaction | Valid items queued; invalid flagged in results |
| TC-42 | Large Batch (100–500) | No timeout; all valid items queued |
Status Retrieval
| ID | Name | Pass criteria |
|---|
| TC-50 | Query valid bridge_transaction_id | Returns status, eis_status, logs |
| TC-51 | Query invalid ID | HTTP 404 |
Webhooks
| ID | Name | Pass criteria |
|---|
| TC-60 | Configure Webhook | HTTP 200; URL and secret saved |
| TC-61 | Receive EIS acknowledgment webhook | Payload with transaction.eis_acknowledged |
| TC-62 | Invalid Webhook URL | HTTP 400; validation error |
| TC-63 | Signature Verification | HMAC-SHA256 matches signature |
Compliance & Edge Cases
| ID | Name | Pass criteria |
|---|
| TC-70 | Void Transaction | Void accepted; linked to original |
| TC-71 | Return/Refund | Return accepted; reference preserved |
| TC-72 | Offline POS (Delayed Transmission) | Accepted within T+3 window |
| TC-73 | High Volume Spike | 1,000 txns in 5 min; all queued |
Security
| ID | Name | Pass criteria |
|---|
| TC-80 | Missing Authorization Header | HTTP 401 |
| TC-81 | Tampered Payload | Rejected; no partial processing |
| TC-82 | SQL/Script Injection Attempt | Sanitized or rejected safely |
Full QA test suite (v1.0) →
Production certification
Vendor must pass all integration test areas before production certification:
- Single transaction submission (TC-10, TC-11, TC-12, TC-13)
- Batch submission (TC-40, TC-41, TC-42)
- Status retrieval (TC-50, TC-51)
- Duplicate handling (TC-30, TC-31)
- Error handling (TC-20 through TC-24)
- Webhook acknowledgment (TC-60 through TC-63)
- Offline/T+3 scenario (TC-72)
- High-volume test (TC-73)
- Refund/Void handling (TC-70, TC-71)
- Security tests (TC-80 through TC-82)
Once all items pass, your vendor account is certified for EIS Bridge Production.
Sandbox vs Production checklist
Sandbox
- Base URL:
https://sandbox.eisbridge.com/v1 (provisioned on request)
- Sandbox API key from vendor onboarding
- Test merchant/branch/device codes assigned
- All QA test cases executed and documented
- Webhook endpoint reachable (HTTPS recommended)
- Error handling verified (400, 401, 403, 409)
- Duplicate and idempotency behavior confirmed
Production
- Base URL:
https://api.eisbridge.com/v1
- Production API key issued after certification
- Live merchant/branch/device codes configured per client
- Certification sign-off from EIS Bridge
- Production webhook URL registered
- Monitoring and retry logic in place
- Support contact and escalation path documented