HIBR Integrations — setup & operations

Connect HIBR to the banks, payment processors, e-commerce stores, logistics partners, government portals, and productivity tools your business already runs on. This is the operational reference for the 30+ native integrations plus the custom-build path via REST API and webhooks.

Integration categories at a glance

HIBR ships with native integrations across seven categories. Every integration is bi-directional where the upstream system permits it, and every sync is logged and reconcilable from the Integrations dashboard.

Connecting a bank feed

UAE bank-feed setup follows the same shape for every supported bank. The exact UI prompts vary per bank, but the steps are consistent.

1. Authorize in the bank's corporate portal. Log into your bank's corporate online banking (e.g., Emirates NBD businessONLINE, ADCB ProCash). Enable third-party statement access for HIBR. This is a one-time owner action.
2. Connect inside HIBR. Settings → Integrations → Banks → choose your bank → click Connect. You'll be redirected to the bank's OAuth or token-exchange flow. Approve the read-only scope (statements + balances; no payment authority).
3. Map accounts. Match each bank account to its corresponding GL ledger in HIBR. Multi-currency accounts auto-create per-currency sub-ledgers.
4. Set match rules (optional). HIBR's auto-match handles most transactions, but you can pin rules: e.g., "FTA reference 100000XXX → VAT Payable", "PRIDC → Petty Cash Reimbursement".
5. Wait for first sync. First sync usually completes within 30 minutes. Subsequent syncs run overnight (~02:00 UAE time). You can trigger a manual sync at any time.

Connecting payment processors

Payment processor setup uses OAuth (Stripe, Telr, Tap, Tabby) or API-key pairing (Network International, PayTabs, Ziina, Tamara). Either path takes under 5 minutes.

1. Settings → Integrations → Payments. Select the processor.
2. OAuth or API key. Log in to the processor (OAuth) or paste the publishable + secret keys from the processor's dashboard (API key flow). HIBR encrypts keys at rest with KMS envelope encryption.
3. Confirm webhook URL. HIBR auto-registers the webhook endpoint with the processor. You'll see a confirmation in the processor's webhook log.
4. Map fee + settlement GL. Processor fees flow to a dedicated expense account; net settlements credit the bank account where the processor deposits.
5. Test with a $1 transaction. Optional but recommended. The test transaction surfaces any account-mapping issues before live volume.

Connecting an e-commerce store

E-commerce platforms are app-store installs. HIBR is listed on the official app stores for Shopify, WooCommerce, Salla, Zid, Magento, and BigCommerce.

1. Install from the store's app marketplace. Approve HIBR's requested scopes (orders, products, inventory, customers, refunds).
2. Sync direction. Decide whether HIBR or your store is the source of truth for inventory. For most SMBs, HIBR (ERP) is the source — inventory updates from HIBR push to the store. For dropshippers, the store remains the source.
3. Channel-level GL mapping. Each store maps to its own revenue, COGS, and processor-fee accounts. Multi-store setups (e.g., a UAE Shopify + a KSA Salla) keep books cleanly separated.
4. Backfill historical orders. Choose how far back to import: 30 days / 90 days / 12 months / full history. Most beta users import 90 days.

FTA EmaraTax + e-invoicing

The FTA integration covers VAT 201, Corporate Tax CT-201, and PEPPOL PINT-AE e-invoicing per Cabinet Decision 28/2024. Setup is a one-time configuration; ongoing operation is automatic.

1. Settings → Tax → FTA EmaraTax. Enter your TRN (Tax Registration Number) and Corporate Tax Reference Number. HIBR validates against FTA's public registry.
2. FTA portal credentials (optional). For direct submission, enter your FTA portal credentials. HIBR uses these in read/submit mode only — never to modify your FTA account profile. Alternatively, skip this step and use the manual-upload export.
3. PEPPOL onboarding. If you're an in-scope taxable person under MD 243/2025, HIBR onboards your TRN to PEPPOL PINT-AE via an accredited service provider. Your customers and suppliers must also be PEPPOL-onboarded for full automation; otherwise HIBR generates PEPPOL-compliant XML for manual exchange.
4. Filing calendar. HIBR auto-detects your VAT period (monthly or quarterly) from FTA records and locks the filing dates per the SLA tier you're on. See the VAT & Tax Filing help article for the full filing workflow.

WhatsApp Business + comms integrations

The WhatsApp Agent (one of HIBR's 10 AI features) requires a WhatsApp Business API number — not a personal WhatsApp account.

1. Provision a WhatsApp Business API number. Through Meta directly, or through a BSP (Business Solution Provider) like Twilio, 360dialog, or MessageBird. HIBR is BSP-agnostic.
2. Settings → Integrations → WhatsApp Business. Paste your phone-number ID and access token.
3. Approve message templates. Outbound proactive messages (invoice reminders, payment confirmations, low-stock alerts) require Meta-approved templates. HIBR ships with 12 pre-approved Arabic + English templates. Custom templates take 24-48h for Meta approval.
4. Train the agent on your data. The WhatsApp Agent learns from your invoice, customer, and inventory data. PDPL redaction (TRN, EID, IBAN, names) runs pre-inference. Owner can review and edit the agent's allowed-actions list at any time.

Sync schedules & rate limits

When a sync fails

Integrations fail. Banks rotate certificates. Processors rate-limit. Stores time out. HIBR's integration monitor handles failure with three layers:

1. Automatic retry. First failure → retry in 60 seconds. Second failure → exponential backoff (5 min, 30 min, 2h). Total of 5 retry attempts before the integration is marked "degraded".
2. Owner alert. After 2 consecutive failures, the owner receives an in-app alert plus an optional WhatsApp/email notification per their notification preferences.
3. Engineering escalation. For SLA-covered integrations (FTA, WPS agent bank), Pro users get a 15-minute engineering acknowledgement; Enterprise users get a 1-hour resolution target. See the SLA page for the full breakdown.

Building your own integration

The REST API and webhook system at HIBR are first-class — not an afterthought. Every entity that exists in the UI exists as an API resource, and 40+ event types fan out to your webhook endpoints in real time.

• Authentication. OAuth 2.0 for user-context apps; scoped API keys for server-to-server. See /developers/api/ for the auth flow.
• Rate limits. Generous defaults (600 requests/minute per workspace), with Enterprise tier raising limits on request. 429 responses include Retry-After headers.
• Webhooks. Subscribe to events like invoice.created, payment.succeeded, inventory.low_stock, payroll.run_completed. Full event catalogue at /developers/webhooks/.
• Sandbox. Every workspace gets a free sandbox at sandbox.hibr.ai with synthetic data — test your integration before going live.
• SDKs. Official SDKs for Python, Node.js, PHP, and Go. Community SDKs for Ruby and .NET in the developer portal.

Common troubleshooting

Bank-feed transactions stopped arriving

Most common cause: the bank's corporate-portal access expired (most UAE banks rotate third-party access every 90-180 days). Fix: re-authorize in the bank's portal, then click "Reconnect" in HIBR's integration row. No data loss — HIBR replays missing transactions on reconnection.

E-commerce orders are syncing but not creating invoices

Check the channel's GL mapping under Settings → Integrations → [your store] → Mapping. A missing revenue or tax-code mapping causes orders to land in a holding queue. The holding queue is visible on the Integrations dashboard with a "needs mapping" badge.

WhatsApp template rejected by Meta

Meta's most common rejection reasons: promotional content in a "Utility" template, missing variable placeholders, or formatting issues. HIBR's template editor flags these before submission, but Meta's automated reviewer is occasionally inconsistent — resubmit with clearer wording or contact HIBR support to escalate through our BSP partner.

Stripe webhook signature mismatch

Almost always caused by the webhook secret being out of date after a Stripe key rotation. Settings → Integrations → Stripe → "Refresh webhook secret" pulls the current secret from your Stripe account automatically.

Tier availability

Related help articles & resources

• For developers: Developer portal, API reference, Webhooks reference
• Tax workflow: VAT & Tax Filing help
• Payroll workflow: Payroll & WPS help
• Migration: Migration help (your prior-system data lands in HIBR before integrations come live)
• AI features: AI Features help
• SLA + escalation: Service Level Agreement