A good checkout starts with the right payment setup.

Does an installed WooCommerce payment plugin automatically work in an app?

It depends on how the app checkout is implemented. A website gateway plugin provides a web integration. A separate Flutter checkout needs a supported path for creating a provider payment, presenting approval and confirming the final result.

WooApp uses dedicated Stripe and PayPal app adapters. They are configured under WooApp → Native payments and do not automatically reuse the website plugins’ credentials or private checkout handlers. Your existing website payment plugins can remain alongside them.

Cash on delivery follows WooCommerce’s own method and availability rules. This is a different setup from an online provider account, so it is useful to understand each method separately.

Cash on delivery: follow the store’s rules

Enable cash on delivery in WooCommerce → Settings → Payments. Review restrictions such as the allowed shipping methods and supported order types. A payment method should appear only when the cart and chosen delivery option are eligible.

The app displays the WooCommerce-calculated total. A COD confirmation does not mean the customer has paid online; it records an order that will be paid according to your store’s collection process.

If COD is missing, compare the same address, cart and shipping method on your website. Check the underlying WooCommerce method configuration rather than hardcoding a payment option in the Flutter interface.

Stripe: native card payment approval

The Stripe adapter creates a PaymentIntent on the server and supplies the app with the information needed for Stripe PaymentSheet. The app presents the payment interface, while the secret key remains on the WordPress server.

Your WooApp settings include the publishable key, secret key, environment mode and webhook signing secret. These values must belong to the intended provider environment. Your developer also keeps the app return URL consistent with the Android/iOS platform configuration.

For the merchant setup steps, use the Stripe section in the payment handbook. Stripe’s own PaymentIntents documentation explains the provider object used by the integration.

PayPal: approval followed by server capture

The PayPal adapter creates a provider order on the server. The app asks the customer to approve that order, then the backend coordinates capture and verification. Credentials include your client ID, client secret and webhook ID for the selected environment.

The native return configuration is part of the app identity. If your developer renames the application package or callback scheme, the related platform and provider settings need to stay aligned.

See the PayPal setup instructions and the provider’s Orders v2 reference for the corresponding account and API concepts.

Shipping, taxes and coupons still belong to WooCommerce

The payment choice comes after the store has calculated the relevant commerce values. An address determines eligible delivery options; the selected delivery method can change the final total. Coupons, fees and tax rules also contribute to the amount due.

WooApp presents those values in its bag and staged checkout. The backend compares the order and provider result instead of accepting an arbitrary amount supplied by the phone. This keeps pricing administration in the same store that manages the catalog.

Before introducing a custom checkout extension, check whether its fields and calculations have a supported app integration. Standard commerce rules and a website-only custom form are different requirements.

What happens if checkout is interrupted?

A closed approval screen or a network timeout can leave an existing order attempt that needs to be resumed. WooApp preserves an eligible retained checkout attempt so the customer can continue that flow instead of immediately creating another order.

Provider approval alone is not the complete order result. The server confirms the provider status and records the WooCommerce order state. Store owners should use the order notes and provider event references when investigating a payment question.

The browser showcase offers COD checkout. Stripe and PayPal approval belong to the Android/iOS app integrations, as described in the payment setup handbook.

Need another payment gateway for your WooCommerce app?

WooApp offers required gateway integration development at no extra charge. Share your provider’s official API/SDK documentation, country, currency, account requirements and intended checkout flow with Tqniyati. We will confirm technical feasibility and a delivery schedule. Provider account approval and transaction fees remain separate.

If you are choosing an overall app approach, compare native storefront and WebView checkout tradeoffs. If you are ready to implement, the Flutter source integration guide and store conversion guide cover the next steps.