Stripe Payments FAQ

Yes. eStoreware Stripe Payments includes sandbox/test mode for validating checkout before accepting live payments. When testing is complete, sandbox mode can be disabled and the store can use live Stripe API keys.

Yes. The plugin supports nopCommerce store-scope configuration. Each store can use its own Stripe keys, webhook signing secret, checkout mode, saved-card behavior, and related payment settings when override settings are enabled.

The plugin supports Embedded Card Fields and Stripe Hosted Checkout. Embedded Card Fields keep the customer inside nopCommerce checkout. Hosted Checkout redirects the customer to Stripe’s secure hosted payment page.

Yes. The transaction mode can be configured for authorize-only. This authorizes the customer’s payment method during checkout without capturing the funds until the admin captures the payment later.

The plugin supports configurable 3D Secure behavior, including automatic handling, requesting authentication when supported, or forcing a challenge when possible.

Yes. Store owners can enable saved cards for logged-in customers, decide whether successful new-card payments should be saved automatically, and control how saved cards are displayed at checkout.

Yes. Logged-in customers can select a saved Stripe payment method at checkout when saved cards are enabled.

Yes. Customers can choose a saved card or select Use a new card to enter different card details.

The plugin can display saved cards in a dropdown after the configured threshold. This keeps the checkout page clean when customers have multiple saved payment methods.

Yes. Customers can access saved payment methods from My Account and manage their stored Stripe payment methods, depending on the features enabled by the store.

If the order was already created in nopCommerce, the plugin can show a payment recovery page. The customer can resume secure payment instead of creating a duplicate order.

The customer receives a clear message explaining that authentication could not be completed. They can choose another saved card or enter a new payment method and try again.

Yes. Stripe transaction references can be associated with the nopCommerce order for traceability. Public screenshots should redact PaymentIntent IDs and other Stripe identifiers.

Authorize Only means the customer’s card is authorized during checkout, but funds are not captured immediately. The merchant can capture or void the authorization later.

Yes. Authorized orders can show a Capture button so the admin can collect the authorized funds when ready.

Yes. If the order should not be charged, the authorization can be voided from the admin order screen.

Yes. Captured payments can support refund and partial refund workflows from the nopCommerce admin order screen.

Yes. Order notes can show checkout processing, authorization, capture, webhook events, payment status changes, and order status changes.

Yes. The plugin includes recurring payment and renewal tools that can work with saved Stripe payment methods.

Yes. Customers can view recurring payment information, including subscription status, cycle details, next payment date, initial order details, and renewal card information when enabled.

Yes. Customers can add or update the default card used for future recurring renewals.

The dashboard can show total recurring payments, active records, paused records, needs-attention records, no-default-card records, inactive/canceled records, and completed records.

Yes. Admins can pause renewal processing until a specified UTC date/time and save an internal pause reason.

These tools allow admins to manually process one pending renewal or a batch of up to ten pending renewals. They are useful for testing and controlled renewal processing.

A webhook is a real-time message Stripe sends to the store when payment, refund, authorization, checkout session, or other payment activity occurs.

Webhooks help keep nopCommerce synchronized with Stripe after checkout. They can update payment state, create order notes, track failures, and support refund or capture-related activity.

The plugin configuration page provides the webhook endpoint URL. This URL should be added in Stripe Dashboard under Developers > Webhooks.

Recommended events include charge.refunded, charge.refund.updated, checkout.session.completed, checkout.session.expired, payment_intent.amount_capturable_updated, payment_intent.canceled, payment_intent.created, payment_intent.payment_failed, and payment_intent.succeeded.

200 OK means Stripe delivered the event and the store accepted it successfully. Stripe will not retry that delivery.

Yes. System logs can help identify webhook signature errors, server errors, ignored events, payment mapping issues, or Stripe API errors.

Upload the plugin package from the nopCommerce Local plugins page or deploy the plugin manually to the nopCommerce plugins folder, then reload or restart the application if required.

Check the nopCommerce Local plugins list and the Payment methods page to confirm that eStoreware Stripe Payments is installed, enabled, and configurable.

The eStoreware dashboard provides centralized access to eStoreware modules, including Stripe Payments, recurring payments, renewal tools, and related plugin features.

Yes. The plugin license should be activated or validated before final testing and production launch.

Yes. Sandbox mode is recommended for setup and testing before accepting live payments.

Test plugin installation, license activation, sandbox keys, webhook setup, connection test, checkout payment selection, saved cards, 3D Secure behavior, refunds, and recurring renewals if used.