Title: Bancontact payment error
Last modified: June 8, 2026

---

# Bancontact payment error

 *  Resolved [Sean](https://wordpress.org/support/users/sean-h/)
 * (@sean-h)
 * [2 days, 9 hours ago](https://wordpress.org/support/topic/bancontact-payment-error/)
 * On my live WooCommerce store selling data only eSIMs, a customer paid with Bancontact(
   via the ING banking app). Stripe captured the payment successfully, the money
   arrived and showed on the card statement with no hold.
 * However, WooCommerce never marked the order as paid. The order stayed on Pending
   payment until I manually changed it to Completed.
 * After payment, Stripe tried to notify my site (webhook) and/or redirect the customer
   back. Both failed with a 500 internal server error.
 * The error was a PHP fatal in the WooCommerce Stripe plugin:
 * WC_Payment_Token_SEPA::set_fingerprint(): Argument #1 ($fingerprint) must be 
   of type string, null given
 * The stack trace shows this happened while handling a successful Bancontact checkout
   session, specifically in `handle_saving_payment_method` when the plugin tried
   to save the Bancontact payment as a SEPA token.
 * Important context
    - Test card payments (<code class=””>4242…) worked fine.
    - My first live payment used Bancontact and failed on this path.
    - A second live Visa payment (with itsme 3DS verification) worked end-to-end—
      order completed and eSIM provisioning ran automatically.
    - All plugins and WooCommerce were up to date at the time. They still are.
 * What should happen:
 * After a successful Bancontact payment, the customer should be redirected back
   to the site, the webhook should return 200, and the order should move to Processing/
   Completed automatically.
 * What actually happened:
 * Payment succeeded at Stripe, but the plugin crashed while saving the payment 
   method. The customer was not redirected back, the webhook returned 500 and the
   order stayed pending.
    -  This topic was modified 2 days, 9 hours ago by [Sean](https://wordpress.org/support/users/sean-h/).
      Reason: Grammar
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fbancontact-payment-error%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [shahzeen(woo-hc)](https://wordpress.org/support/users/shahzeenfarooq/)
 * (@shahzeenfarooq)
 * [2 days, 7 hours ago](https://wordpress.org/support/topic/bancontact-payment-error/#post-18932535)
 * Hi [@sean-h](https://wordpress.org/support/users/sean-h/)!
 * Thanks for sharing the details of the error and the stack trace.
 * I understand your concern this indicates an issue occurring while WooCommerce
   is trying to save a SEPA payment token during a Bancontact checkout flow, where
   a required value (fingerprint) is missing in the process.
 * To help investigate this properly, I’d like to understand your site properly.
   Please share with us the necessary information below for us to investigate the
   issue further:
    - **System Status Report** which you can find via WooCommerce > Status
 * Please use [https://pastebin.com/](https://pastebin.com/) or [https://gist.github.com/](https://gist.github.com/)
   and share a link to that paste in reply here. Once we have more information, 
   we’ll be able to assist you further
 *  Thread Starter [Sean](https://wordpress.org/support/users/sean-h/)
 * (@sean-h)
 * [2 days, 6 hours ago](https://wordpress.org/support/topic/bancontact-payment-error/#post-18932574)
 * I’m not comfortable posting a full System Status Report on a public support thread.
   The stack trace above should be enough for a Bancontact/SEPA fingerprint bug.
   While I would like to offer it, I’ve disabled Bancontact; no further action needed
   on my site at this time. Visa and Mastercard otherwise work fine.
    -  This reply was modified 2 days, 6 hours ago by [Sean](https://wordpress.org/support/users/sean-h/).
    -  This reply was modified 2 days, 6 hours ago by [Sean](https://wordpress.org/support/users/sean-h/).
      Reason: Context
 *  Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/)
 * (@frankremmy)
 * [1 day, 11 hours ago](https://wordpress.org/support/topic/bancontact-payment-error/#post-18933337)
 * Hi [@sean-h](https://wordpress.org/support/users/sean-h/),
 * Totally understood on the system status report. And you’re right, the stack trace
   is enough here. From what I see, the plugin was attempting to save the Bancontact
   payment as a SEPA Direct Debit token, and when Stripe’s response returned a null`
   fingerprint` for that token, it triggered the fatal error, crashed the webhook
   handler, and left the order pending.
 * This is a bug that was addressed long ago, so saving SEPA tokens for Bancontact(
   and iDEAL) is now disabled by default, preventing the plugin from hitting this
   code path entirely. If you re-enable Bancontact on an up-to-date version of the
   plugin and it keeps happening, it’d be worth looking into.
 * We’re sorry this happened on your first live Bancontact transaction. It’s a frustrating
   way to discover a bug. The payment itself was captured successfully by Stripe,
   which is at least the most important part. While switching to card payments works
   for you, we’re more than happy to investigate this.
 * I’ll be marking this thread as closed but if you ever change your mind, please
   share any Stripe-related entry and your system report securely via [https://quickforget.com/](https://quickforget.com/)
   and set it to view once or so.
 * Take care!
 *  Plugin Support [Thu P. a11n](https://wordpress.org/support/users/thup90/)
 * (@thup90)
 * [13 hours, 6 minutes ago](https://wordpress.org/support/topic/bancontact-payment-error/#post-18934341)
 * Hi [@sean-h](https://wordpress.org/support/users/sean-h/),
 * I’m reopening this thread, as I was able to replicate the issue with Bancontact
   that you reported, with Adaptive Pricing enabled. Thanks for taking the time 
   to share those details earlier, it made it much easier to narrow down and confirm
   what’s happening.
 * I’ve reported this to our developers for investigation, and we’ll keep you posted
   as soon as we have an update on progress or a fix.
 * Thank you for your patience while we’re working through this.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fbancontact-payment-error%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/woocommerce-gateway-stripe/assets/icon-256x256.png?rev=3177277)
 * [WooCommerce Stripe Payment Gateway](https://wordpress.org/plugins/woocommerce-gateway-stripe/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-gateway-stripe/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [Thu P. a11n](https://wordpress.org/support/users/thup90/)
 * Last activity: [13 hours, 6 minutes ago](https://wordpress.org/support/topic/bancontact-payment-error/#post-18934341)
 * Status: resolved