Can you connect an SCB payment gateway to your website?
You can connect an SCB payment gateway to your website, but it is rarely a plug-in-and-go job. The bank approves you as an online merchant first, then your developer connects the store to SCB's systems, either through an existing plugin or a custom integration built on SCB's developer APIs.
That route suits an established company that already banks with SCB, has steady order volume and wants money to land straight in its SCB account.
For a new shop, or anyone who wants cards, PromptPay and wallets live within a couple of weeks, a payment aggregator such as Omise (for a time branded Opn Payments) or 2C2P is usually simpler. Aggregators usually have ready-made WooCommerce plugins, several list a Shopify integration (check Shopify's directory for Thailand), one contract covers several payment methods, and payouts still go to your Thai bank account, SCB included. If you want the wider picture first, our pillar guide has Omise, 2C2P and SCB compared side by side.
A quick way to decide
- Lean towards SCB directly if you already have an SCB relationship manager, sell enough to negotiate rates, and have a developer who can maintain an API integration.
- Lean towards an aggregator if you need a fast launch, sell on Shopify, or want many payment methods under one dashboard.
- Consider both if you want SCB's QR for local buyers and an aggregator for international cards.
We are not a partner or reseller of SCB or any gateway. We build stores and connect whichever provider you sign with, so the advice below is written from the website side, which is the part the bank's own pages do not cover.
What SCB offers for online payments
SCB publishes its payment APIs on the SCB Developers portal. At the time of writing, the portal lists services built around Thai QR payments (the PromptPay-compatible QR a customer scans with any Thai banking app) and payment through the SCB EASY app for buyers who bank with SCB. Card acceptance for online stores is arranged through SCB's merchant services team rather than self-service sign-up. Product names and bundles change, so confirm the current list with the bank before you plan the build.
What each option means for your checkout
- QR payment: the store shows a QR code with the exact amount, the customer pays from their banking app, and SCB notifies your website when the money arrives. This is the option most Thai shoppers already know.
- App payment on mobile: a buyer on a phone taps a button, the SCB EASY app opens, they confirm, and they return to your store. Smooth for SCB customers, irrelevant for everyone else.
- Cards: Visa, Mastercard and others through the bank's card acquiring. Expect a separate application and stricter checks than for QR.
Note what is missing: e-wallets such as TrueMoney Wallet payments, instalment plans from other banks and foreign wallets usually need an aggregator or a separate contract. If your customers are mostly SCB account holders paying by QR, the bank route covers you well. If they are tourists or expats paying by foreign card, it covers only part of the picture.
What will SCB ask you for?
Banks check your business and your website before they let you take money online. Have these ready before you apply, because a missing refund policy can stall an application for weeks. The exact list comes from SCB, so treat this as preparation, not the official form.
- Business registrationCompany or shop registration documents, plus the ID of the directors or owner.
- SCB business accountThe account where settlements will land, in the same name as the business.
- A live or staging websiteThe bank usually wants to see real products, prices in THB and a working checkout flow.
- Refund and return policyClear, visible, and matching how you actually handle returns.
- Privacy noticeA PDPA-aligned notice explaining what customer data you collect and why.
- Terms and contact detailsTerms of sale, a business address, phone and email shown on the site.
- Delivery informationWhich couriers you use, delivery times and shipping costs.
Fees and settlement: questions to ask
We do not publish SCB's rates here because merchant pricing is negotiated and changes, and a wrong number is worse than none. What we can give you is the list of questions that make two quotes comparable, whether they come from SCB, Omise or 2C2P.
On the fee itself
- What is the percentage per transaction for QR, for Thai cards and for foreign cards? Are they different?
- Is there a setup fee, a monthly fee or a minimum monthly volume?
- Are fees charged on refunded orders?
On settlement
- How many working days until the money reaches your account, and does that differ by payment method?
- Is settlement gross (fees invoiced later) or net (fees deducted first)? This matters for your bookkeeping and for matching payouts to orders.
- Does the bank issue a tax invoice for its fees in a format your accountant can use?
On risk
- Is there a rolling reserve or a deposit held back on card payments?
- How are chargebacks handled, and what evidence will you need to supply?
An aggregator often charges a higher headline rate than a bank quote for a large merchant, but it bundles more payment methods and needs less development work. Compare the total cost over a year, including the build and upkeep, not just the percentage.
Connecting SCB to WooCommerce
WooCommerce is the more flexible platform for a bank-direct gateway (see how we approach WooCommerce store development), because you control the code and can add any payment method. There are two routes.
Route 1: an existing plugin
Some developers sell WooCommerce plugins for Thai bank QR payments. Before you install one, check who maintains it, when it was last updated, whether it supports the current WooCommerce version, and whether SCB recognises it. An abandoned payment plugin is a real risk: a WooCommerce update can break checkout on a Saturday night.
Route 2: a custom integration on SCB's API
Here your developer builds a small WooCommerce payment extension that asks SCB for a QR code for each order, shows it at checkout, and listens for SCB's payment confirmation (a webhook) to mark the order paid. Done properly, it also handles expired QR codes, duplicate notifications and partial failures. This takes longer than installing a plugin, but it fits your checkout exactly and does not depend on an outside plugin author.
If you only need PromptPay QR and do not mind which bank sits behind it, there are lighter options, which we cover in our guide to choosing a payment gateway for WordPress stores that accept PromptPay. Whichever route you take, keep the order status logic simple: an order should move to "processing" only when the bank confirms payment, never when the customer clicks "I have paid".
SCB and Shopify
Shopify works differently. You cannot drop any payment code into its checkout, as our guide to Shopify payments in Thailand explains: payments must come from Shopify's own processor or from a provider that Shopify has approved as a third-party payment provider. So the question is not "can we connect SCB?" but "is there an approved provider in Shopify's list for Thailand that settles to SCB or offers SCB QR?"
At the time of writing, aggregators that operate in Thailand appear in Shopify's third-party provider list, and those can pay out to an SCB account. A direct SCB integration inside Shopify's checkout is not something a store owner or developer can build independently. Check Shopify's help page on third-party providers for the current list before you commit.
Workarounds to avoid
- Manual payment methods where the customer transfers to your SCB account and uploads a slip. It works for small volumes, but every order needs a human check, and slips can be faked.
- Redirecting buyers off Shopify to a separate payment page you built. It breaks order tracking and usually breaches the platform's rules.
Plan level does not change this much. Shopify Plus unlocks more checkout customisation, but payment providers still need approval; our article on Shopify vs Shopify Plus explains where that upgrade does and does not pay off.
Testing before launch
SCB's developer portal provides a sandbox, a test environment where your store can create QR codes and receive fake payment confirmations without real money moving. Use it fully before you switch to live keys.
Test orders worth running
- A normal paid order, from cart to "processing", with the confirmation email sent.
- A QR code that expires before payment, so the order is cancelled and stock is released.
- The same payment notification arriving twice, which should not create two paid orders.
- A refund issued from the store, checked against what the bank shows.
- A customer on a slow mobile connection who closes the tab after paying. The webhook should still mark the order paid.
Reconciliation, refunds and data duties
Once live, someone has to match bank settlements to orders each week. Ask your developer to store the bank's transaction reference on every order so this is a search, not a guessing game. Refunds may need to be triggered in the bank's merchant portal rather than inside WooCommerce, so write the steps down for your staff.
On data: if card details are entered on the bank's hosted page, most of the card security burden under the PCI DSS standard stays with the bank. Your store still holds names, addresses and phone numbers, so PDPA duties apply: a privacy notice, consent where needed, and limited staff access to order data.
How does merchant approval fit your launch timeline?
The most common surprise is timing. A typical store build with us takes about 15 days from the agreed brief to launch, and larger catalogues take longer. Merchant approval runs on the bank's schedule, not ours, and it can take longer than the build itself, especially for card acceptance. So apply to SCB, or to an aggregator, as soon as you decide to sell online, ideally before design starts.
A sensible order of work
- Decide bank-direct or aggregator, using the trade-offs above.
- Prepare the documents and website policies from the checklist.
- Submit the merchant application while the store is being built on a staging site the bank can review.
- Integrate and test in the sandbox, then switch to live keys once approval arrives.
- Launch with at least one payment method working, and add others later if one is still pending.
If you are still at the planning stage, our step-by-step guide on how to create a website for e-commerce in Thailand puts payments in context with products, shipping and tax, and our look at how e-commerce in Thailand is shifting explains why QR payments matter so much to local buyers.
When you are ready to build, our ecommerce website design and development service covers Shopify or WooCommerce with PromptPay, cards, COD and Thai couriers set up, plus e-Tax invoice setup and staff training. The E-commerce package starts from THB 50,000 as an indicative one-time price, and the final figure is set in your written quote; see how much an e-commerce website costs for what drives the number.
About this guide
Who builds your site
Litesh Dhir
Builds and ranks the websites: the systems behind the 17 client sites whose Search Console numbers we publish.
More about usMore on e-commerce payments
Sources
- SCB Developers portal
- Shopify Help: third-party payment providers
- PCI Security Standards Council
- Bank of Thailand: PromptPay