Title: Fastaar Pay
Author: Fastaar
Published: <strong>Agẹmọ  17, 2026</strong>
Last modified: Agẹmọ  17, 2026

---

Ṣàwárí àwọn plugin

![](https://ps.w.org/fastaar-pay/assets/banner-772x250.png?rev=3611770)

![](https://ps.w.org/fastaar-pay/assets/icon-256x256.png?rev=3611770)

# Fastaar Pay

 Láti ọwọ́ [Fastaar](https://profiles.wordpress.org/fastaar/)

[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/fastaar-pay.1.2.7.zip)

 * [Àwọn àlàyé](https://yor.wordpress.org/plugins/fastaar-pay/#description)
 * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/fastaar-pay/#reviews)
 *  [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/fastaar-pay/#installation)
 * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/fastaar-pay/#developers)

 [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/fastaar-pay/)

## Àpèjúwe

Fastaar Pay allows you to easily accept bKash, Nagad, Rocket, and Upay payments 
on your WooCommerce store. This plugin is built with modern performance and security
standards in mind, utilizing native WordPress APIs to achieve fast response times
and safe cryptographic signature verification on incoming webhooks.

### Key Features

 * **Seamless Checkout:** Redirect customers to the secure Fastaar checkout page
   to pay via bKash, Nagad, Rocket, or Upay.
 * **Block Checkout Compatible:** Works on both the classic shortcode checkout and
   the WooCommerce Cart & Checkout blocks.
 * **Full & Partial Refunds:** Issue full or partial refunds directly from the WooCommerce
   order admin — no need to log in to the Fastaar dashboard. Partially refunded 
   orders stay refundable for the remaining balance.
 * **Cryptographic Verification:** Every webhook request is verified using SHA-256
   HMAC signature validation to prevent tampering and spoofing.
 * **Idempotency Support:** Automatic safety checks prevent double processing of
   identical webhooks.
 * **Detailed Logs:** Enable debug logging to track and trace API calls and incoming
   webhook payloads.
 * **High Performance:** No external libraries or SDK dependencies; uses optimized
   WordPress HTTP APIs.

### External services

This plugin connects to the Fastaar payment platform (fastaar.com) to process bKash,
Nagad, Rocket, and Upay payments — this connection is required for the plugin to
function, since Fastaar is the payment processor.

 * **Creating a payment (at checkout):** When a customer places an order using Fastaar,
   the order total, currency, order ID, order key, and the return/cancel URLs are
   sent to `https://fastaar.com/api/v1/payments` so Fastaar can create a hosted 
   checkout session. The customerÌtumọ̀ Yorùbá: ’s browser is then redirected to
   FastaarÌtumọ̀ Yorùbá: ’s checkout page to complete payment.
 * **Refunds (from the WooCommerce order admin):** If you issue a refund, the Fastaar
   payment ID and the refund amount are sent to FastaarÌtumọ̀ Yorùbá: ’s refund 
   endpoint.
 * **Checking payment status:** On the order-received (thank-you) page, the plugin
   may query Fastaar for the current status of a payment, in case the confirmation
   webhook hasnÌtumọ̀ Yorùbá: ’t arrived yet.
 * **Incoming webhooks:** Fastaar sends payment status updates (e.g. `payment.completed`)
   back to this siteÌtumọ̀ Yorùbá: ’s webhook URL so the corresponding WooCommerce
   order can be marked paid.

No data is sent to Fastaar unless a customer actually places an order using this
gateway, or a store admin performs the actions above.

Fastaar service: [Terms of Service](https://fastaar.com/terms), [Privacy Policy](https://fastaar.com/privacy).

## Àwọn àwòrán ìbòjú

[⌊Fastaar payment gateway selection during checkout.⌉⌊Fastaar payment gateway selection
during checkout.⌉[

Fastaar payment gateway selection during checkout.

[⌊Fastaar listed among WooCommerce's Payment providers.⌉⌊Fastaar listed among WooCommerce's
Payment providers.⌉[

Fastaar listed among WooCommerceÌtumọ̀ Yorùbá: ’s Payment providers.

[⌊Fastaar settings page — API Key, Test Mode, and Order Status After Payment.⌉⌊Fastaar
settings page — API Key, Test Mode, and Order Status After Payment.⌉[

Fastaar settings page — API Key, Test Mode, and Order Status After Payment.

[⌊Fastaar settings page continued — Webhook URL, Webhook Secret, and Debug Log.⌉⌊
Fastaar settings page continued — Webhook URL, Webhook Secret, and Debug Log.⌉[

Fastaar settings page continued — Webhook URL, Webhook Secret, and Debug Log.

## Ìgbéwọlẹ̀

 1. Upload the entire `fastaar-pay` folder to the `/wp-content/plugins/` directory,
    or install it directly via the WordPress admin panel.
 2. Activate the plugin through the ‘Plugins’ menu in WordPress.
 3. Navigate to **WooCommerce > Settings > Payments**.
 4. Click on **Fastaar** to configure your gateway options:
 5.  * **Test Mode:** Leave off for real payments. Turn on to test the full order flow
       without real money — same Test Mode already available in your Fastaar merchant
       panel.
     * **API Key:** Enter the key matching the Test Mode setting above — a Test API
       Key (starts with `fk_test_`) if Test Mode is on, or a Live API Key (starts with`
       fk_live_`) if itÌtumọ̀ Yorùbá: ’s off. Get it from your Fastaar merchant dashboard.
       It must include the `payments:write` ability (and `payments:refund` if you plan
       to issue refunds from WooCommerce). Switching Test Mode means re-entering the
       matching key.
     * **Order Status After Payment:** Choose which WooCommerce order status a Fastaar
       payment moves to once confirmed — Processing, Completed, On hold, or leave it
       as Default to let WooCommerce decide as usual.
     * **Webhook Secret:** Set the signing secret for webhook verification.
 6. The settings page shows your storeÌtumọ̀ Yorùbá: ’s **Webhook URL** — copy it and
    add it as a webhook endpoint in your Fastaar merchant dashboard. When picking which
    events to send, `payment.completed` is the only one this plugin acts on (it marks
    the order paid); subscribing to just that is enough, though subscribing to all 
    events is harmless too. Paste the signing secret Fastaar gives you back into **
    Webhook Secret** above.

## FAQ

### Where can I get my Fastaar API credentials?

Log in to your Fastaar merchant portal, and navigate to settings to find your API
key and Webhook secret.

### Where do I find the Webhook URL to register in my Fastaar dashboard?

ItÌtumọ̀ Yorùbá: ’s shown directly on the **WooCommerce > Settings > Payments > 
Fastaar** page, just above the Webhook Secret field — copy it from there. It follows
the format `https://yourdomain.com/?wc-api=fastaar`.

### Which webhook events do I need to subscribe to?

Only `payment.completed` — thatÌtumọ̀ Yorùbá: ’s the only event this plugin listens
for, and itÌtumọ̀ Yorùbá: ’s what marks a WooCommerce order as paid. Any other event
Fastaar sends (e.g. `payment.refunded`, `payment.failed`) is received and acknowledged
but otherwise ignored.

### What API key abilities does this plugin need?

payments:write is required to create payments at checkout. `payments:refund` is 
only needed if you plan to issue refunds from the WooCommerce order admin — without
it, refund attempts fail with an “ability_denied” error.

### Can I test payments before going live?

Yes — turn on Test Mode, then enter your Test API Key (starts with `fk_test_`) in
the API Key field. Test payments never touch real money and auto-complete on the
Fastaar checkout page. When youÌtumọ̀ Yorùbá: ’re ready to go live, turn Test Mode
back off and swap in your Live API Key (starts with `fk_live_`).

### What does the “Order Status After Payment” setting do?

By default WooCommerce decides the status after payment (usually Processing, or 
Completed for virtual/downloadable-only orders). If youÌtumọ̀ Yorùbá: ’d rather 
every Fastaar payment always land on a specific status — e.g. always Completed, 
or always On hold for manual review — pick it here instead of Default.

### IÌtumọ̀ Yorùbá: ’m getting an “ability_denied” or “authentication_error” response

Your API key is missing a required ability, or has expired. Open the key in your
Fastaar merchant dashboard
 under API Keys and confirm it has `payments:write` (
and `payments:refund` for refunds) and no expiry date in the past.

### I enabled Fastaar but it doesnÌtumọ̀ Yorùbá: ’t show up at checkout

Make sure you clicked Save on WooCommerce > Settings > Payments after enabling it.
If your checkout page uses the WooCommerce Cart & Checkout blocks, this plugin registers
itself there too — if itÌtumọ̀ Yorùbá: ’s still missing, deactivate and reactivate
the plugin to make sure the block registration is picked up, and check for a plugin
update.

## Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

## Àwọn Olùkópa & Olùgbéejáde

“Fastaar Pay” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa 
sí plugin yìí.

Àwọn Olùkópa

 *   [ Fastaar ](https://profiles.wordpress.org/fastaar/)
 *   [ Amdadul Haq ](https://profiles.wordpress.org/amdad121/)

[Túmọ̀ “Fastaar Pay” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/fastaar-pay)

### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/fastaar-pay/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/fastaar-pay/), tàbí ṣe àgbékalẹ̀
sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/fastaar-pay/) nípasẹ̀
[RSS](https://plugins.trac.wordpress.org/log/fastaar-pay/?limit=100&mode=stop_on_copy&format=rss).

## Àkọsílẹ̀ àwọn àyípadà

#### 1.2.7

 * Added a Bangla (bn_BD) translation, bundled as a fallback for stores whose site
   language is set to Bangla.
 * Added a `.distignore` file so the WordPress.org SVN deploy explicitly excludes
   dev-only files, instead of relying on the deploy actionÌtumọ̀ Yorùbá: ’s default
   behavior.
 * Removed “or cards” from the default gateway description, since Fastaar checkout
   is mobile banking only.

#### 1.2.6

 * Minor readme and CI workflow cleanup.

#### 1.2.5

 * Added `uninstall.php` to remove the pluginÌtumọ̀ Yorùbá: ’s settings when itÌtumọ̀
   Yorùbá: ’s deleted through the WordPress admin.
 * Added a `Requires Plugins: woocommerce` header so WordPress can prompt to install
   WooCommerce first, if itÌtumọ̀ Yorùbá: ’s missing.
 * Removed a dead legacy webhook hook that never fired.

#### 1.2.4

 * Renamed the gateway class from `WC_Gateway_Fastaar` to `Fastaar_WC_Gateway` (
   and its file to match) so it carries the pluginÌtumọ̀ Yorùbá: ’s own prefix, 
   per WordPress.orgÌtumọ̀ Yorùbá: ’s naming-collision guidelines.

#### 1.2.3

 * Documented the pluginÌtumọ̀ Yorùbá: ’s use of the Fastaar API as an external 
   service, per WordPress.org guidelines.
 * Sanitized webhook input (event name, order ID, payment ID, and the logged request
   body) before use.

#### 1.2.2

 * Fixed the Plugin URI and Author URI being identical in the plugin header (a WordPress.
   org plugin check requirement) — Plugin URI now points to the pluginÌtumọ̀ Yorùbá:’
   s GitHub repository, Author URI to fastaar.com.

#### 1.2.1

 * Renamed the plugin folder from `fastaar-woocommerce` to `fastaar-pay` to match
   the pluginÌtumọ̀ Yorùbá: ’s text domain and WordPress.org slug.
 * Simplified the API Key setting to a single field (used as either the Live or 
   Test key depending on the Test Mode toggle) instead of separate Live/Test API
   Key fields.
 * Added a directory listing icon and banner, and corrected the Screenshots section
   to describe all four current screenshots.
 * Added `amdad121` as a contributor.

#### 1.2.0

 * Reworked Test Mode into an actual working toggle, matching the Test Mode in your
   Fastaar merchant panel: a Test Mode switch plus a single API Key field, validated
   against the matching `fk_test_`/`fk_live_` prefix for whichever mode is on. (
   The old “Sandbox Mode” checkbox was stored but never used anywhere — itÌtumọ̀
   Yorùbá: ’s been replaced by this.)
 * Added an “Order Status After Payment” setting — choose Processing, Completed,
   On hold, or leave it as WooCommerceÌtumọ̀ Yorùbá: ’s default for orders paid 
   via Fastaar.
 * Fixed orders getting stuck on “Pending payment” when the Fastaar webhook is delayed
   or canÌtumọ̀ Yorùbá: ’t reach the site (e.g. local development). The order-received
   page now double-checks the payment status directly as a fallback, in addition
   to the webhook.
 * Added the Fastaar logo next to the gateway title at checkout, on both the classic
   and block-based checkout.
 * Fixed settings validation — enabling the gateway without an API Key for the active
   mode, or entering one that doesnÌtumọ̀ Yorùbá: ’t start with the right prefix(`
   fk_live_`/`fk_test_`), is now rejected on save with a clear admin notice instead
   of silently saving. A missing Webhook Secret is still saved (itÌtumọ̀ Yorùbá:’
   s optional), but now shows a warning since webhook signature verification wonÌtumọ̀
   Yorùbá: ’t work without one.
 * Verified compatibility with WordPress 7.0 and WooCommerce 10.9.
 * Added WooCommerce Cart & Checkout blocks support — Fastaar now appears at checkout
   on stores using the block-based checkout, not just the classic shortcode checkout.
 * Added partial refund support — WooCommerceÌtumọ̀ Yorùbá: ’s own refund amount(
   full order, a partial amount, or individual line items) is now passed through
   to Fastaar instead of always refunding in full. Refunding less than the full 
   amount marks the Fastaar payment as partially refunded, and it can be refunded
   again later for the rest.
 * The settings page now displays your storeÌtumọ̀ Yorùbá: ’s Webhook URL directly,
   so you no longer have to construct it by hand to register it in the Fastaar dashboard.
 * The API Key and Webhook URL settings now explain exactly which abilities (`payments:
   write`, `payments:refund`) and webhook event (`payment.completed`) the plugin
   needs, so you donÌtumọ̀ Yorùbá: ’t have to guess or check the docs separately.

#### 1.1.0

 * Added refund support — issue refunds from the WooCommerce order admin via `POST/
   api/v1/payments/{id}/refund`.
 * Updated error parsing to match the new API error format (`message` + `code` fields
   instead of the nested `error` object).

#### 1.0.0

 * Initial release of the Fastaar Payment Gateway for WooCommerce.

## Àkójọpọ̀ Meta

 *  Ẹ̀yà **1.2.7**
 *  Ìgbàgbọ́hùn tó kẹ́yìn **ọjọ́ 6 sẹ́yìn**
 *  Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10**
 *  Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ **
 *  Dánwò dé **7.0.2**
 *  Ẹ̀yà PHP ** 8.1 tàbí ju bẹ́ẹ̀ lọ **
 *  Èdè
 * [English (US)](https://wordpress.org/plugins/fastaar-pay/)
 * Àwọn àmì
 * [Bangladesh](https://yor.wordpress.org/plugins/tags/bangladesh/)[bKash](https://yor.wordpress.org/plugins/tags/bkash/)
   [nagad](https://yor.wordpress.org/plugins/tags/nagad/)[payment gateway](https://yor.wordpress.org/plugins/tags/payment-gateway/)
 *  [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/fastaar-pay/advanced/)

## Àwọn ìbò

Kò sí ìwádìí tí a tíì fi ránṣẹ́.

[Your review](https://wordpress.org/support/plugin/fastaar-pay/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/fastaar-pay/reviews/)

## Àwọn Olùkópa

 *   [ Fastaar ](https://profiles.wordpress.org/fastaar/)
 *   [ Amdadul Haq ](https://profiles.wordpress.org/amdad121/)

## Ìrànlọ́wọ́

Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?

 [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/fastaar-pay/)

## Ṣe ìtọrẹ

Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí?

 [ Ṣe ìtọrẹ sí plugin yìí ](https://fastaar.com)