The merchant uses its own Stripe account
A US store configures its own Stripe publishable key, secret key and webhook signing secret. Tiendli does not pool merchant funds into a shared seller account.
Stripe account eligibility, payment methods, settlement and processing fees are governed by Stripe and the merchant account.
Card details stay on Stripe-hosted Checkout
The buyer is redirected to Checkout to enter payment details. Tiendli does not need to collect or store card numbers or CVC data in this flow.
After payment, Stripe sends a server webhook to Tiendli.
The webhook is what confirms the order
Tiendli validates the Stripe webhook signature and checks the internal order reference, USD currency and exact order amount before marking the order paid.
A browser success URL alone never changes payment status. This prevents a buyer from faking a successful return URL.
Test before switching to live keys
Use test-mode keys and a test webhook endpoint configuration first. Run successful, cancelled and mismatched-order scenarios before enabling live mode.
When switching modes, all keys must belong to the same Stripe environment.
Related guides
View all →Frequently asked questions
Does Tiendli store my Stripe secret key in the browser?
No. Secret keys and webhook signing secrets are stored server-side and are redacted from the merchant-facing API after saving.
Can the success page mark an order paid?
No. Tiendli confirms payment only from a valid signed Stripe webhook that matches the expected order, amount and currency.
Does Tiendli decide Stripe processing fees?
No. Stripe processing fees and settlement conditions belong to Stripe and the merchant account.
Sources
Turn this guide into a real online store
Create your Tiendli store, publish your catalog and start with the Free plan in United States.
Create my store free