How can we help?

Confirm the intended Stripe account and environment before reviewing its ShopTill-e method. An Active method and a saved credential do not establish that a payment completed.

Prepare the Stripe account

1. If you do not have the intended business account, follow Stripe’s account-setup instructions and use its official registration route.
2. Complete the requested business verification directly with Stripe. Account creation and activation for live services are separate stages.
3. Check the account’s business identity and the environment you intend to use. A provider sandbox is separate from live resources; confirm the ShopTill-e integration supports the agreed test setup.
4. Review the fees, payout arrangements and any outstanding account requirements in your own provider account before advertising the payment option.

Do not assume registration gives instant live acceptance or a fixed payout schedule. Keep account verification documents and private credentials out of support screenshots and messages.

Review Builder’s fields

1. Open Payment Methods and the intended Stripe method, or follow the add-method guide if none exists.
2. Review Display title.
3. Identify the fields labelled Secret key and Publishable Key. Confirm the credential types and permissions supported by this integration before an intended update.
4. Review Enable 3D Secure payments and Always use 3D Secure check separately.
5. Review Active and use Save changes only for the intended setup, then reopen it and check the result.

Test and live are different

Stripe’s current API-key guidance distinguishes publishable keys from private server-side credentials and separates test/sandbox resources from live resources. A webhook signing secret is a different credential. Confirm the environment and compatible key configuration; do not mix keys or paste a webhook secret into an API-key field.

Authentication is not a payment guarantee

Before changing either 3D Secure choice, confirm with support how it applies to your checkout and plan a controlled test in the appropriate provider test environment. Stripe’s 3DS guidance explains mandatory authentication and states that successful authentication does not guarantee liability shift for every payment or dispute. A checkbox selection alone does not establish the authentication or dispute protection for a particular payment. Check the actual payment and authentication details in Stripe when investigating an outcome.

Review card-code and postcode checks

CVC is the card security-code check; address verification can include the billing postcode. These checks are separate from 3D Secure. Stripe explains that an issuer can approve a payment even when a card-code or address check fails, and its available Radar rules can differ between accounts. See Stripe’s current fraud-prevention rules.

1. Confirm the intended Stripe account and environment before reviewing its rules.
2. Use Stripe’s current documentation to identify the applicable CVC/postcode rules. Read the actual payment’s check results as well as its payment status; a missing or unsupported check is not the same as a failed check.
3. Review an intended rule change with the person responsible for payment risk and the supported ShopTill-e integration. Check its effect in the agreed test environment before relying on it for trading.

If a payment is blocked or unclear, keep its reference and exact result for support. Do not treat a successful authentication or a checkbox label as confirmation of every card check.

Verify before normal operation

Use an authorised provider test environment to check success, decline, authentication success/cancel/failure, return handling and the resulting order/provider references. Reconcile actual payment status before another attempt after a lost response. Review current fees, settlement schedule and account eligibility in the merchant’s actual provider terms.

If the method fails

Keep the storefront, order/provider reference, stage, time and exact message for support. Do not include secret keys or full card details. A status correction in Builder is not a substitute for checking Stripe’s actual outcome.

Method setup · Find the order.