Accept card, bank and digital wallet payments on your website. We help you choose a provider, configure the integration and test order payments. We can also replace your current gateway or fix payment errors.
Tell us your website, sales countries and required currencies. We will assess suitable options and explain what the integration needs. Processing fees and contract terms are set by the payment provider.
Choose payment methods that match your customers, currencies and products. We check availability with the selected provider before configuring the integration.
We check that the selected integration supports each required payment method. Features offered by one provider are not automatically available with another.
Visa and Mastercard where supported by the provider. We also check customer authentication and handling of the payment response.
Available banks depend on the provider and the customer’s country. We test the handoff to the bank and the return to your store.
Availability depends on the integration, market, device and browser. Where required, we configure domain registration or verification according to the provider’s requirements.
Subscriptions need a compatible payment provider and store setup. For custom API integrations, we review the documentation and business workflow first.
Add payments to an existing store, switch providers or build a custom integration. We review the current setup and agree the work before making changes.
For stores that already accept orders but do not yet offer online payment.
When the current provider lacks the methods you need or no longer fits your markets and requirements.
For payment flows that must connect to an external system or follow a specific business process.
Send your website address and a short description of the task. We will assess suitable payment integrations and any changes your store needs.
Your business signs the provider agreement and obtains the required access. We handle technical integration, testing and preparation for live payments.
Payment integrations include the agreed configuration and tests. Custom features and additional work are scoped separately.
WooCommerce version, theme, plugins and checkout type.
Payment methods, credentials and provider status notifications.
Successful, cancelled and failed payments, order statuses and notifications.
After testing and provider approval, agree how the live integration will be launched.
Provides the payment service, transaction processing and access.
Connects and configures the website integration and tests order payments.
We will assess available payment methods and your store’s technical requirements.
Answers about provider selection, costs, compatibility and testing payment integrations for WordPress and WooCommerce.
Yes. We start with your business registration country, customer markets, order currencies and required payment methods. We check suitable providers’ technical capabilities, store compatibility and contract terms before recommending an integration. Your chosen provider supplies the final fee offer and decides whether to approve the merchant account.
Your business signs the agreement, supplies the provider with its business and settlement details, and obtains the required access. WebDigital handles technical setup and website testing. Completing the integration does not replace merchant account approval: live payments can be enabled once the provider permits them and the technical prerequisites are met.
Yes. We first check the WooCommerce version, theme, existing plugins and checkout type. Payment integrations usually do not require rebuilding the entire store, although an outdated environment or custom checkout may need additional work. We confirm which methods will be available and how payment responses and order statuses will be handled.
Yes. We configure and test the new gateway, then agree the transition timing. We also review previous orders, possible refunds and subscriptions, which cannot always be transferred automatically to another provider. Before disabling the old integration, we clarify how your team should handle transactions that were already processed through it.
Yes, where the provider, your market and the integration support them. Wallet button availability can depend on the customer’s device, browser and eligible card. Some setups also require domain registration or verification. We test payment integrations in supported environments; the same wallet buttons cannot be guaranteed on every device.
No. WebDigital’s price covers the agreed technical integration. The provider sets transaction fees, subscriptions and other service charges. A paid plugin licence or custom development may also be required. Before starting, we identify known additional costs and explain which of them your business will need to pay separately.
We assess an API solution when a standard plugin cannot support the required workflow or payments must connect to an external system. First we review documentation, authentication, status notifications and the test environment. Error handling and maintenance are also scoped. An available API does not mean that every payment scenario is supported.
Send your website URL, chosen provider, required payment methods, countries and currencies. If something fails, explain the step where it happens and include the error text without credentials. Payment integration costs are determined after review: configuring a supported plugin and building a custom API connection involve different amounts of work.
We estimate the timeline after reviewing your website, provider and required features. A compatible ready-made plugin generally involves less work than a custom API solution. Merchant account approval and obtaining test access must also be considered. Before starting, we agree the technical schedule and identify which steps depend on the payment provider.
We test checkout, successful payments, cancellation, failure and the return to your store. We compare the provider’s transaction status with the WooCommerce order, emails and order amount. Refunds are checked where supported and included in the scope. Test orders may send emails and appear in store reports, so testing is planned rather than treated as invisible.
Yes. We compare the order with the provider’s transaction and check status notifications, logs and integration settings. Causes may include incorrect configuration, blocked notifications or a plugin conflict. An order status alone is not proof of the payment result: we establish what actually happened to the transaction first, then test subsequent status updates after the fix.
It depends on the gateway plugin and provider. Some integrations support initiating refunds in WooCommerce; others require the provider’s portal. We confirm full and partial refund capabilities and how they appear on the order. Refund conditions and any fees are set by the payment provider rather than WebDigital.
Yes, if the payment provider and the store’s subscription solution support the required workflow. We clarify payment frequency, renewals, cancellation and failed-payment handling. An additional plugin licence may be needed. When switching providers, existing subscriptions cannot be assumed to transfer automatically, so migration requirements are reviewed separately.
Yes. Changes to WooCommerce, the theme or the gateway plugin can affect checkout and status handling. Significant updates should be checked in a test environment first. Ongoing monitoring and maintenance can be agreed separately. At handover, we explain the key checks and the information needed to investigate a payment error later.
Testing starts before the handoff to the provider: the store must calculate the order total correctly. Agreed test scenarios include shipping charges, discount coupons and the store’s tax settings. We compare the amount shown at checkout, in the provider’s payment window and on the WooCommerce order. We also check what happens when a customer changes a shipping method or coupon before paying.
If your store uses multiple currencies, we scope the required currency and payment-method combinations. Payment integrations do not automatically fix incorrect shipping or pricing rules. If we identify a problem, we explain its impact and agree a separate fix. Tell us about special rules, such as free-shipping thresholds, customer-group prices or additional charges, so the test cases reflect the orders your store actually receives.
We check this before starting. A gateway plugin being installable does not establish compatibility with your particular checkout. We review the theme, checkout plugins, custom fields and custom code. Payment integrations can also be affected by rules that change available methods according to the delivery address, currency or customer group.
If the required combination is unsupported, we assess another plugin, a checkout adjustment or a custom integration. Before launch, we check the main screens on desktop and mobile: method selection, error messages, the return from the provider and order confirmation. Testing covers more than one successful transaction. We also scope cancellation and retry scenarios so customers can understand how to continue their purchase. The required adjustments and the devices covered by testing are agreed in advance.
For the initial enquiry, send only your website address and the task. Do not include passwords, API keys or customer card details. After agreeing the work, we confirm the required access to WordPress, the payment provider and a test environment where needed. Permissions are chosen according to the task. Test and live credentials should be kept separate to avoid using a test configuration for real transactions.
At handover, we explain where to check order and transaction statuses, which settings were configured and which functions the integration supports. We also clarify who to contact about a store error and when to contact the provider about the account or a transaction. Responsibility for future plugin updates and checks is agreed. Your business should retain control of its merchant account and settlement details. Ongoing maintenance can be scoped separately.
Documentation: troubleshooting WooCommerce payment errors
Tell us which payment methods you need or what should change. We will clarify the information required and the next steps.
