GST Verification for Marketplace Seller Onboarding

GST verification for marketplace seller onboarding means confirming a seller’s GSTIN is real, active, and consistent with their registered state before they can list on the platform. It matters because e-commerce operators carry their own tax collection at source obligations under Section 52, and a bad or mismatched seller GSTIN turns into a compliance headache for the platform, not just the seller.

TCS obligations under Section 52 for e-commerce operators

Under Section 52 of the CGST Act, an e-commerce operator is required to collect tax at source on the net value of taxable supplies made through its platform by third-party sellers, and to deposit that amount with the government, reporting it via GSTR-8. This obligation sits with the marketplace, not the individual seller — which is exactly why the marketplace needs accurate, verified GSTIN data for every seller it onboards: TCS reporting and reconciliation depend on the seller’s GSTIN being both correct and current.

A seller onboarding a listing with a mistyped, expired, or fraudulently constructed GSTIN does not just create a bad listing — it creates a TCS reporting mismatch the marketplace has to untangle later, often long after the transactions in question have settled.

Why a seller's GSTIN state should match pickup and registration state

A GSTIN’s first two digits encode the state code of registration — see our GSTIN format explainer for the full structure. When a seller declares a pickup or warehouse address for a marketplace, that address’s state should generally line up with the state their GSTIN was registered in, or with an additional place of business registered under the same GSTIN and reflected in a live lookup response.

A mismatch is not automatically fraud — a business can legitimately register additional places of business in other states — but an unexplained mismatch, especially one with no corresponding additional place of business on record, is worth a manual review step before the seller starts shipping.

Handling composition-scheme sellers on your marketplace

Composition-scheme taxpayers pay GST as a flat percentage of turnover rather than the standard value-added mechanism, and in exchange face restrictions — most notably, they are generally not permitted to make inter-state supplies. Because selling through most online marketplaces functions as inter-state trade capability by default, a seller registered under the composition scheme is typically not eligible to sell through an e-commerce operator the same way a regular taxpayer can. This is a live constraint a marketplace needs to catch at onboarding, not discover after the seller has already listed products.

A GST-aware seller onboarding flow

Put together, a practical marketplace seller onboarding flow runs: GSTIN format and checksum validation, a live status lookup, a check of registration constitution to catch composition-scheme sellers, and a state-consistency check between the GSTIN and the declared pickup address. Only after all four checks clear does the seller move to catalogue setup and payout configuration. This mirrors the general vendor onboarding pattern covered in our vendor onboarding guide, adapted for the seller-side, TCS-specific concerns of a marketplace.

Bulk re-verification of an existing seller base

Marketplaces with an established seller base face a different problem than one-time onboarding: sellers who passed every check at signup can later have their GSTIN cancelled or suspended, and nothing in a marketplace’s day-to-day operation would otherwise surface that change. A periodic bulk sweep — commonly run monthly — re-checks every active seller’s GSTIN status and flags any seller whose registration has lapsed, so listings can be suspended and payouts held before the issue compounds.

// Pseudocode — monthly sweep across the active seller base
for seller in active_sellers:
    response = get_taxpayer_info(seller.gstin)
    if response.status != "Active":
        suspend_listings(seller)
        hold_payouts(seller, reason=response.status)

For marketplaces running this across tens of thousands of sellers, batching lookups through a spreadsheet or scheduled job is more practical than checking one seller at a time — see our bulk GSTIN verification guide for patterns that scale to a large seller base.

Frequently asked questions