Disbursement Payout Bridge for NICEPAY helps your team create bank payout requests, approve them with separation of duties, and track results. In Automatically mode it connects to NICEPAY Sandbox or Production APIs and accepts signed notification callbacks.
Common use cases:
Employee salary payments
Vendor or supplier payouts
Affiliate commission payments
Cashback or refund transfers
Marketplace withdrawal payments
First-time setup
Activate the plugin. Database tables and payout capabilities are created for Administrators.
Open Settings. Choose Manually (no API) or Automatically (live NICEPAY integration).
Select Sandbox (dev.nicepay.co.id) for testing or Production (www.nicepay.co.id) for live payouts.
Enter Merchant ID, Channel ID, Client Key, Merchant Key, and Private Key from your NICEPAY contract.
Copy the Notification callback URL from Settings and register it in the NICEPAY merchant portal.
Enable API logging only while debugging (recommended on Sandbox, off on Production).
Use two different WordPress users to test: one creates requests, another approves them.
Daily workflow
Manually mode
User A: Request → create payout (or bulk CSV) → status pending.
User B: Approvals → Approve or Reject (no NICEPAY API call).
Transaction: view history and statuses.
Automatically mode
User A: Request → create payout → plugin registers with NICEPAY when applicable.
After purchase, open this item in My Downloads and choose Get Support.
What support includes
Answers to product-related questions
Help with reported bugs and issues
Guidance for included third-party assets
What support does not include
Customizations or new features
Installation or setup services
Plugin
Maintenance snapshot
See recent updates, compatibility, support, and developer activity.
Updated 92 days ago
Developer active
WPBay support available
WordPress 6.9 tested
Snapshot updated 1 second ago
View detailsHide details
Maintenance details
This is maintenance data. It does not measure product quality or sales.
Last updateUpdated 92 days ago
CompatibilityWordPress 6.9 tested, two versions behind · PHP 8.5 not marked as tested · WooCommerce 8 tested, three versions behind
Releases1 release in the last 12 months
Developer activityDeveloper active
SupportNo recent support tickets to measure
Docs and demoDocumentation available · Changelog missing · No demo listed
Health reflects recent activity during the last 90 days.
How this snapshot works
Plugin Health
The score is out of 100 and uses data WPBay can check. Ratings, popularity, and sales are not used.
Last update30 points
Plugins receive full recency points under 30 days, then step down at 90, 180, 365, and 545 days.
Compatibility20 points
WordPress, PHP, and WooCommerce (when relevant) are scored separately. The latest two PHP lines count as current. Nearby previous versions keep most of the points.
Current version100%
One version behind75%
Two versions behind50%
Three versions behind25%
Older or not listed0%
Releases15 points
One release earns 10, two or three earn 13, and four or more earn 15. Each accepted product ZIP counts once; reprocessing the same upload and listing-only edits do not count.
Developer activity15 points
Based on WPBay login and dashboard activity. Exact last-login dates are never shown.
Support15 points
There are no recent WPBay tickets to measure.
Docs and demo5 points
Documentation: 2. Changelog: 1. Working demo or preview: 2.
Score ranges
90–100 Excellent
75–89 Healthy
60–74 Fair
40–59 Needs attention
0–39 Limited
Long gaps
WPBay also checks for long gaps between updates, developer activity, support replies, and releases. Buyers do not see this score.
Reviews
There are no reviews yet.