New payment gateways: Mercado Pago, PayPal, Square and Adyen

Four online payment gateways in the bring-your-own-account (BYO) model, mirroring Stripe. You paste the credential in Settings, Integrations, enable it, and payment lands straight in YOUR gateway account. The webhook confirms the payment and, when linked to an invoice, settles it automatically. Encrypted credentials, no cost from us.

These gateways work like Stripe: you bring your own account (BYO). The money lands straight in YOUR gateway account, with no cost or middleman on our side. Open Settings, Integrations, find the card, paste the credential (always encrypted) and enable it. Until it is configured and enabled, nothing happens.

In all of them the webhook is what confirms the payment: copy the webhook URL from the card, register it in the gateway dashboard and paste the verification secret. When the payment is linked to a customer invoice, settlement is automatic (the invoice becomes paid or partial), through the same idempotent path as Stripe, with no double posting.

Mercado Pago

1. Paste the production access token (Your integrations, in the Mercado Pago dashboard).
2. Register a webhook for the card URL with the payments event and paste the webhook secret key.
3. Enable it. When a payment is confirmed, we fetch the real status and settle the linked invoice.

PayPal

1. Create a REST app (Developer Dashboard) and paste the Client ID and Secret; choose the environment (live or sandbox).
2. Register a webhook for the card URL and enter the Webhook ID (we use it to verify the signature).
3. Enable it. On a completed capture (PAYMENT.CAPTURE.COMPLETED), the payment is confirmed.

Square

1. Paste the access token and the location ID (Developer Dashboard) and choose the environment.
2. Register a webhook for the card URL with the payment.updated event and paste the signature key.
3. Enable it. A completed payment confirms the charge and settles the linked invoice.

Adyen

1. Paste the API key and the merchant account; in production also enter the live endpoint prefix.
2. Register a standard webhook for the card URL, turn on HMAC and paste the HMAC key.
3. Enable it. We verify the HMAC of each notification and, on a successful AUTHORISATION, confirm the payment.

None of these costs anything from us: the account and credentials are yours. If a webhook is rejected, check the webhook secret (a value different from the one stored in the CRM is rejected).

Open this article inside the system →