Choosing and connecting a payment provider
What the four providers offer, how a provider account connects to your workspace, and how to find out why payments stay pending.
Every provider is used the same way: buyers pay on the provider's hosted page, and the provider tells your workspace about the result through a signed webhook. You bring your own provider account; the money is paid into it directly.
Which provider?#
| Stripe | PayPal | Square | Authorize.net | |
|---|---|---|---|---|
| Cards | yes | yes | yes | yes |
| Buyer's PayPal balance | — | yes | — | — |
| US bank payments | ACH | (PayPal's own eCheck) | — | eCheck |
| Subscriptions | yes | yes | yes | yes (ARB) |
| Free trials | yes | yes | — | yes ($1 card check, voided) |
| Partial refunds | yes | yes | yes | after settlement |
| Fees shown in reports | yes | yes | yes | no |
| Disputes reported | yes | yes | yes | no (handle them in its Merchant Interface) |
Many stores offer Stripe or Square for cards plus PayPal for buyers who prefer it. Authorize.net suits merchants who already have a merchant account with a bank.
Connecting a provider, in short#
- Create the provider account and finish its verification (business details, bank account).
- In the provider's developer area, copy the API keys for test/sandbox first.
- Settings → Gateways → Add credential set, paste the keys.
- Register the webhook URL shown on the set at the provider, with the listed events, and paste the webhook value back into the set.
- Verify, then Put in service (Test). Bind the set to a product and make a test payment.
- Repeat with live/production keys when the test works.
Text description
The provider posts an event to /webhooks/provider.php with the credential set in the query string (Authorize.net: no query string; the set is found by its signature key). The signature is checked on the raw body before anything is parsed or stored; a bad signature is refused. The event id is recorded once, so duplicates are ignored. The object is fetched again from the provider's API. The state machine applies the change if it is allowed; a stale or out-of-order event is kept but not applied. Then emails, outbound webhooks and analytics follow. If processing fails the endpoint answers 500 and the provider retries.
Test and live sets#
Keep a test set and a live set per provider. Events from the provider are accepted only for payments made with a set of the same provider and the same mode, so the webhook secret of a test set, which developers often see, can never mark a live payment as paid. When you replace a set with a new one for the same provider account, renewals of older subscriptions that arrive at the new set's address still apply.
When payments stay pending#
A buyer paid but the payment stays Pending and the page keeps saying Confirming your payment…: the provider's webhook did not arrive or was refused.
- Open the payment's page. Under History, are there any provider events?
- Open the provider's webhook or event log for the endpoint. It shows each delivery and the answer it got.
- Match the answer:
| Symptom | Cause / fix |
|---|---|
| Set disabled, owners emailed | Three authentication failures: a key was rotated or revoked. Edit the set, paste the new key, verify. |
| Webhook log shows 400 Invalid signature | Wrong secret, key or webhook ID in the set; for Square, the subscription URL differs from the URL shown on the set. |
| Webhook log shows 503 | No webhook value in the set yet, or (PayPal) PayPal's verification API could not be reached. The provider retries. |
| Webhook log shows 409 (Authorize.net) | Two credential sets use the same Signature Key. Keep one set per account. |
| Payment stays Confirming… | No webhook arrived: check the endpoint in the provider dashboard and the events selected. |
| eCheck stays Processing | Normal until settlement (Authorize.net 1–3 business days). Super → Health & jobs shows payments.reconcile. |