OneFor<\/strong> payment services so customers can complete checkout payments and so your store can receive payment status updates.<\/p>\n\nWhat it is used for<\/strong><\/p>\n\n\n- Creating payment sessions when a customer chooses OneFor at WooCommerce checkout<\/li>\n
- Redirecting the customer to OneFor-hosted payment pages (card, QR code, or OneFor sign-in)<\/li>\n
- Verifying API credentials from the plugin settings page (Test connection<\/strong>)<\/li>\n
- Receiving server-to-server webhook notifications when OneFor reports a payment result<\/li>\n
- Processing refunds through the OneFor API when initiated from WooCommerce<\/li>\n<\/ul>\n\n
What data is sent, and when<\/strong><\/p>\n\n\n- When a customer pays:<\/strong> After checkout, your store sends the WooCommerce order ID, order total, currency (EUR), return URL, and merchant order reference to the OneFor API (
api.staging.app.onefor.com<\/code> or api.app.onefor.com<\/code>). If configured, your merchant account number is also sent. API requests are authenticated with the API username and password you enter in the plugin settings.<\/li>\n- When you click Test connection:<\/strong> Your API username and password are sent to the OneFor API to verify the connection.<\/li>\n
- When a refund is processed:<\/strong> The payment session ID is sent to the OneFor API.<\/li>\n
- On the OneFor payment pages:<\/strong> The customer completes payment on OneFor's website or app. Any card, account, or identity data entered there is handled by OneFor, not stored by this plugin.<\/li>\n
- Webhook (incoming):<\/strong> OneFor sends payment status updates to your WordPress site. The plugin does not send customer location or tracking data to OneFor.<\/li>\n<\/ul>\n\n
This plugin does not<\/strong> collect GPS location or track site visitors. It only communicates with OneFor when payment-related actions occur.<\/p>\n\nOneFor Terms of Service and Privacy Policy<\/strong><\/p>\n\n\n- Terms of Service:<\/strong> https:\/\/www.onefor.com\/web\/en\/legalDocuments<\/li>\n
- Privacy Policy:<\/strong> https:\/\/www.onefor.com\/web\/en\/privacyPolicy<\/li>\n
- Cookie policy: https:\/\/www.onefor.com\/web\/en\/cookiePolicy<\/li>\n
- Imprint: https:\/\/www.onefor.com\/web\/en\/imprint<\/li>\n
- Security & protection: https:\/\/www.onefor.com\/web\/en\/security-posts<\/li>\n
- Complaint policy: https:\/\/www.onefor.com\/web\/en\/compliantPolicy<\/li>\n<\/ul>\n\n\n
\n- Upload the plugin files to
\/wp-content\/plugins\/onefor-payment-gateway<\/code>, or install the plugin through the WordPress plugins screen.<\/li>\n- Activate the plugin through the Plugins<\/strong> screen in WordPress.<\/li>\n
- Go to OneFor - Payment Gateway<\/strong> in the WordPress admin menu.<\/li>\n
- Enter your OneFor API username and password.<\/li>\n
- Copy the webhook URL shown in settings and provide it to OneFor so they can notify your store when payments complete.<\/li>\n
- Set webhook key and webhook secret to match what OneFor configured for your merchant account.<\/li>\n
- Enable the gateway and save your settings.<\/li>\n
- Use Test connection<\/strong> to verify your API credentials before going live.<\/li>\n
- Switch from staging to production when you are ready.<\/li>\n<\/ol>\n\n\n
\nDo I need a OneFor merchant account?<\/h3><\/dt>\nYes. You need API credentials from OneFor before the gateway can create payment sessions.<\/p><\/dd>\n
Which currencies are supported?<\/h3><\/dt>\nOneFor currently supports EUR. The gateway is only available at checkout when your store currency is EUR.<\/p><\/dd>\n
How does the webhook work?<\/h3><\/dt>\nOneFor sends a server-to-server POST request to your store after a payment is processed. The plugin verifies the request using HTTP Basic Auth with your webhook key and secret, then updates the related WooCommerce order.<\/p><\/dd>\n
Does this work with WooCommerce blocks checkout?<\/h3><\/dt>\nYes. The plugin registers support for WooCommerce Checkout Blocks.<\/p><\/dd>\n
Can I test before going live?<\/h3><\/dt>\nYes. Enable staging mode in the plugin settings and use your OneFor sandbox credentials.<\/p><\/dd>\n\n<\/dl>\n\n\n
2.5.55<\/h4>\n\n\n- Renamed WooCommerce gateway classes to OneFor_ prefix for Plugin Check compliance; webhook URL unchanged.<\/li>\n<\/ul>\n\n
2.5.54<\/h4>\n\n\n- Improved admin onboarding guidance (signup\/support links + webhook setup steps) and fixed settings clearing behavior.<\/li>\n<\/ul>\n\n
2.5.53<\/h4>\n\n\n- Fixed card payment redirect URLs to use the same staging\/production hosts as QR and sign-in (app.onefor.com \/ staging.app.onefor.com)<\/li>\n<\/ul>\n\n
2.5.52<\/h4>\n\n\n- Equalized sidebar card spacing and moved credit card activation above OneFor support<\/li>\n<\/ul>\n\n
2.5.51<\/h4>\n\n\n- Removed phpcs.xml.dist from the plugin package (not permitted on WordPress.org)<\/li>\n
- Always show OneFor support contact details after a successful API connection; credit card activation note only when card is unavailable<\/li>\n<\/ul>\n\n
2.5.50<\/h4>\n\n\n- Fixed setup status badge and alert not updating after saving settings without a page refresh<\/li>\n<\/ul>\n\n
2.5.49<\/h4>\n\n\n- Added OneFor legal and privacy links to the admin settings sidebar; expanded readme legal links<\/li>\n<\/ul>\n\n
2.5.48<\/h4>\n\n\n- Documented OneFor external API usage, data transmission, and legal links in readme.txt<\/li>\n<\/ul>\n\n
2.5.47<\/h4>\n\n\n- Added PHPCS text domain configuration; removed hidden files from the distributable package<\/li>\n<\/ul>\n\n
2.5.46<\/h4>\n\n\n- Fixed PHP 8.2 dynamic property warnings and strengthened API URL migration on load<\/li>\n<\/ul>\n\n
2.5.45<\/h4>\n\n\n- Fixed API URL migration from corebaas hosts and improved test connection errors to show the full request URL<\/li>\n<\/ul>\n\n
2.5.44<\/h4>\n\n\n- Updated API base URLs to api.staging.app.onefor.com\/core and api.app.onefor.com\/core<\/li>\n<\/ul>\n\n
2.5.43<\/h4>\n\n\n- Restored checkout logo via standard WooCommerce gateway icon without custom HTML in the payment title<\/li>\n<\/ul>\n\n
2.5.42<\/h4>\n\n\n- Removed all checkout UI customization; payment method now uses plain WooCommerce title and description only<\/li>\n<\/ul>\n\n
2.5.41<\/h4>\n\n\n- Stopped checkout HTML from being stored on orders; admin order payment line now always shows plain text<\/li>\n<\/ul>\n\n
2.5.40<\/h4>\n\n\n- Fixed raw HTML showing in WooCommerce admin order payment details<\/li>\n<\/ul>\n\n
2.5.39<\/h4>\n\n\n- Fixed Plugin Check warning on legacy admin settings URL redirect<\/li>\n<\/ul>\n\n
2.5.38<\/h4>\n\n\n- Fixed WooCommerce settings link and legacy admin URL redirect for old onefor-epay-gateway page slug<\/li>\n
- Removed unused legacy payment-waiting assets<\/li>\n<\/ul>\n\n
2.5.37<\/h4>\n\n\n- Renamed main plugin file to onefor-payment-gateway.php to match the WordPress.org slug<\/li>\n<\/ul>\n\n
2.5.36<\/h4>\n\n\n- Plugin Check: fixed i18n translators comments, enqueued payment page assets, and WordPress 7.0 compatibility metadata<\/li>\n
- Raised minimum WordPress version to 6.1 for object cache group support<\/li>\n<\/ul>\n\n
2.5.35<\/h4>\n\n\n- WordPress.org: added License header and aligned text domain with plugin slug<\/li>\n<\/ul>\n\n
2.5.28<\/h4>\n\n\n- Fixed infinite recursion in checkout title filter that could cause a critical site error<\/li>\n<\/ul>\n\n
2.5.27<\/h4>\n\n\n- Fixed page scroll when the mouse is over the sticky admin sidebar<\/li>\n<\/ul>\n\n
2.5.26<\/h4>\n\n\n- Increased spacing between admin settings columns<\/li>\n<\/ul>\n\n
2.5.25<\/h4>\n\n\n- Sticky admin sidebar, improved payment method card layout, and spacing polish<\/li>\n<\/ul>\n\n
2.5.24<\/h4>\n\n\n- Improved checkout logo size and text alignment for classic and blocks checkout<\/li>\n<\/ul>\n\n
2.5.23<\/h4>\n\n\n- Security: added nonce verification for order status polling<\/li>\n
- Security: sanitized query string input and improved output escaping<\/li>\n
- Added readme.txt for WordPress.org submission<\/li>\n<\/ul>\n\n
2.5.22<\/h4>\n\n\n- Faster redirect after successful payment on the payment selection page<\/li>\n<\/ul>\n\n
2.5.21<\/h4>\n\n\n- Updated plugin display name to OneFor - Payment Gateway<\/li>\n<\/ul>\n\n
2.5.20<\/h4>\n\n\n- Fixed payment redirect URL format for QR and sign-in flows<\/li>\n<\/ul>\n\n
2.5.19<\/h4>\n\n\n- Updated session creation payload for OneFor API compatibility<\/li>\n<\/ul>\n\n
2.5.18<\/h4>\n\n\n- Test connection now uses the methods endpoint instead of creating a test session<\/li>\n<\/ul>\n\n
2.5.17<\/h4>\n\n\n- Removed webhook URL from session creation payload per OneFor API guidance<\/li>\n<\/ul>\n\n
2.5.0<\/h4>\n\n\n- Redesigned payment selection page<\/li>\n
- Webhook handling with Basic Auth<\/li>\n
- Staging and production environment support<\/li>\n<\/ul>","raw_excerpt":"Accept card, QR code, and OneFor sign-in payments in WooCommerce with staging and production support.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/327356","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=327356"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/onefor"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=327356"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=327356"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=327356"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=327356"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=327356"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=327356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}