Troubleshooting

Module cannot be activated

If the activation of Stripe Payment fails with the following message, the module OXID Payment Base is not active:

Module "oe_payments_stripe_wallet" has unfulfilled dependencies in shop "1" and can not be activated.
"oe_payments_stripe_wallet" requires the following modules to be activated: "oe_payment_base"

Procedure

  1. Activate OXID Payment Base first:

    ./vendor/bin/oe-console oe:module:activate oe_payment_base
    
  2. Then activate Stripe Payment:

    ./vendor/bin/oe-console oe:module:activate oe_payments_stripe_wallet
    

In a shop with subshops, the dependency applies per subshop: activate OXID Payment Base in every subshop in which you want to use Stripe Payment.

Database tables are missing

If payment processes fail and the log contains a database error such as Table '…oe_payments_contract' doesn't exist, the database migrations of OXID Payment Base have not been run.

Procedure

  1. Run the migrations in the root directory of your eShop:

    ./vendor/bin/oe-eshop-db_migrate migrations:migrate
    
  2. Clear the cache:

    ./vendor/bin/oe-console oe:cache:clear
    

For more information, see installation, step “Run the database migrations”.

Raise the log level for troubleshooting

If payment processes with Stripe Payment are not working as expected, raise the log level to narrow down the cause.

Procedure

  1. Go to Extensions ‣ Modules ‣ Stripe Payment ‣ Settings.

  2. Under Logging, set Log level to Debug (all channels + frontend console).

  3. Make sure the checkbox Log webhooks is enabled.

  4. Save your settings.

  5. Reproduce the failing process.

Result

Stripe Payment writes log files with daily timestamps to the directory <root directory of your OXID eShop>/log/stripe/:

  • stripe_requests_YYYY-MM-DD.log – API requests and responses

  • stripe_webhooks_YYYY-MM-DD.log – incoming webhook calls from Stripe

  • stripe_events_YYYY-MM-DD.log – internal event processing

  • stripe_reconciliation_YYYY-MM-DD.log – results of order reconciliation (console command stripe:reconcile-oxpaid)

At the Debug level, the module additionally writes diagnostic messages to the browser console.

Note

Set the log level back to Normal (requests + reconciliation) once the problem is resolved, to keep the amount of stored data low.

For more information about the log levels, see Configure logging.

Fix webhook problems

If status notifications from Stripe are not arriving in your OXID eShop, check the webhook.

Procedure

  1. Go to Extensions ‣ Modules ‣ Stripe Payment ‣ Settings.

  2. Open the Webhooks section.

  3. Check whether the status Configured is shown next to the Webhook Endpoint field.

    If Not configured is shown, create the webhook (see Create webhook).

  4. If the webhook is configured but notifications still do not arrive, reset it:

    1. Select the button Clear all webhooks and confirm the prompt.

    2. Select the button Create webhooks.

    3. Save your settings.

Result

The webhook endpoint and its secret are regenerated, and the status Configured is shown next to the Webhook Endpoint again.

Important

After an update to version 3.5, activate the module once

As of version 3.5, the module stores the webhook secret separately for test mode and live mode. It takes over a secret from an older version once, when the module is activated.

If the module has not been reactivated after the update, your eShop rejects all webhook calls from Stripe. In this case, deactivate and activate the module once, or run the command ./vendor/bin/oe-console oe:module:activate oe_payments_stripe_wallet. Alternatively, choose Create webhooks.

Note

The button Clear all webhooks deletes the webhook endpoints registered for this shop on your Stripe platform account.

To record incoming webhook calls, enable the checkbox Log webhooks under Logging.