R
Docs
Troubleshooting

Payment issues — Stripe, PayPal, Swish

When checkout fails, this is where to start.

1 min read Updated 5/28/2026restaurant-owner

Card declined

Most declines are from the customer's bank, not Restora 360. Common causes:

  • Insufficient funds
  • 3D Secure challenge failed — the customer didn't complete the verify step
  • Card blocked by issuer — fraud rules; the customer needs to call their bank
  • AVS mismatch — billing address doesn't match the bank record

The customer sees a generic "Your card was declined" message. You see the specific Stripe decline reason in your Stripe dashboard → Payments.

Stripe says "not connected" or "incomplete"

Open Billing → Payment methods. If you see "Verification incomplete", click the link to finish Stripe's onboarding form. Stripe will tell you exactly which documents they need.

Until verification finishes, you can still accept payments, but Stripe holds payouts until cleared.

PayPal payments showing as "test"

Your PayPal client ID is still a sandbox value. Open Settings → Payment Methods → PayPal and replace the sandbox client ID with your live client ID (from your PayPal Developer dashboard).

Swish "transaction failed"

Swish requires the merchant's certificate to be uploaded. Open Settings → Payment Methods → Swish → re-upload the certificate (PKCS#12 .p12 file from Bankgirot).

Order shows "paid" in Stripe but "pending" in Restora 360

The Stripe webhook didn't reach Restora 360. Open your Stripe dashboard → Developers → Webhooks. Check the recent deliveries — any 5xx or 4xx? Click "Resend" on the failed events. Stripe also retries automatically for 3 days.

Frequently asked

  • In DEV mode (no Stripe key set), Restora 360 simulates payment intents. For real test mode, use Stripe's test cards (e.g. `4242 4242 4242 4242`).

Related articles