ROKI Connect for WooCommerce
| 开发者 | rokiconnect |
|---|---|
| 更新时间 | 2026年8月27日 00:23 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
ROKI Connect lets your WooCommerce store accept credit and debit cards in Honduran lempira (HNL).
The plugin interface is in Spanish. The settings labels, the admin notices and the texts your customers read are written for Honduran merchants and are not translated. Only this readme is in English, because the plugin directory requires it.
Two ways to charge, and you pick
- Card fields in your store. ROKI draws the card fields inside your own checkout, in a secure iframe. The customer never leaves your page and the card number never touches your server.
- The ROKI hosted checkout. The customer goes out to a ROKI page, pays, and comes back. It is the simplest path and it works even if your store has no HTTPS.
- Refunds and voids from the admin. If the transaction can still be voided, the plugin voids it instead of refunding it: a void never shows up on the customer's card statement.
- Automatic reconciliation. Every five minutes it looks at pending orders and asks ROKI about them. If a webhook is lost to a deployment or a network outage, your customer is not left with a stuck order.
- Verified webhooks. The signature is checked with HMAC-SHA256 over the raw body and in constant time, and repeated deliveries are discarded by their event id.
- A diagnostics button. It checks your configuration end to end - key, environment, webhook, signature - and tells you exactly what is missing, instead of failing only when a customer tries to pay.
- Processing fee passed to the customer. An optional switch: ROKI recalculates the total so that your store keeps the order amount.
- It does not mark an order as paid because the customer came back from the checkout. Coming back means the browser came back, not that money moved. An order is marked paid by the webhook or by reconciliation.
- It does not store card numbers. It never receives them: card entry always happens on a ROKI surface.
- Service and merchant accounts: https://roki.la
- Technical documentation: https://connect.roki.la
安装:
- Upload the plugin folder to
/wp-content/plugins/, or install it from Plugins > Add New. - Activate it from the Plugins menu.
- Go to WooCommerce > Settings > Payments > ROKI Connect.
- Paste your secret key. It starts with
sk_test_for testing and withsk_live_to charge for real. You will find it in the API integration tab of the ROKI portal. - In the mode selector, labelled
Como cobra, choose how you want to charge:Checkout de ROKI (el cliente sale de tu tienda)sends the customer out to ROKI, andCampos de tarjeta en tu tiendadraws the card fields inside your own checkout. For the second one you also need the publishable key (pk_test_orpk_live_) and your store must be served over HTTPS. - Copy the webhook address shown on that screen, register it in the ROKI portal, and paste back the signing secret it gives you.
- Press the
Ejecutar diagnosticobutton. If every check comes out green, you can start charging.
屏幕截图:
常见问题:
Is the plugin interface in English?
No. The settings, the notices and the customer-facing texts are in Spanish, because ROKI Connect is a Honduran payment gateway and its merchants read Spanish. Only this readme is in English, as the plugin directory requires. That is why the steps above quote the on-screen labels in Spanish: they are what you will actually see.
Do I need HTTPS?
Not for the ROKI hosted checkout: the payment happens on a ROKI page, which is HTTPS. For the card fields inside your store, yes - ROKI requires the return addresses to be HTTPS. If you have no certificate, the plugin falls back to the hosted checkout on its own and says so in the diagnostics.
What happens if a webhook is lost?
Nothing serious. Every five minutes the plugin looks at the orders that are still pending and asks ROKI about each one. A paid order is credited on its own even if the notification never arrived.
Can I refund from WooCommerce?
Yes, from the order. The plugin tries to void first, which is the right thing to do while the transaction has not settled, and refunds it if it can no longer be voided.
Which currency does it charge in?
Honduran lempira (HNL), which is what ROKI Connect processes.
Can I test without charging for real?
Yes. With an sk_test_ key everything works the same against ROKI's sandbox, without moving money.
更新日志:
1.1.7
- The External services section now lists, one by one, every address this plugin contacts, which file does it, and under what conditions - including that with the hosted checkout the browser never contacts ROKI at all.
- Ready for the WordPress.org plugin directory. The text domain now matches the plugin slug, so the directory can serve translations; the plugin name follows the "for WooCommerce" pattern the directory requires; and this readme is in English. Nothing in the interface changed: the screens, the settings and their labels are exactly the same, in Spanish.
- The diagnostics script is registered and attached with
wp_add_inline_script()instead of being printed as a tag, and its result is built withcreateElementrather thaninnerHTML, because part of that text comes from the API response. - Added the
Requires Plugins: woocommerceheader. - The ROKI card script is now enqueued with the plugin version attached, so updating the plugin also refreshes the copy the browser had cached.
- The diagnostics button is only drawn for users who can manage WooCommerce. It never granted anything by itself - the diagnostics action already checked the capability and rejected anyone else - but it printed its nonce on any admin screen that carried the right query parameter.
- Fixes a crash that took down the whole site when two ROKI plugins live together. Each one carries its own copy of the PHP client, and the second one to load brought WordPress down with a white screen. It showed up when installing the GiveWP donations plugin next to this one, which is a normal combination for a school or a church with a shop. Now the first one to load wins and the other reuses it.
- A payment made in ANOTHER store can no longer mark an order of this one as paid. If you have two stores connected to the same ROKI account - a test copy, two brands, or a migration with the old store still plugged in - each one receives the other's notifications, signed with the same secret. The plugin now checks whose payment it is before touching anything.
- The card fields inside your store are no longer marked as Beta. The mode has already taken real payments, 3-D Secure included, and there is no reason for the setting to keep saying otherwise.
- Orders taken with the embedded card fields are back in reconciliation and in the query made when the customer returns from the checkout. They used to fall out of both, because both started by asking for a numeric id that this mode never produces: if the webhook was lost, the order stayed pending forever.
- The card fields can live inside your own store: the customer no longer has to go out to the ROKI
checkout. You choose it in the settings, under
Como cobra. - The hosted checkout is still there and is what gets used when the publishable key is missing or the store is not HTTPS.
- The diagnostics warns you when you picked the card fields in your store but they are not being used, and why.
- The API client records the warnings ROKI returns when it ignores a field.
- The automatic update check tolerates a manifest with a BOM, which used to make it fail silently.
- Classic and block checkout.
- Signed webhooks with deduplication by event id.
- Voids and refunds from the admin.
- Automatic reconciliation every five minutes.