Skip to main content
Site Store Pro ships with four payment processors ready to activate. You select one as your primary gateway, toggle between sandbox and production modes, and register webhook endpoints so the gateway can push real-time payment events back to your store. Navigate to Admin → Checkout → Processors (/admin/ecommerce/checkout-processors) to get started.

Built-In Processors


Configuring Your Gateway

1

Navigate to Checkout Processors

Go to Admin → Checkout → Processors (/admin/ecommerce/checkout-processors).
2

Add your credentials to .env

Before activating a live gateway, add the required API keys to your .env file. Refer to your gateway dashboard for the correct key values.
3

Select your primary gateway

Click the processor you want to use and select it as the Primary Payment Gateway.
4

Set the operating mode

Toggle between Production and Sandbox / Test Mode. Start in sandbox mode to validate your integration before taking live payments.
5

Save and test

Save your settings and place a test order to confirm the checkout flow is working end-to-end.
Keep your gateway in Sandbox / Test Mode until you have verified the full checkout and webhook flow with test transactions. Switching to Production with unverified webhooks can result in missed order status updates and unprocessed subscription events.

Webhook Endpoints

Register the webhook endpoints below in each gateway’s developer dashboard. Webhooks allow the gateway to notify Site Store Pro when payments succeed, fail, or are refunded — keeping your order records accurate without polling.
Register your webhook endpoints in the gateway dashboard before going live. Without active webhooks, Site Store Pro cannot automatically update order statuses for asynchronous payment events such as delayed captures, refunds, or subscription renewals.
Webhook endpoint to register:
Required events to enable in the Stripe dashboard:Add the webhook in your Stripe dashboard under Developers → Webhooks → Add endpoint. Copy your Webhook Signing Secret and add it to your .env as STRIPE_WEBHOOK_SECRET.