TBC Card Payment — quick-start
Accept Visa, Mastercard, Apple Pay and Google Pay on your WooCommerce checkout via TBC Bank's hosted payment page. This guide takes about 30 minutes end-to-end, assuming your TBC merchant contract is already signed.
codeon-tbc-card-paymentBefore you begin
Three things you'll want in front of you before you start. The setup is much smoother when you don't have to leave mid-flow to chase a credential.
- An active TBC E-commerce merchant contract. If you don't have one yet, sign up at tbcbank.ge → Business. Approval typically takes 3-5 business days.
- Your TBC merchant API credentials: a
merchantIdand anapiKey. TBC sends these by email once your contract is live. Look for a message titled "TBC Acquiring — API access". - WordPress admin access to your store, and WooCommerce already installed and active. The plugin doesn't install WooCommerce for you; if you don't have it yet, install it from Plugins → Add New first.
Buy a TBC Card Payment license
Open the TBC Card product page and click Buy license. License is ₾160 / year per domain with a 14-day no-questions refund window.
On checkout, pick how you'd like to pay (card via Bank of Georgia, or bank transfer in GEL). Bank-transfer orders activate within one business day of the wire landing; card orders activate within seconds.
Download the plugin ZIP
Sign in and open codeon.ge/downloads. Find TBC Card Payment in the list and click Download.
The download is a ZIP file watermarked with your account. Don't share it — it's tied to your license and will stop working on stores it's not meant for.
Install the plugin in WordPress
In your WordPress admin, go to Plugins → Add New → Upload Plugin. Select the ZIP you downloaded, click Install Now, then Activate Plugin.
Once activated, you'll see a new admin notice at the top of the screen prompting you for your license key. Click Enter license key— it goes to the plugin's settings screen at WooCommerce → Settings → Payments → TBC Card.
Activate your license
On the plugin settings screen, paste your license key into the License key field and click Save changes.
When the activation succeeds, you'll see:
- A green Active badge with your expiry date (one year from purchase).
- Your store's domain shown as the bound domain — license keys bind on first use.
- The TBC credentials section becomes unlocked underneath.
Plug in your TBC merchant credentials
The TBC credentials section accepts merchantId and apiKey. You'll start with the sandbox / test credentials (the ones with the test_ prefix).
- Field: merchantId
- Your TBC merchant identifier. Looks like
test_M00012345for sandbox. - Field: apiKey
- The API key TBC issued. 32+ character random string. Treat as a secret — never paste into public chats.
- Mode
- Toggle
Sandbox / Production. Start in Sandbox; flip to Production in step 7 once your test order succeeds.
Click Save changes. The plugin pings TBC's status endpoint with these credentials and shows a green Connectedbadge if the handshake succeeds. A red badge means TBC rejected the credentials — usually a typo in the apiKey, or you're still waiting for TBC to activate the merchant account on their side.
Place a 1-tetri test order
Open your storefront in an incognito window so you're not logged in as admin. Add any product to cart, drop the quantity / price down to a 1-tetri test value (you can do this from a hidden test product, or temporarily lower a real product's price), and proceed to checkout.
Pick TBC Card and click Place order. You'll be redirected to TBC's hosted card-entry page.
TBC sandbox test cards
Use one of TBC's sandbox test cards:
Card number : 4111 1111 1111 1111
Expiry : any future month / year
CVV : 123
Name : any
3-D Secure : 1234 (when prompted)
Confirm the test charge. TBC redirects back to your store and you should see:
- Order status flips from Pending to Processing.
- A new Order received email lands in your inbox.
- In WooCommerce → Orders, the TBC transaction ID field is populated on the order detail page.
- In TBC's sandbox merchant portal, the test payment shows up in the transaction log within ~5 seconds.
Switch to production credentials
Once your sandbox test passes, flip the Mode toggle to Production and replace the credentials with the production merchantId + apiKey TBC issued (the ones without the test_ prefix). Click Save changes — the green Connectedbadge should reappear, this time against TBC's production endpoint.
Run one more 1-tetri order using a real card (NOT a sandbox test number). The charge will land on your actual card statement; refund it to yourself from WooCommerce → Orders → Refundwhen you're done to make a clean cut.
What your customers see
On your storefront checkout, the TBC Card option appears with the official TBC logo and the supported card network marks (Visa, Mastercard). Selecting it and placing the order takes the customer to TBC's hosted card-entry page — you never handle their card data, and you don't need PCI-DSS Level 1 certification.
Issuing a refund
From WooCommerce → Orders → [order] → Refund, enter the refund amount and click Refund via TBC Card. The plugin calls TBC's refund endpoint and updates the order status when TBC confirms.
- Full refund:any time before the order is settled by TBC (typically next business day) — instant on the customer's card. After settlement, TBC processes it as a standard refund (3-5 business days back to the card).
- Partial refund: supported. You can refund line items individually.
- Refund decline: TBC rate-limits refunds per-card. If a refund declines with "decline general", wait until the next business day and try again — that's usually the cause. We have a dedicated note on TBC refund rate-limits (coming soon) in the troubleshooting page.
Common errors and what they mean
License domain limit reached- Your key is already bound to a domain. Disconnect the old domain from /licenses first, then re-activate on the new store.
License expired- Your 365-day term ended. Plugin keeps working through the 14-day grace window. Renew from /licenses — the same key continues to work after renewal.
TBC: invalid signature- The apiKey you pasted doesn't match the merchantId on TBC's side. Double-check you're using the matching test/test or production/production pair.
TBC: 3DS authentication failed- Customer cancelled or failed the 3-D Secure step on TBC's page. The order stays Pending — the customer can retry with a different card or bank.
Next steps
- Want to add TBC Installments alongside card? The setup mirrors this guide; see TBC Installments setup.
- Cover Bank of Georgia as well? Many stores run TBC + BoG side-by-side so customers can pick their issuing bank. See BoG Card setup.
- Building automation around order events? The integrator docs cover the public REST surface and webhook contract.