Description
RevCent Payments connects WooCommerce to the RevCent payment service. A RevCent account and configured payment routing are required. Service and payment-processing charges may apply under your RevCent agreement.
- Accept card payments in classic WooCommerce checkout and Checkout Blocks.
- Use WooCommerce High-Performance Order Storage (HPOS) or legacy order storage.
- Connect FunnelKit one-click upsells to RevCent. Combined funnels update one pending sale and process it when the funnel completes; separate-order funnels use the saved card reference from the original purchase.
- View payment references and outcomes in WooCommerce order notes.
- Complete eligible interrupted orders from a saved payment approval without charging again.
- Optionally load RevCent DNS tracking for visitor attribution.
FunnelKit is a separate plugin and is not bundled. RevCent’s broader reporting, automation and account-management features are configured in RevCent; this plugin provides the payment and attribution connection described here.
Requirements
WordPress 6.8.12+, WooCommerce 10.4.4+ and PHP 7.4+ are required. Your installation must also meet the requirements of its chosen WordPress, WooCommerce and FunnelKit versions. Use a maintained PHP version supported by those products. Serve checkout over HTTPS.
External services and data
RevCent payment API: When a shopper submits a RevCent payment, accepts an eligible upsell, or an eligible pending payment or cancellation is processed, the store sends HTTPS requests to https://api.revcent.com/v2. Requests include the information needed for the operation: customer name, email, phone, billing and shipping addresses, IP address, order and product identifiers, quantities, amounts, currency, discounts, coupons, customer notes, and configured shop, campaign and payment-routing identifiers. Initial card payments send the entered card number, expiry and security code from the store server to RevCent. Later eligible payments can use a RevCent saved-card reference. Custom checkout extensions may add supported request fields.
The plugin stores payment references, attempt status and limited response details with the WooCommerce order for payment tracking and recovery. It does not save full card numbers or security codes in order metadata or plugin logs. The API key is held in the store’s gateway settings and used for server-side authentication.
Optional RevCent DNS tracking: This setting is off by default. When enabled, storefront pages load the service script from https://rctrk.<registered-domain>/trk.js; for example, shop.example.com uses https://rctrk.example.com/trk.js. DNS and HTTPS must first be configured for that hostname through RevCent. The plugin does not provision or verify them. The remote script supplies visitor tracking and attribution; loading it shares the visitor’s network and browser request information with the tracking service, and tracking can use cookies and browsing activity according to your RevCent configuration.
When present, the plugin includes the revcent_track_id, revcent_entry_id, revcent_google_click_id and revcent_kount_session_id cookie values in payment attribution metadata. Disabling the DNS Tracking setting stops this plugin loading the tracking script; it does not clear existing cookies or suppress attribution values already present. The plugin does not include a cookie-consent interface. Configure your store’s privacy notices and consent controls for the services you enable.
Support
For account configuration or payment review, contact RevCent. General service documentation is available in the RevCent Knowledge Base.
Include the plugin, WordPress, WooCommerce and FunnelKit versions, relevant order IDs, payment reference IDs, error wording, timestamps and steps already taken. Share payment details only through a private support channel. Never post API keys, full card numbers, security codes or customer information in public support forums.
Licenses
RevCent Payments is licensed under GPLv2 or later. The bundled country-code mapping retains its MIT copyright and permission notice in includes/country-alpha3.php. The Public Suffix List data retains its Mozilla Public License 2.0 notice and source information in includes/public-suffix-list.dat.
Installation
- Install and activate WooCommerce.
- Install RevCent Payments through Plugins > Add New, or upload the plugin ZIP through Plugins > Add New > Upload Plugin, then activate it.
- Open WooCommerce > Settings > Payments > RevCent Payments.
- Enter the RevCent API key, Third Party Shop ID and Campaign ID supplied for this store. Enter a Payment Profile ID if routing is not already configured for the shop in RevCent.
- Choose the checkout title and description, enable the gateway, and save the settings.
- If using FunnelKit, configure its RevCent gateway and chosen combined or separate-order funnel mode.
- Enable DNS Tracking only after the tracking hostname and your store’s privacy controls are configured.
- Verify your checkout and funnel configuration in a test environment before accepting customer payments.
Upgrading from 2.0.10
Pause new checkouts, finish or reconcile all active 2.0.10 funnels, and allow existing payment requests to finish before replacing the plugin.
Gateway settings are retained. New orders use the RevCent v2 API. Historical orders are preserved, but this version cannot resume their payments, upsells, cancellations or recovery actions automatically. Review unresolved historical orders in RevCent with support. Do not downgrade an active store containing new v2 orders to resume an old funnel.
FAQ
Do I need a RevCent account?
Yes. Contact RevCent to arrange an account and the payment-routing settings for your store.
Which checkout and upsell options are supported?
The plugin supports classic WooCommerce checkout, Checkout Blocks, and combined or separate-order FunnelKit one-click upsells. FunnelKit must be installed separately. Check your complete checkout configuration before enabling it for customers.
Does this plugin provide subscriptions, wallets or refunds?
This integration does not implement WooCommerce Subscriptions renewals, Apple Pay, Google Pay, WooCommerce automatic refunds or individual FunnelKit offer refunds. Contact RevCent support for refund handling and reconcile the corresponding WooCommerce order records.
What should I do if an order needs payment review?
Read the WooCommerce order notes and compare the payment references in RevCent. A timeout or missing response can mean that payment was already collected. Keep the order on hold and contact support before retrying, recreating the payment or marking the order paid.
Eligible orders offer “RevCent: complete order from saved approval (no new charge)” in the Order actions menu. This uses an approval already saved locally and makes no new API request. Completing the order can trigger normal WooCommerce stock, fulfillment and email integrations.
A definitive failure of the final combined payment may offer “RevCent: retry failed pending payment (attempts a charge)”. This makes another payment attempt against the existing pending sale using its existing payment details; it does not collect a different card. Use it only after reviewing the failure. See the bundled support-recovery.txt for the support procedure.
What happens when RevCent approves a reduced payment with salvage?
When your RevCent payment profile approves a reduced payment and creates salvage for the remaining balance, WooCommerce completes the order using that approval. The order total stays unchanged, and an order note records the reduced payment. RevCent handles the remaining balance through salvage; the plugin does not submit another checkout payment for it.
How are replacement offers handled?
For an offer charged only at the price difference, the original payment contributes to the replacement total even if FunnelKit cancels the original WooCommerce order locally. Review the linked orders and sales together; do not void that original payment independently. A full-price replacement instead requires successful cancellation of the original sale. Failed or uncertain cancellations and interrupted offer saves require support review.
Can I use DNS tracking on a subdomain?
Yes, when the registered domain’s tracking hostname is configured in RevCent. For example, both www.example.co.uk and shop.example.co.uk use https://rctrk.example.co.uk/trk.js. Private hosting tenant domains do not get separate tracking hostnames. Tracking cookies remain subject to browser and domain restrictions.
Changelog
3.0.2
- Fixed shipping method handling.
3.0.1
- Accept approved reduced payments with RevCent salvage during checkout and FunnelKit upsells.
- Support saved-approval recovery for these payments without charging again.
- Record the approved reduced amount in order notes while preserving payment identity checks and duplicate-payment protections.
3.0.0
- Migrate card checkout and FunnelKit pending sales to the RevCent v2 API.
- Preserve sale references across declines and prevent unsafe duplicate payment attempts.
- Keep combined funnel payments pending until completion and require a confirmed approval before marking orders paid.
- Add saved-approval order recovery and an explicit retry action for eligible failed combined payments.
- Hold uncertain payment outcomes, interrupted offer saves and conflicting responses for review.
- Preserve replacement payment credits and guard original-sale cancellations.
- Retain gateway settings and protect historical orders during the upgrade from 2.0.10.
- Resolve DNS tracking hostnames from registered domains using bundled public suffix data.
- Update compatibility metadata, merchant documentation and code formatting.
2.0.10
- Update plugin description.
- Fix WooFunnels compatibility with declared RevCent gateway settings.
- Replace deprecated FILTER_SANITIZE_STRING usage.
- Fix WooCommerce Blocks checkout script registration.
2.0.9
- Update code to prevent PHP deprecation warnings.
2.0.8
- Add asset images.
2.0.7
- Update readme.
2.0.6
- Update tags.
2.0.1
- Update latest WordPress tested version.
2.0.0
- Major Update: WooCommerce Blocks Support
- Added full WooCommerce Blocks checkout compatibility
- Implemented floating label payment forms with smooth animations
- Improved mobile layout and accessibility
- Added High-Performance Order Storage (HPOS) compatibility
- Improved payment field validation and formatting
- Enhanced error handling and user feedback
- Added support for dark mode and high contrast themes
- Streamlined admin settings
- Backward compatible – all existing settings preserved
1.6.5
- Updated plugin readme and compatibility information
- Classic checkout support and basic RevCent integration
- WooFunnels upsell compatibility
- DNS tracking support for visitor attribution
1.6.4
- Updated compatible WordPress and WooCommerce versions
- Performance improvements and bug fixes
Earlier Versions
- Initial plugin development and core payment processing
- Basic RevCent API integration
- Classic WooCommerce checkout support
