API and schema changes
BIR EIS payload updates are centralized in EIS Bridge, so vendor adapters stay stable as regulations evolve.
Recommended path: EIS Bridge Vendor Partner Program
Integrate once with one Vendor API and one Standard Sale Object. EIS Bridge handles mapping, signing, and async transmission so checkout never blocks on BIR calls.
Request partner access Open Developer PortalWhy partner with EIS Bridge
POS and ERP vendors use a thin adapter layer while the shared transmission core handles BIR-specific complexity.
Signing and certificate workflows
Per-merchant signing and transmission flows are managed in the bridge with auditable status tracking.
Checkout performance
POST /transactions returns immediate acceptance status while transmission and retries run asynchronously.
Rollout at scale
Vendor tenancy and per-merchant activation enable phased rollout across multi-branch customer fleets.
Editions and pricing overview
| Edition / Component | Audience | Typical pricing (PHP) | Notes |
|---|---|---|---|
| EIS Bridge Vendor Edition | POS and ERP companies | Core: ₱180,000 - ₱350,000 | Recommended entry path for partner-led rollout. |
| Per-merchant activation | Vendor rollout base | ₱25,000 - ₱35,000 each merchant | Applied as each merchant completes go-live requirements. |
| EIS Bridge Merchant Edition | Enterprise retailers | Per agreement | Direct licensing for enterprise compliance programs. |
| EIS Bridge SaaS | Small merchants | Subscription, per agreement | Managed cloud compliance through vendor channel or direct. |
What is included in Vendor Edition
Vendor API keys
Unique keys per partner account with controlled issuance and rotation through onboarding workflows.
Standard Sale Object
Open JSON-based contract, validation schema, and integration resources for predictable adapter development.
Async submission model
Immediate queue-based acceptance plus status checks and webhook notifications for BIR acknowledgments.
Multi-merchant tenancy
Structure merchants, branches, and devices under one vendor account to support staged deployments.
Certification support
Sandbox onboarding, QA suite preparation, and production key enablement after certification sign-off.
Onboarding path
1) Register
Request Vendor Edition access and receive sandbox credentials plus onboarding checklist.
2) Map and submit
Map POS data to the Standard Sale Object and submit transactions to /v1/transactions.
3) Confirm and certify
Use status polling or webhooks, then complete certification with the QA suite and playbook.
4) Activate merchants
Enable production access as each merchant completes EIS CERT and Permit to Transmit requirements.
Ready to launch your vendor integration?
Start with the recommended Vendor Partner Program path and request onboarding today.
Request partner accessNeed the full markdown reference? Download details.