Integrations
Available via: Dashboard only
The Integrations section in Settings is where you connect Inflow to the tools you already run your business with. Each integration is independent — connect what you need, ignore the rest.
Available Integrations
| Integration | What it does | Where to set it up |
|---|---|---|
| Discord | Auto-assign roles to subscribers, send payment / subscription notifications to your server. | Discord Integration |
| Quaderno | Cross-border VAT, tax-compliant receipts, B2B reverse charge, structured tax reports. | Quaderno (Tax Compliance) |
| Shopify | Use Inflow as a payment method on your Shopify store. | Shopify Integration |
Apple Pay
Apple Pay on the web is offered both on Inflow's hosted checkout (used by payment links and subscription pages) and through the Inflow SDK when you embed the iframe card form on your own site. In both cases the same prerequisite applies: the domain that displays the Apple Pay button must be registered and verified with Apple by Inflow.
What gets stored on your account
Three independent flags determine whether your customers see the Apple Pay button:
| Flag | Meaning | How to change it |
|---|---|---|
applePayDomain | The exact hostname (e.g. checkout.yourbrand.com) that you want to display the Apple Pay button on. | You set it from Settings → Apple Pay. |
applePayDomainVerified | Apple has confirmed that the domain is yours. | Flips to true after a successful round-trip with Apple. Flips back to false if you change the domain. |
applePayEnabled | Inflow has enabled Apple Pay processing on your account. | Inflow-controlled. Once your domain is verified, contact support to flip this on after compliance review. |
The Apple Pay button is shown to your customers only when all three are satisfied (enabled=true, domainVerified=true, and the page hostname matches applePayDomain). The check also runs in the SDK iframe — see applepay-availability.js if you are debugging why the button does not appear.
How to register your domain
- Go to Settings → Apple Pay in your dashboard.
- Enter the domain that will host the Apple Pay button — typically the hostname of your checkout page or your storefront if you embed the SDK on your own site (e.g.
pay.yourbrand.com,checkout.yourbrand.com,shop.yourbrand.com). - Inflow tells Apple "this domain belongs to merchant X" via the underlying payment provider.
- Apple performs a callback to
https://yourdomain/.well-known/apple-developer-merchantid-domain-association— your site must serve the file Apple expects at that path. The file is provided to you during the Apple Pay onboarding kick-off; ask support if you don't have it. - Status flips to Verified once Apple confirms.
If verification fails, the dashboard shows Domain not verified with the most common cause being a missing or wrong apple-developer-merchantid-domain-association file. Re-host the file and retry.
Where Apple Pay shows up
- Hosted checkout (
checkout.inflowpay.com/pay/...): Apple Pay is automatic once your domain is verified and Apple Pay is enabled, no SDK integration needed. - SDK iframe: when you embed
<inflow-pay-card>on your domain, the iframe runs an availability check on load. The Apple Pay button appears next to the card form only if the customer is on Safari, on a device that supports Apple Pay, and the page hostname matches the verified domain. See Vanilla JS Integration and React Integration.
Multiple domains
Inflow stores one Apple Pay domain per merchant account today. If you need to support several distinct hostnames (e.g. one for checkout pages and one for embedded SDK), contact [email protected] — we add additional verified domains manually.
Webhooks
Webhooks are configured via the API rather than the Integrations page. See Setting Up Webhooks.
Coming Soon
If you need an integration that is not listed, contact [email protected] — we prioritize based on demand.
Updated 2 days ago