High Risk Payment Gateway for PrestaShop

What is the WcPay high risk payment gateway for PrestaShop?

WcPay is a native PrestaShop module — a single wcpay.zip you upload through the Module Manager. It registers 25 separate payment methods in your checkout, each one independent of the others: its own title, its own description, its own logo, its own minimum amount and, most importantly, its own payout wallet address.

When a customer picks one, the module converts the cart total to US dollars at the live rate, requests a single-use receiving address from the payment infrastructure, creates the order in a dedicated "Awaiting WcPay payment" state and sends the customer to the provider's hosted page. The customer pays with their card, wallet or local rail. The provider converts and forwards the funds to your address. A confirmation comes back to your store, the amount is checked against the amount expected, and the order moves to Payment accepted — the same state PrestaShop uses for every other gateway, so your invoices, stock movements, emails and reports all behave exactly as they always have.

The result is a high risk payment gateway for PrestaShop with no merchant account anywhere in the chain. You are not underwritten, because there is nothing to underwrite. You cannot be terminated, because there is no account to terminate. And you cannot receive a chargeback, because a settled stablecoin transaction is final by design.

Seen from the two sides of the transaction, the high risk payment gateway for PrestaShop looks like this:

How the high risk payment gateway for PrestaShop settles an order

Six steps, all automatic. Your only manual task in the high risk payment gateway for PrestaShop is entering a wallet address once, when you set the method up.

1. The customer reaches the payment step

   PrestaShop asks the module which methods apply. It converts the cart total to USD at the live rate, hides anything below its minimum and returns the rest, each with the title, description and logo you configured.

2. A single-use receiving address is created

   The moment the customer confirms, the module requests a receiving address dedicated to that one order. It is never reused, which is what makes matching a payment to an order reliable rather than a guess.

3. The order is created in a waiting state

   A dedicated order state, "Awaiting WcPay payment", is added to your shop when the high risk payment gateway for PrestaShop is installed. The order exists in your back office from this second onwards, with the amount expected recorded against it, so nothing is ever lost if the customer closes the tab.

4. The customer pays on the provider's page

   Card details, Apple Pay, Google Pay or a local rail — entered on the provider's hosted page, never on your server. Your store never sees, stores or transmits a card number.

5. Funds arrive in your wallet

   The provider converts and forwards the amount to the payout address configured for that method. This normally takes a few minutes and involves no intermediary that could hold, reserve or reverse the money.

6. The order is validated — or flagged

   A confirmation returns to a short, dedicated URL on your store. The amount received is compared against the amount expected. Sufficient, and the order moves to Payment accepted. Short, and it moves to Payment error with a private note recording the exact shortfall and the transaction reference.

Three details that matter in production

Most of what separates a high risk payment gateway for PrestaShop that works on day one from one that works on day ninety is in the edge cases. Three of them are worth spelling out.

Underpayment is never silently accepted. Exchange rates move between the moment a customer clicks and the moment the funds settle, so a strict equality check would fail honest payments. The module accepts a configured tolerance band and rejects anything below it, leaving the order unpaid and the difference documented. You decide what to do; the gateway never decides for you.

Confirmations are replay-safe. If a provider sends the same confirmation twice — which happens — the second one is acknowledged and ignored. An order is never processed, emailed or stocked twice.

The confirmation URL is deliberately short. Several providers silently reject callback URLs beyond a certain length. The module uses a compact controller name and a short token, which keeps the URL comfortably inside every provider's limit — 61 characters with PrestaShop's friendly URLs enabled, 92 without. It is one of those details that only shows up after a week of mysteriously unconfirmed orders, and it is handled for you.

Installing the high risk payment gateway for PrestaShop in 6 steps

No FTP, no database work, no developer. If you can upload a module, you can have the high risk payment gateway for PrestaShop running in about ten minutes.

How to install and configure WcPay payment methods on PrestaShop Upload, activate, configure and take a first live payment

1. Buy your licence and download the module

   Pick a plan below. Your licence key and the wcpay.zip file arrive by email within minutes of payment.

2. Upload it in the Module Manager

   Back office → Modules → Module Manager → Upload a module. Drop wcpay.zip in as it is, without renaming it, and click Install.

3. Open the configuration screen

   Click Configure. Installing the high risk payment gateway for PrestaShop has already created the "Awaiting WcPay payment" order state, registered the checkout hooks and authorised your shop currencies — there is nothing to set up by hand.

4. Activate with your licence key

   Paste the key into the WcPay Activation card and click Activate. All 25 payment methods unlock together. Until a valid key is accepted, the payment settings are not displayed at all.

5. Enable the methods you want

   Tick a method, give it your payout wallet address, and adjust the title, description, logo and logo height if you want to. Leave everything else switched off; you can come back any time.

6. Place a test order

   Go through your own checkout with a small amount. Watch the order appear as "Awaiting WcPay payment", then flip to "Payment accepted" once the funds confirm. That single test tells you the whole chain works. Your high risk payment gateway for PrestaShop is live.

The configuration screen

Everything lives on one page, and that page has exactly two states. Here is what each one looks like.

What your customers then see

Enabled methods appear in the PrestaShop payment step as ordinary options, each with the title and logo you chose. Nothing announces that this is a high risk payment gateway for PrestaShop — it simply looks like the rest of your checkout. Methods below their minimum are absent: here the basket is $56, so iDEAL, UPI and Interac are not offered.

Which businesses run the high risk payment gateway for PrestaShop

Every one of these categories is routinely refused, reserved or terminated by traditional acquirers — and every one of them runs a high risk payment gateway for PrestaShop instead.

The common thread is not the product. It is that a bank somewhere decided the category is not worth its risk budget. A high risk payment gateway for PrestaShop that settles in stablecoin simply does not consult that bank, which is why the same store that was refused on Monday can be taking payments again by Tuesday afternoon.

Choose your plan for the high risk payment gateway for PrestaShop

One licence covers the whole high risk payment gateway for PrestaShop and all 25 payment methods. No per-transaction plugin fee, no revenue share, no percentage taken on your sales — an API partner fee of approximately 4.5 % applies at the provider level.

FAQ — high risk payment gateway for PrestaShop