WP Companion
Cayman Islands

Payment gateways in the Cayman Islands.

Take Visa and Mastercard in KYD or USD through your own merchant account, with the authentication and audit trail that higher-value transactions call for.

Start here

Which plugin do you need?

It depends on which payment gateway your merchant account runs on. Your bank usually recommends one when you apply, so the bank you choose is the best clue. These are the acquiring banks operating in the Cayman Islands and the gateways they typically recommend.

Plugin available now

Scotiabank

Scotiabank merchants use the eCom+ gateway, and our plugin for it is available today with modal checkout and 3D Secure 2.0. Ask Scotiabank to enable API access for refunds and captures, and tokenization with recurring payments if you want saved cards or subscriptions.

Typically recommends Scotiabank eCom+

Settles in Local currency, USD

Plugin coming Q4 2026

CIBC Caribbean

Formerly CIBC FirstCaribbean International Bank, operating across much of the English-speaking Caribbean. Typically recommends PowerTranz for e-commerce.

Typically recommends PowerTranz

Settles in Local currency, USD

Plugin coming Q4 2026

RBC Royal Bank

Supports e-commerce merchants across several Caribbean markets and typically recommends PowerTranz.

Typically recommends PowerTranz

Settles in Local currency, USD

Not sure which gateway your account runs on? Ask your merchant services contact, or send us what the bank gave you with the sensitive values removed and we will tell you.

Currencies

KYD and USD

Card data

Never touches your site

Settlement

Next business day

Transaction fee

None from us

Why this matters here

Higher ticket values raise the stakes on compliance.

Commerce in Cayman skews towards professional services, membership fees, charter and villa bookings and other transactions where a single payment can be substantial. When individual amounts are large, the questions your clients and your auditors ask about payment handling get sharper.

The architecture here answers most of them before they are asked. The payment form is presented in a modal on your own checkout page but served directly by your bank’s PCI-compliant gateway. Card numbers are entered into the gateway’s field, not yours. Your WordPress database never contains a card number, which means a compromise of your website does not become a compromise of your customers’ cards.

For repeat clients, tokenization lets a card be saved for faster future payment while your site stores only a reference token. Where your bank permits it, the same mechanism powers WooCommerce Subscriptions, so retainers and recurring engagements bill automatically. Combined with 3D Secure 2.0 and full transaction records in both WooCommerce and your bank’s reporting, you get a defensible audit trail without extra process.

What we never do

WP Companion does not process payments, hold funds, or see card data. We are a software licensor, not a payment intermediary, and your relationship for the money itself stays entirely with your bank.

How it works

From application to first live payment.

01

Get an e-commerce merchant account

Ask your bank’s merchant services team for online card acceptance and confirm which gateway the account runs on. If you intend to offer saved cards to repeat clients, confirm that tokenization is permitted on your account configuration during the application.

02

Test free in sandbox

Install our free sandbox build and run the supplied test cards, including a 3D Secure challenge, so you can document the flow before it handles real money. Every feature is unlocked in sandbox, including saved cards, so you can test the full client journey.

03

Go live in KYD, USD, or both

Swap in live credentials, place a small real transaction, and reconcile it against your bank’s reporting before opening the flow to clients.

Start accepting payments in the Cayman Islands.

Tell us where you are in the process and we will tell you honestly what is left to do.