Agiled Docs

Payment integrations let customers pay invoices, checkout links, storefronts, and paid bookings.

Connect payments before sending customer-facing payment links. A public invoice or checkout page can be shared without online payment, but customers will not see the expected online payment option until the gateway is active.

Providers

Stripe Connect
PayPal
Mollie

Where Payments Are Used

Public invoice payment pages
Checkout links
Storefront checkout
Paid scheduling events
Payment webhooks and payment status updates

Choose a Provider

Use Stripe Connect when Stripe is your primary payment processor. Use PayPal or Mollie when your customer region, currency, or finance process depends on those providers.

Confirm provider fees, supported currencies, payout timing, and account verification before making a gateway the default payment path.

Connect a Payment Provider

Open Settings.
Go to Finance.
Find the payment gateway section.
Connect Stripe or enter the required PayPal/Mollie credentials.
Save and confirm the gateway is active before sharing public payment links.

Before Connecting

Confirm the provider account is owned by the business, supports the currencies you use, and has payout, tax, and verification requirements completed. Also decide who can access the provider dashboard for disputes, refunds, and failed payment review.

Do not connect a personal or temporary provider account for live customer payments. Payouts, disputes, refunds, and tax records need business-owned access.

After connecting a provider, test the payment path with a safe document or checkout flow. Confirm the payment appears in Agiled and in the provider dashboard.

Test the exact surfaces your customers will use: invoice payment page, checkout link, storefront, or paid booking. A gateway can work for one flow while another flow has a missing currency, inactive product, or disabled payment method.

Operational Checks

After the first live payment, confirm invoice status, payment record, provider transaction, customer receipt, and any accounting handoff. Keep the provider dashboard available during launch so failed or pending payments can be diagnosed quickly.

For paid bookings and checkout links, also confirm the created appointment or order. A successful charge is not enough if the downstream record was not created correctly.

Launch Checklist

test every payment surface you will share
confirm provider live mode or production credentials
confirm webhook/status updates work
confirm refund and dispute ownership
confirm finance knows where to reconcile payouts

Add one real post-launch review after the first customer payment. Confirm the provider payout, Agiled record, customer receipt, and finance report all match.

Troubleshooting

If payment buttons are missing, check gateway connection, enabled methods, currency support, invoice status, and whether the public page is using the correct workspace.

If Agiled and the provider disagree on status, review webhooks, return URLs, provider dashboard events, and payment record history.

Do not record a manual payment just because a webhook is delayed. First compare the provider transaction, Agiled payment history, invoice balance, and customer receipt so duplicate payments are not created.

If a customer reports a charge but Agiled shows unpaid, verify the provider transaction before sending another payment request.

Payment Integrations