Payments

Sellerlane is a bring-your-own-gateway platform. You connect your own merchant account, and settlements go directly from the gateway to your bank. Sellerlane never holds your funds and adds 0% in extra transaction fees — you pay the pricing of your selected gateway and messaging provider.

Everything lives under Settings → Payments, where you manage two distinct things: gateway accounts (the connection to a provider) and payment methods (what a buyer actually sees and selects). You also add manual / offline methods like Cash on Delivery here.

Note

Connecting a gateway is two steps, not one. First you connect an account, then you add it as a payment method and decide whether it shows online, at POS, or both. Connecting alone does not make a method appear at checkout.

Providers

The Connect gateway modal is deployment-aware and shows the providers available to your store. Sellerlane includes adapters for Razorpay, PayU, Cashfree, Stripe, Adyen, Xendit, Paystack, Mercado Pago, Tap, 2C2P, Flutterwave, and Airwallex. Availability, currencies, payment instruments, and live-account approval still depend on the provider and your merchant account.

For India, the primary INR choices are:

• Razorpay — UPI, cards, netbanking, and wallets according to your account.
• PayU — an alternative INR gateway with its provider-hosted checkout.
• Cashfree — INR checkout through Cashfree Web Checkout; approve every storefront/POS domain you use in Cashfree’s domain-whitelisting settings.

Stripe and the regional providers appear only where the deployment and store currency support them. The connect modal is authoritative; a provider that is not offered cannot be activated by typing its enum or reusing old credentials.

The payment methods a buyer can choose — UPI, credit/debit cards, netbanking, wallets — are whatever your gateway account has enabled. Sellerlane surfaces your account; it doesn’t separately toggle individual card networks or UPI apps.

Prerequisites

1. A supported merchant account with KYC/onboarding completed and live mode enabled by the provider.

2. Your API credentials (key/secret) or the ability to complete the provider’s OAuth/Connect authorization in a browser popup.

3. Staff access to Settings → Payments for the store. See staff accounts.

Connect a gateway

Open Settings → Payments → Connect gateway and pick a provider card. Use a redirect/OAuth button when the card offers one, or choose Enter credentials for the provider’s supported manual API-key flow.

Connect (when offered)

Use this when your provider supports it — no copying secrets by hand.

1. In Connect a payment gateway, click Connect on a provider card that offers a redirect flow. Stripe uses Stripe Connect; other providers expose a redirect only when that integration is enabled.

2. A new window opens on the provider’s site. Sign in and authorize Sellerlane.

3. You’re returned to the connect result screen. The account appears under Gateway accounts with a connection status of Connected.

Tip

If the popup is blocked, allow popups for the admin domain or copy the authorization link your browser shows, then retry.

With Connect, webhooks are registered for you automatically — you don’t set a webhook secret.

Enter credentials (manual)

Use this if you’d rather paste API keys, or your provider account isn’t eligible for the redirect flow.

1. Click Enter credentials on the provider card to open Connect provider manually.

2. Choose Mode: Test or Live. Test and live are separate accounts — start in Test, then connect a Live account when you’re ready.

3. Paste the provider credentials requested by the form. Common examples:

   • Razorpay — Key ID and Key secret.
   • PayU — Merchant key and Salt.
   • Cashfree — App ID and Secret key.
   • Stripe — Secret key (and optional Publishable key).

4. Optionally paste a Webhook secret now (you can also add it later — see below). Leave Set active after saving on to make this the active account for its provider.

5. Click Save. Credentials are encrypted before storage — never share them in screenshots or support chats.

Caution

Manual (API-credential) accounts do not auto-register webhooks. You must set a Webhook secret so Sellerlane can verify provider webhook signatures — otherwise payment confirmations can’t be trusted. See Set a webhook secret below.

Add the account as a payment method

A connected account does nothing at checkout until you publish it as a method:

1. Under Gateway accounts, open the ⋮ menu on the account and choose Add as payment method (or Add method on the mobile cards).

2. The method is created instantly under Selectable payment methods, named after the provider and starting Inactive with both channels off. (Each account can have one gateway method — the option is disabled once one exists.)

3. Activate the method from its ⋮ menu, then flip the Online and POS switches to control where buyers see it. Channels only take effect on an Active method; an inactive one shows as Hidden.

Set the active account

You can hold more than one account per provider (for example a Test and a Live account). Only one is active at a time. From the account’s ⋮ menu, choose Set active. An account must be Connected before it can be set active.

POS payment actions

A POS-enabled gateway method exposes only the actions compatible with its provider family and your configured allow-list.

Action	Where it is available	What it does
QR code	POS for Razorpay, PayU, and Cashfree	Shows a Sellerlane scan-to-open QR that takes the buyer to secure hosted checkout; it is not advertised as a provider-native UPI QR
Payment link	POS	Displays the safe link or queues it through configured SMS/email delivery
Hosted checkout	Online and POS	Opens the provider-hosted payment experience

Online-enabled methods must retain hosted checkout. A bad or incompatible allow-list fails closed instead of silently offering broader actions. Sellerlane does not offer a synthetic UPI intent, because the current adapters do not return a real upi:// action.

For simultaneous sale tabs, buyer-device handoff, messaging behavior, and counter examples, see POS billing & payments.

Manual and offline payment methods

Beyond gateways, you can create manual methods for anything settled outside a gateway: Cash on Delivery (COD), bank transfer, manual UPI, cash, or an external card terminal. Click Add manual method on the Payments page.

The form (Settings → Payments → manual / new) gives you:

• Display name and Short description — what the buyer sees at checkout (e.g. Cash on Delivery).
• Payment instructions — longer text shown to the buyer after they pick the method (e.g. your bank account or UPI ID).
• Status — Active or Inactive. Inactive methods are kept for history but hidden from checkout and POS.
• Settlement policy — the key choice:
  • Pending until confirmed — order stays awaiting payment until you confirm it. Use for COD, bank transfer, manual UPI, or invoices.
  • Mark paid immediately — order is treated as paid at checkout. Use for POS cash or external-terminal payments you collect on the spot.
• Require reference — ask the buyer for a UTR / transaction ID (or any custom label you set in Reference label).
• Minimum / Maximum amount — restrict the method to an order-value range.
• Online checkout and POS toggles — per-method visibility. An Active method must be enabled on at least one of the two.

Note

Amount limits are entered in cents (the smallest currency unit). For INR, ₹100 is 10000. Leave a field blank for no limit.

Manage methods and accounts

Under Selectable payment methods, each row shows where it’s visible (Online, POS, or Hidden) and an action menu.

• Activate / Deactivate — deactivating hides a method from checkout and POS but keeps its history intact; you can reactivate it any time.
• Archive — hides a method from normal settings lists while preserving its order history and analytics. Use this instead of deleting a method that has orders against it.
• Reorder — manual methods carry up/down arrows to set the order buyers see them in at checkout. Each row also exposes its Online and POS switches directly, and manual methods have an Edit action.

For gateway accounts, the ⋮ menu also offers:

• Set webhook secret — see below.
• Disconnect — drops the connection; linked gateway payment methods are deactivated.
• Delete account — only works when the account isn’t active and no payment method references it. Disconnect or deactivate first.

Caution

Never try to remove a method tied to past orders. Deactivate or Archive it instead — both keep the records and analytics your reports depend on.

Set a webhook secret

Required for manual / API-credential accounts (Connect/OAuth accounts get webhooks automatically).

1. Open the account’s ⋮ menu and choose Set webhook secret.

2. Paste the webhook signing secret from your provider’s dashboard and click Save.

The secret is encrypted and used by Sellerlane to verify the signature on incoming provider webhooks, so payment and refund notifications can be trusted.

Test vs live mode

Manual accounts carry a Mode of Test or Live, set when you enter credentials. They are independent accounts, so the safe path is:

1. Connect a Test account and add it as a method.

2. Place a test order end to end, then issue a small test refund.

3. Connect a Live account, set it active, and disable or deactivate the test method.

4. Finish with one small real transaction and refund before launch.

Connect-session audit log

Every connect attempt is logged at Settings → Payments → sessions (Gateway connect sessions). Each row shows the provider, auth method, and a status of Completed, Pending, or Expired. Check it when a Connect flow didn’t finish — for example a popup closed early or the link expired.

What’s handled for you

• Reconciliation — orders are continuously reconciled against gateway records, so a delayed webhook or dropped connection never leaves an order in limbo.
• Capture — gateway charges are captured automatically; there’s no separate manual-capture step to forget. If a charge lands with no matching order (e.g. after a session expired), Sellerlane issues an automatic late refund.
• Failed payments — stuck or failed attempts are retried and swept automatically.

Refunds

Issue full or partial refunds from the order page; they’re processed back to the original payment method and tracked to completion, with an automatic late-refund safety net for edge cases. For the full procedure, see refunds and returns.

Payouts

There is no separate payouts page in Sellerlane — and that’s by design. Funds settle gateway → your bank on your gateway’s own schedule. Sellerlane is not in the money path and takes no cut, so manage payout timing and statements in your connected gateway’s dashboard.

Troubleshooting

• A method isn’t showing at checkout — confirm it’s Active and toggled Online, and that the order total is within any min/max amount limits.
• Webhooks aren’t confirming payments — for manual accounts, set the Webhook secret; for Connect accounts, re-check the connection status.
• Can’t set an account active — it must be Connected first; check the sessions log for a failed connect.
• Can’t delete an account — disconnect it and remove any payment method that references it first.

Next steps

Shipping & checkout

Configure delivery and the checkout flow buyers complete payment in. Shipping and checkout

Manual payment methods

A deeper look at offline methods like COD and bank transfer. Manual payment methods

Refunds & returns

Issue refunds and run returns from the order page. Refunds and returns

Taxes

Set up GST and tax rules for India. Taxes