AlphaWebConnect Stripe
Connect your Stripe account to accept payments in AlphaWeb. Set up preview testing or live payments, choose your regions, and connect with a secret or restricted key.
You need access to your workspace's payment settings and permission to manage API keys in Stripe. For real payments, complete Stripe's account activation first.
Keep your keys private
Enter your secret or restricted key only in AlphaWeb's payment connection form. Keep it out of AI chats, screenshots and video recordings.
Open Stripe in your workspace
- Sign in to AlphaWeb and select the workspace you want to connect.
- Open Payments, then select Stripe.
- Keep Account details open while you get your keys from Stripe.
- If you cannot manage payments, ask a workspace owner to check your access.
- If your store is still being set up, you can save the account details now. Checkout setup finishes when the store is ready.
Choose preview testing or live payments
AlphaWeb keeps its Preview and Live connections separate. Connecting one does not configure the other.
Select Preview in AlphaWeb. In Stripe, select the sandbox or test environment you want to use.
Use a publishable key beginning with pk_test_ and a server key beginning with sk_test_ or rk_test_. Preview does not accept live keys.
Use both keys from the same Stripe account and the same sandbox or live environment.
Get your two Stripe keys
Open API keys in the Stripe Dashboard. You can also find this under Developers → API keys; some accounts show it under Workbench → API keys.
You need a publishable key and one server key. A restricted key replaces the secret key; you do not need all three.
A restricted key lets you choose which Stripe resources AlphaWeb can access.
- Copy the Publishable key for the selected account and environment.
- Choose Create restricted key, or edit a restricted key dedicated to AlphaWeb.
- Name it AlphaWeb and set the permissions below for the account you are connecting.
| Stripe resource | Access | Used for |
|---|---|---|
| Accounts (under Connect) | Read | Verify which Stripe account the key belongs to. |
| Payment Intents | Write | Create, confirm, capture and cancel payments, including renewal charges. |
| Customers | Write | Create the customer record used for saved payments. |
| Payment Methods | Write | Create and retrieve payment methods for checkout and future charges. |
| Setup Intents | Write | Set up payment methods for future use. |
| Payment Method Configurations | Read | Read the payment methods available to checkout. |
| Webhook Endpoints / Event Destinations | Write | Configure payment-event delivery to AlphaWeb. |
| Payment Method Domains | Write | Register and validate checkout domains for supported wallet payments. |
Include these permissions for the features you use:
| Stripe resource | Access | Used for |
|---|---|---|
| Charges and Refunds | Write | Issue and reconcile refunds through AlphaWeb. |
| Payment Disputes | Read | Retrieve dispute information. |
- Save or Apply changes and complete any verification Stripe requests.
- Copy the resulting
rk_test_orrk_live_key into AlphaWeb's Secret or restricted key field in the next step.
Stripe's labels can vary. Write includes read access. Follow the resource named in a Stripe permission error rather than granting every permission. See Stripe's restricted-key instructions.
Accounts: Read is required even for a valid key
AlphaWeb reads your Stripe account to verify its identity. A restricted key can be valid and still fail this check when Accounts → Read is missing. This permission allows reading Stripe account details, not only its ID; AlphaWeb does not need Accounts → Write for this check.
That is a restricted key, and AlphaWeb supports it. Use the restricted-key instructions above to configure its permissions. Paste it into Secret or restricted key, alongside your account's publishable key.
Paste each key into the matching field
Return to Payments → Stripe in AlphaWeb and check that you are still on the intended tab.
| AlphaWeb field | Paste here |
|---|---|
| Publishable key | Your pk_test_ or pk_live_ key. |
| Secret or restricted key | Your sk_test_, rk_test_, sk_live_ or rk_live_ key, in the same mode as the publishable key. |
Match the labels, not their order in Stripe. A webhook signing secret beginning with whsec_ does not belong in either field.
Choose regions and connect
- For the Live connection, select the regions where Stripe should appear under Enable in regions. This includes published-checkout testing with test keys. The Preview form has no region selector.
- Click Connect once and wait for the result.
- If setup is still finishing, use Refresh status to check progress.
AlphaWeb verifies the credentials and saves them securely. It configures the checkout connection and its webhooks as setup completes; you do not need to create webhook endpoints or paste a signing secret manually for this flow.
If your store is ready but the list is empty, create a region in your store Admin and return to Refresh status. If the page says regions are temporarily unavailable, refresh rather than creating duplicate regions.
Connected can appear with a message that checkout setup is still running or waiting for your store. Let that setup finish before testing payments. If the page reports an activation error, address it and use Retry connection. Re-enter keys only if the credentials need changing.
Check the connection before taking payments
- Confirm Connected, the expected Test mode or Live mode badge, and no remaining setup or error message.
- For a published checkout, confirm Stripe is enabled in the shopper's region.
- Test your checkout with test keys and Stripe's test payment details. Confirm the order and payment in AlphaWeb and the matching Stripe sandbox.
- If you sell subscriptions or use refunds, test those operations too. A successful connection or first payment alone does not prove every permission on a restricted key.
When you are ready for real payments, configure the Live connection with live keys and check the Live mode badge. Keep Preview on test keys.
Troubleshooting
For a restricted key, open its permissions in Stripe API keys and enable Accounts → Read under Connect. Save or Apply changes, complete Stripe's verification, then retry in AlphaWeb. Changing a dropdown without saving does not update the key.
Check for a revoked key, a partial copy or the wrong field. Use pk_ in Publishable key and sk_ or rk_ in Secret or restricted key. Both must come from the same account and environment. Do not share the key in a support message.
Both keys must contain _test_ or both must contain _live_. Preview requires test keys. For real payments, use the Live tab with the live pair.
A restricted key may allow account verification but lack access for a payment, webhook, refund or wallet domain. Check the denied resource in the key's View request logs in Stripe, update that permission, save, and retry. Use the permissions table above; avoid granting unrelated access.
Open the correct AlphaWeb workspace and payment tab, then choose Re-enter credentials. Submit the publishable key and replacement server key together. Wait for setup to finish and check the mode again. Preview and Live connections are updated separately.
Connect your Shopify store
Connect Shopify so AlphaWeb imports your products and orders. It takes about 10 minutes. You create an AlphaWeb app in your Shopify organization and paste its details into AlphaWeb.
Connect PayPal
Connect your PayPal Business account to AlphaWeb. Set up sandbox testing or live payments, and check the requirements for saved payments and automatic renewals.