The withdrawal button: build it, test it, log it
Since 19 June 2026 section 356a BGB requires an electronic withdrawal function. Who is covered, what the two stages look like and what maintenance checks.
This is page 3 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
Since 19 June 2026 section 356a BGB requires an electronic withdrawal function. Who is covered, what the two stages look like and what maintenance checks.
After updates and imports snippets go missing, the fallback language kicks in and hreflang breaks. How to check and maintain your shop's language states.
Zero results, missing synonyms and a stale index cost orders. How shop search becomes a fixed, measurable part of ongoing maintenance instead of a side note.
Cron jobs and imports die quietly while the shop stays green. Set up heartbeat monitoring plus runtime and volume thresholds that catch half-finished runs.
Agencies build shops, then care slips. How white-label maintenance works: cooperation models, SLA boundaries, tenant separation and reports in your own brand.
When your current maintenance ends, the handover decides: secure the credentials, review the real state in 30 days and switch provider without shop downtime.
Database passwords and payment API keys often stay valid for years. Anchor secret rotation and leak monitoring as a fixed maintenance block in your shop.
DDoS attacks hit online shops when revenue peaks. Here is how managed protection keeps the shop reachable through the season – filters, capacity and alerting.
Automated bots test stolen card data at checkout. How to spot card testing early, stop it with monitoring and rate limiting, and avoid chargeback fees.