Wicker™

SECURITY AT WICKER™

Security at Wicker™

Effective October 29, 2026

Where we stand

Wicker™ runs on Amazon Web Services, often called AWS. Our server is running in test mode, and payments are not live yet. This page explains the safeguards already in place for that server and its cloud account.

Encrypted connections

Web traffic to our server is encrypted while it travels. If a connection starts without encryption, the server redirects it to the encrypted address. These protections apply while we test the service, too.

Checks before updates

Updates to the running server are installed automatically through our code review process. The update process uses temporary permission to connect to AWS, rather than a saved AWS access key. The software package for each update is scanned for known security problems before it goes live. Findings that remain open are recorded for follow-up, with a date to check them again. Our main code branches have rules against deletion and rewriting their history. Changes go through pull requests, where proposed edits can be checked, and the release process runs automated tests.

Limited developer access

The developer’s access to our live AWS account is view only. It allows the developer to check service health and read the server’s logs, but not change the service or read its stored secrets. The account requires registration of an extra sign-in check, called multi-factor authentication. Access sessions last one hour.

Protected keys and activity records

Our main encryption and sign-in token keys were created inside AWS and are stored in its secret-storage service. An infrastructure update was blocked when it tried to change protected resources, including these keys. The update rolled back, leaving the protection in place. We also keep records of changes to the AWS account through its cloud activity log. Those records cover cloud administration, not every action a shop or customer takes.

Handle payment details carefully

Do not send raw card data to our general API, logs or support channels. Keep full card numbers, card security codes, passwords and verification codes out of ordinary email and order notes. Before using a new payment method or device, confirm that it has been approved for your business.

Report a security concern

To report a suspected security problem, use security@wickerpay.com. Tell us what happened, which part of the service was involved and how we can reach you. Remove customer details and secrets from any screenshot before including it. Include the steps you took and what you expected to happen. Start with a short description, leaving passwords and private customer information out of the report. For questions about an order, refund or cancellation, contact the shop responsible for the purchase.