DahuConcept Deferred SEPA for WooCommerce

Description

Some customers are not charged when they order. A trade account on 30-day terms,
a wholesale buyer, a subscription-style arrangement: the mandate is signed, the
order ships, and the money is taken later.

Stripe charges a SEPA Direct Debit as soon as the order is placed. This plugin
adds a checkout option that does not. It reuses the mandate the customer has
already saved, records it on the order, puts the order on hold, and schedules
the real charge for a configurable number of days after the order is marked
Completed. Eight days by default, overridable per customer.

Who may pay late is decided by the shop, not by the customer. An
administrator names one of the customer’s saved IBANs as the active mandate on
their user profile. The customer must also have that same IBAN set as their own
default. Both halves have to agree, which is what stops a customer quietly
switching to an IBAN nobody approved.

What it does

• Deferred charging. Nothing is taken at checkout. The charge is scheduled
  automatically when the order is completed, using Action Scheduler.
• Move the date. The due date is shown on the order screen and can be moved
  until the moment it fires, with every move recorded.
• Charge now. A button to send the charge immediately, behind a capability
  check, a nonce and a confirmation.
• Charged once, whatever happens. A persistent idempotency key per order
  means a replayed scheduled action, a network timeout or a retry can never
  produce a second debit.
• Its own Stripe webhook. SEPA is asynchronous: a charge leaves as
  “processing” and succeeds or fails days later. A dedicated endpoint with its
  own signing secret listens for the outcome and for disputes, independently of
  the official Stripe plugin’s webhook.
• Per-customer terms. A delay set on a customer’s profile overrides the
  global one, for a trade account on different terms.
• A charges screen. WooCommerce → SEPA charges, with an Upcoming tab for
  expected cash and a History tab of every charge sent, filterable by date and
  outcome, sortable, and exportable to CSV.
• Optionally hides Stripe’s immediate SEPA option at checkout, while
  leaving it available under My account → Payment methods, where the customer
  signs the mandate in the first place.
• Nothing fails in silence. A refused charge is emailed to the shop, once,
  with the reason and never with a raw carrier response. A charge whose date
  has passed and which never ran is taken out of “upcoming”, listed at the top
  of the screen with what is in the way, and reported by a daily check: a
  deferred charge is the one payment path with no customer in front of a
  screen to find out it did not work. Nothing is ever retried automatically,
  because a charge that may already have been sent would be taken twice.
• Diagnostics. The gateway is deliberately hard to qualify for, so it can
  show an administrator each condition it checks and the answer, rather than
  leaving “why is it not showing?” to be guessed.
• HPOS and legacy order storage. Both, with no custom tables: everything is
  order meta.

What it needs

WooCommerce, and SEPA Direct Debit working at Stripe — in practice the official
WooCommerce Stripe Payment Gateway, which is what lets a customer sign and save
a mandate. This plugin does not replace it and does not take card payments.

The Stripe secret key can be this plugin’s own setting (a restricted key that
may only write PaymentIntents is enough) or borrowed from the official plugin’s
configuration.

Before you switch it on

A SEPA mandate carries obligations to the payer that are yours, not this
plugin’s. Depending on the mandate you use, you may owe the customer advance
notice of the date and amount of each debit. Deferring a charge changes that
date. Check what your mandate and your bank require before charging customers
on a delay, and tell your customers what to expect.

This plugin is not affiliated with or endorsed by Stripe.

External services

This plugin sends requests to Stripe (https://api.stripe.com), using the
Stripe API key you configure. Stripe is the payment processor that holds the
customer’s SEPA mandate and moves the money; without it the plugin has nothing
to charge.

What is sent, and when:

• When a deferred charge comes due — the order total and currency, the
  Stripe customer and payment-method identifiers already saved on the order, a
  description containing the order number and your site name, and metadata
  containing the order id, the order number and your site URL. This is the
  request that creates and confirms the payment.
• When resolving which Stripe customer owns a saved mandate — the
  payment-method identifier alone, read back to confirm its owner. The answer is
  cached so this is not repeated.

Nothing is sent for an order that is not being charged, and no request is made
unless a Stripe secret key is configured.

The plugin also receives requests from Stripe, at its own webhook endpoint,
telling it whether a charge succeeded, failed or was disputed. Those requests
are rejected unless they carry a valid signature for your webhook signing
secret.

Stripe’s terms: https://stripe.com/legal/ssa
Stripe’s privacy policy: https://stripe.com/privacy

This plugin is not affiliated with, endorsed by or sponsored by Stripe.