Integrations
Connect the tools merchants already run
Connect payments, marketing channels, email, and business services while Bizmerce keeps commerce data, permissions, and operational rules under control.
External providers extend Bizmerce; they do not become the system of record.
This page lists integrations and provider capabilities currently supported by Bizmerce. Planned integrations are not presented as available.
Bizmerce
Integration layer
Overview
Integration categories
Payments
Connect merchant-configured providers for shopper checkout.
Marketing
Connect advertising channels to Growth Hub.
Authentication
Support provider-based merchant sign-in where implemented.
Email
Deliver transactional account and operational messages.
Domains
Connect verified custom storefront domains.
Platform services
Use managed infrastructure that supports Bizmerce operations.
Supported integrations
What you can connect today
Each item reflects a real product surface — with status and requirements stated plainly.
Commerce payments
Merchant-configuredPayments
Merchant-configured providers process shopper checkout. Adapters include SSLCommerz, Stripe, and bKash where the store enables them.
Requirement: Store payment configuration · verified provider confirmation before payment success
Learn moreMeta
Provider-dependentMarketing
Connect a merchant advertising account for Growth Hub campaigns where permissions and plan entitlements allow.
Requirement: Provider authorization · Growth entitlement · Meta scopes and account approval
Learn moreGoogle Ads
Provider-dependentMarketing
Connect Google Ads for supported campaign work. YouTube Ads are a Google Ads channel, not a separate provider.
Requirement: Provider authorization · Growth entitlement · Google Ads account access
Learn moreTikTok Ads
Provider-dependentMarketing
Connect TikTok advertising where the merchant has granted access and the plan supports Growth connections.
Requirement: Provider authorization · Growth entitlement · TikTok Ads access
Learn moreGoogle sign-in
AvailableAuthentication
Optional Google authentication for merchants. Provider tokens are verified server-side before a Bizmerce session is created.
Requirement: Configured Google OAuth · backend token verification
Learn moreFacebook sign-in
AvailableAuthentication
Optional Facebook authentication alongside Google and email for merchants.
Requirement: Configured Facebook OAuth · backend token verification
Learn moreTransactional email
Platform-managedEmail
Verification, invitations, and operational notifications for merchant and platform workflows.
Requirement: Promotional marketing email remains separate from transactional delivery
Custom domains
Plan-gatedDomains
Connect a verified custom domain to a storefront when the merchant plan includes the required entitlement.
Requirement: DNS ownership verification · custom domain entitlement
Learn moreSaaS billing
Platform-managedPlatform
Organization subscription billing to Bizmerce, kept separate from shopper commerce payments.
Requirement: Organization subscription flow · not used for store checkout
Learn more
Capability matrix
What Bizmerce supports — and where it stops
Requirements and provider limits stay visible so evaluators are not surprised later.
Payments
Commerce checkout
What Bizmerce supports
Merchant-configured payment providers handle shopper checkout. Bizmerce updates order and payment state only after verified provider confirmation. Provider signatures are verified where supported, and duplicate events are handled safely.
Requirements / limits
Browser redirects are not proof of payment. Shopper payment flows remain separate from Bizmerce subscription billing. Bizmerce does not claim PCI DSS certification.
Marketing
Meta
What Bizmerce supports
Connect a merchant advertising account for Growth Hub campaign workflows where permissions and plan entitlements allow.
Requirements / limits
Actions depend on Meta account type, granted scopes, plan entitlement, and provider approval.
Marketing
Google Ads
What Bizmerce supports
Connect Google Ads for supported campaign work, including YouTube as a Google Ads channel.
Requirements / limits
Provider metrics stay labeled separately from Bizmerce first-party commerce data.
Marketing
TikTok Ads
What Bizmerce supports
Connect TikTok advertising where the merchant has granted access and the plan supports Growth connections.
Requirements / limits
Unsupported provider actions fail clearly rather than claiming full parity.
Authentication
Google & Facebook
What Bizmerce supports
Optional provider sign-in for merchants. Tokens are verified on the server before a Bizmerce session is created.
Requirements / limits
Provider login does not grant Organization privilege without membership.
Email
Transactional email
What Bizmerce supports
Account verification, invitations, and operational notifications for platform and merchant workflows.
Requirements / limits
Promotional marketing email and transactional email remain separate.
Domains
Custom domains
What Bizmerce supports
Point a verified custom domain at your storefront when the plan includes the custom domain entitlement.
Requirements / limits
Domain ownership is verified before the hostname becomes active.
Ownership
Who controls each connection
Merchant-connected integrations
The merchant authorizes and configures these connections.
- Commerce payments
- Meta
- Google Ads
- TikTok Ads
- Custom domains
Bizmerce-managed platform services
Bizmerce configures these services to support platform operations.
- Google sign-in
- Facebook sign-in
- Transactional email
- SaaS billing
Connection lifecycle
- Merchant
- Connect provider
- Provider authorization
- Permission & scope check
- Plan entitlement check
- Bizmerce adapter
- Provider API
- Verified response / event
- Bizmerce state
Guardrails
Growth stays behind policy
Connecting an advertising account does not automatically enable autonomous spending. Automation actions remain subject to merchant-defined controls.
- Plan entitlement
- Merchant-selected automation mode
- Channel permissions
- Budget policy
- Inventory checks
- Kill switch
- Revalidation before action
Provider boundary
External SDKs extend Bizmerce but do not determine authoritative commerce state.
Access & entitlement
Plans, permissions, and merchant configuration determine which integrations can be used.
Revalidation before action
Bizmerce rechecks relevant state before external actions are executed.