Integrations: everything your store plugs into

LokZon connects to the couriers, gateways, wallets and ad tools merchants in Bangladesh already use. Below is every connection that works today, what each one needs before it will switch on, and where in your dashboard to set it up.

Integrations

Resource snapshot

Courier partners
4
Ways to get paid
6
Marketing & SEO tools
6

Delivery

Courier partners that update your orders by themselves

Connect a courier once and parcel booking, tracking and parcel counts run from the order screen. Every partner verifies your credentials before it goes live, so a typo fails in settings instead of on a customer's order.

RedX

Nationwide parcel booking and live delivery status

LiveSandbox + production

Book a parcel from any paid order and RedX status updates flow back to the order timeline, so support answers “where is my order” without opening another tab.

What it does

  • Create parcels from an order in one click
  • Track pickup and delivery status per consignment
  • See booked and delivered parcel counts per connected account

Have these ready

  • RedX API key
  • Pickup store chosen in RedX

Pathao Courier

Same-city and nationwide delivery through Pathao

LiveSandbox + production

Pathao issues OAuth-style credentials per merchant account; paste them once and Lokzon keeps the token fresh while you book and track parcels from the order view.

What it does

  • Book city and inter-city parcels after packing
  • Read live status back onto the order
  • Choose sandbox or production when you connect

Have these ready

  • Client ID and secret
  • Merchant username and password

Steadfast

Express courier with webhook-fast status updates

LiveSandbox + production

Built for merchants shipping at volume: Steadfast returns consignment ids immediately, and delivery or return events arrive without refreshing the dashboard.

What it does

  • Bulk-friendly parcel creation from the orders list
  • Automatic delivery and return status sync
  • Parcel totals per connected account

Have these ready

  • API key
  • Secret key

CarryBee

Multi-hub tracking that lands on the order in real time

LiveSandbox + production

Built for routes that pass through more than one hub: each status change arrives as a signed webhook, so the order timeline is current without anyone refreshing it.

What it does

  • Create shipments and read tracking events
  • Receive status webhooks instead of polling
  • Keep an audit trail of each status change

Have these ready

  • Client ID and secret
  • Approved merchant account

Every partner carries its own sandbox and production base URL, so the address you test against is never the one your customers hit. Status changes arrive as signed webhooks rather than polls, and the parcel counts on each card come from your connected account, not an estimate. Bulk dispatch is available on plans that include it.

Payments

Every way your customers already pay

Three verified payment gateways, direct mobile-financial-service accounts, the Lokzon Wallet and cash on delivery with per-zone advance rules. Run a gateway in sandbox first, then switch the same connection to production.

Payment gateways

Your own merchant accounts, verified against the provider before they can be enabled.

AamarPay

Cards and mobile banking on one hosted checkout

LiveSandbox + production

One hosted checkout for cards and mobile banking, so you are not negotiating a separate merchant account for every instrument. Sandbox uses the shared test store ID aamarpaytest.

What it does

  • Cards, mobile financial services and net banking at checkout
  • Sandbox and production stores on the same connection
  • Credentials verified before the gateway can be enabled

Have these ready

  • Store ID
  • Signature key
  • Approved AamarPay merchant account

bKash Merchant API

Direct bKash payments into your own merchant wallet

LiveSandbox + production

Uses bKash's own merchant API rather than an aggregator, so payment is confirmed against bKash directly and settles into the merchant account you already own.

What it does

  • Create and confirm payments against bKash directly
  • Switch between sandbox and production per connection
  • Show the connected app key so you know which account is live

Have these ready

  • App key and app secret
  • Merchant username and password
  • Live bKash merchant account

SSLCommerz

Cards, internet banking and wallets from one aggregator

LiveSandbox + production

An established Bangladeshi payment aggregator. Point it at your own store ID and every card, bank and wallet it supports appears as a single checkout option.

What it does

  • Visa, Mastercard, Amex and local bank cards
  • Internet banking and aggregator-supported wallets
  • Sandbox store “testbox” for end-to-end test orders

Have these ready

  • Store ID
  • Store password
  • Approved SSLCommerz merchant account

Built-in methods

Available on every store, with no third-party approval to wait for.

Cash on Delivery

On by default, with per-zone advance rules

LiveBuilt in

COD is the default method on every store, because a checkout with no way to pay is a lost order. Tighten it per delivery zone instead of switching it off.

What it does

  • Collect nothing, the delivery charge only, a percentage, a fixed amount or the full total before dispatch
  • Apply different rules to different delivery zones
  • Cap the rule with a minimum and maximum order value

Have these ready

  • Delivery zones defined in Manage Shop

Self MFS accounts

Take bKash, Nagad, Rocket and Upay before you have a gateway

LiveManual verification

Add the mobile wallet numbers you already collect money into. The customer sends the amount, then submits the transaction ID (and optionally a screenshot) for you to approve.

What it does

  • One or many accounts: bKash, Nagad, Rocket, Upay or a custom wallet
  • Mark each account personal, merchant or agent
  • Transaction ID and screenshot captured on the order for reconciliation

Have these ready

  • A receiving mobile wallet number
  • Account type

Lokzon Wallet

Platform checkout for customers holding a Lokzon balance

LivePlan dependent

Customers pay from their Lokzon balance without leaving checkout. The wallet has to be activated for your store before the switch unlocks.

What it does

  • Pay from the Lokzon balance without leaving checkout
  • Activation handled from your finance settings
  • Available on plans that include the wallet

Have these ready

  • Activated Lokzon Wallet
  • A plan with wallet checkout

What customers can pay with

Every instrument, mapped to the thing that actually has to be configured.

  • bKash

    Through
    bKash Merchant API, or AamarPay / SSLCommerz
    You need
    bKash merchant credentials, or gateway store ID
  • Nagad

    Through
    Self MFS account, or an aggregator's hosted page
    You need
    A receiving Nagad number, or gateway store ID
  • Rocket

    Through
    Self MFS account, or an aggregator's hosted page
    You need
    A receiving Rocket number, or gateway store ID
  • Upay

    Through
    Self MFS account, or an aggregator's hosted page
    You need
    A receiving Upay number, or gateway store ID
  • Visa, Mastercard, Amex

    Through
    AamarPay or SSLCommerz
    You need
    Store ID and signature or store password
  • Internet banking

    Through
    AamarPay or SSLCommerz
    You need
    The same gateway connection
  • Lokzon Wallet balance

    Through
    Lokzon Wallet checkout
    You need
    Activated wallet on an eligible plan
  • Cash on delivery

    Through
    Built into every store
    You need
    Delivery zones, plus an online method for advances

Sandbox and production are stored separately

Every gateway and courier keeps its own credentials per environment, so a test key can never reach a live order. Providers issue test store IDs for exactly this: testbox at SSLCommerz, aamarpaytest at AamarPay. Confirm an end-to-end order in sandbox, then add production credentials and flip the switch.

Marketing & SEO

Measure the traffic you pay for, and get found for free

Ad pixels and their server-side counterparts, Google Analytics, Tag Manager, Search Console and machine-readable catalog feeds. Each tool connects with an ID or one Google sign-in, no developer required.

Meta Pixel & Conversions API

Facebook and Instagram ad events that survive ad blockers

Live

The browser pixel and server-side Conversions API fire together and deduplicate, so purchase events still arrive when a customer blocks scripts.

What it does

  • View, add-to-cart, checkout and purchase events
  • Server-side events with automatic deduplication
  • Product catalog feed for Meta Commerce Manager

Have these ready

  • Meta Pixel ID
  • Optional Conversions API token

TikTok Pixel & Events API

TikTok ad measurement from the same storefront events

Live

Reuses the storefront event stream, so you add a pixel ID instead of tagging every template by hand.

What it does

  • Pixel and Events API from one connection
  • Product views, carts and completed purchases
  • Test event codes for validating before you spend

Have these ready

  • TikTok Pixel ID
  • Optional Events API token

Google Analytics 4

Traffic, product views and revenue in GA4

Live

Loads on public storefront pages only, never in the dashboard, so merchant sessions do not pollute acquisition reports.

What it does

  • Page views, traffic sources and product engagement
  • E-commerce purchase events with order value
  • Enable or pause measurement without removing the tag

Have these ready

  • GA4 measurement ID

Google Tag Manager

Your own GTM container on every storefront page

LivePlan dependent

For teams that already run tags in GTM: the container loads on public pages and each store event is pushed to the dataLayer for your triggers.

What it does

  • Load a container ID on public storefront pages
  • Push every store event to the dataLayer
  • Keep tag changes out of your theme

Have these ready

  • GTM container ID
  • A plan that includes Tag Manager

Google Search Console

Verified ownership and indexed pages, without pasting tags

Live

One Google sign-in verifies the domain and submits your sitemap. If your team prefers manual control, the verification meta tag path is still there.

What it does

  • One-click OAuth verification for subdomains and custom domains
  • Sitemap submission with the correct live host
  • Manual HTML tag option when OAuth is not allowed

Have these ready

  • Google account with Search Console access

SEO & product catalog feeds

Sitemap, robots and a Facebook feed that stay current

LiveAutomatic

Generated from your live catalog, so a new product is discoverable the moment it is published instead of after a manual export.

What it does

  • sitemap.xml generated from your live products and pages
  • robots.txt served for your storefront, not shared with the platform
  • facebook-feed.xml for scheduled catalog syncs

Have these ready

  • A published storefront

Mailchimp

Email campaigns from your customer list

Coming soon

Audience sync and campaign tooling are on the roadmap, not shipped. The row stays visible so you can plan around it instead of assuming it exists.

What it does

  • Planned: audience sync from your customers

Pixels and analytics load on public storefront pages only, never inside the dashboard, so your own team's sessions do not end up in your acquisition reports.

Setup

Three steps from credentials to a live connection

No developer, and no app review on our side. If you can copy a key from your provider's portal, you can complete any connection on this page.

  1. 01

    Open the right settings page

    Couriers and marketing tools live in Manage Shop → Integrations. Payment gateways live in Finance → Payment Gateways. Both are one click from the dashboard sidebar.

  2. 02

    Paste your own credentials

    Lokzon connects to accounts you already own. Credentials are encrypted at rest, and the API only ever returns a masked store or app key, never the secret.

  3. 03

    Verify, then go live

    Test in sandbox first: a wrong key fails while you are still on the settings screen. When the verification passes, switch the same connection to production.

Step-by-step guides for each provider live in the documentation.

How your credentials are handled

  • Credentials encrypted at rest

    Gateway and courier secrets are sealed with AES-256-GCM before they are stored.

  • Secrets never return to the browser

    A saved connection shows a masked store or app key so you can recognise the account, nothing more.

  • Owner-only changes

    Connecting, reconfiguring and disconnecting a delivery or marketing integration is restricted to the store owner.

More on how Lokzon handles merchant data: security and data practices.

Questions

What merchants ask before connecting

Where each credential comes from, how sandbox orders behave, and what happens when a provider is not on the list yet.

Which courier partners can I connect today?

RedX, Pathao, Steadfast and CarryBee. Each one supports a sandbox and a production environment, verifies your credentials before saving, pushes signed status webhooks back to your orders, and shows booked and delivered parcel counts on its integration card.

Can I accept bKash, Nagad, Rocket and Upay?

Yes, but not all through the same door. bKash has a direct merchant API integration. Nagad, Rocket and Upay reach your checkout either through Self MFS accounts you control, or through the hosted page of a gateway like AamarPay or SSLCommerz. The payment instruments table above maps every option to the setup it needs.

Do I need my own merchant account?

For AamarPay, bKash and SSLCommerz, yes. You connect the credentials your provider issued, and settlement stays between you and that provider. Lokzon never asks for your gateway login and never holds your payout.

What is Self MFS, and when should I use it?

Self MFS lets customers send money straight to a mobile wallet number you own, then submit the transaction ID and an optional screenshot. It is the fastest route to taking wallet payments before a gateway approves you. The trade-off is manual confirmation: someone on your team approves each order.

How do advance payments on cash-on-delivery orders work?

For each delivery zone you choose whether the customer pays nothing up front, the delivery charge only, a percentage of the order, a fixed amount, or the full total before dispatch. An advance needs at least one online method enabled, otherwise the option stays locked so a customer is never left unable to pay.

Is there a test mode?

Payment gateways and all four couriers support sandbox credentials. Use the sandbox store IDs your provider issues, place a test order end to end, then change the same connection to production. Marketing tools use test event codes where the provider supports them.

How are my integration credentials stored?

Credentials are encrypted at rest with AES-256-GCM before they reach the database. The API returns only a masked store or app key so you can recognise which account is connected; app secrets, passwords and API tokens are never sent back to the browser.

What if I need a partner you do not support yet?

Tell us which provider and what it needs to do. We prioritise integrations that unblock merchants already selling in Bangladesh, and we will say plainly whether it is on the roadmap.

Selling through something we do not list?

Tell us the provider and what it has to do. We prioritise the ones that unblock merchants already shipping in Bangladesh, and we will tell you honestly whether it is on the roadmap.

What bKash merchant onboarding actually asks for, and how the courier charge you are quoted compares with the platform fee.