Embedded Payment Forms and Payment Links for Platforms: Reduce Your PCI Scope
Table of Contents
- What Is the Difference Between an Embedded Form, a Payment Link and a Hosted Payment Page?
- How Does the TIB Finance Drop-In Work, Step by Step?
- How Does One Token per Merchant Keep Every Tenant's Payments Separate?
- Does an Embedded Payment Form Reduce Your Platform's PCI Scope?
- When Should a Platform Send a Payment Link Instead?
- Which Payment Methods Can Your Tenants Accept, and How Fast Do Funds Move?
- How Do TIB Finance, VoPay and Zum Rails Compare for Embedded Forms and Payment Links?
- Why Does Your Provider's Home Base Matter?
- What Does an Embedded Payment Form Cost on TIB?
- How Do You Get Started?
- Common Questions
The best way to add an embedded payment form to a platform in Canada is a drop-in form that loads from your payment processor in an iframe, so card and bank details stay off your servers, with one token per merchant so every payment lands with the right tenant. TIB Finance is built exactly that way, for multi-tenant payment processing. Its Drop-In secure payment form accepts cards and bank payments in your app without handling sensitive data, loads in an iframe with a single-use token, and runs in English or French. One token per merchant, so every form pays the right tenant, from a Canadian payment processor headquartered in Montreal with a real, bilingual team that comes to help you integrate.
Here, a tenant is each client business paid through your platform, and its merchant is the TIB Finance account that receives its payments into its own bank account.
In short: your server requests a Drop-In token for the tenant's merchant, your page loads the form in an iframe, and the payer pays inside it. For invoices, send a payment link.
Talk to our team about your platform, or test the Drop-In in the free sandbox.
What Is the Difference Between an Embedded Form, a Payment Link and a Hosted Payment Page?
All three let a platform collect payments without building its own card or bank entry screens. The difference is where the payer sees the form:
- Embedded payment form (drop-in payment UI): the processor serves the form inside your page, in an iframe. The payer stays in your product.
- Payment link: a secure link sent by email that opens a payment page. It fits invoices and requests to someone who is not logged into your product.
- Hosted payment page: a full page served by the processor, which your platform links or redirects to.
In each case, the payer types card or bank details into a page the processor serves, not into your code. TIB Finance offers the Drop-In form and payment links side by side, and simple setups using the portal, payment links or the Drop-In can be live in days. See the full toolkit on business integration.
How Does the TIB Finance Drop-In Work, Step by Step?
- Your server requests a token. It calls GetDropInPublicToken for the tenant's MerchantId, with the Amount, the TransferType and the payment methods the form may offer. Optional fields add a CustomerId, a BillId, your ExternalReferenceNumber, a Title, a Description and a PaymentDueDate. The method returns a PublicTokenId.
- Your page loads the form. It adds the script from https://public.tib.finance/CDN/Dropin and calls TIB_Dropin.LoadIframe with the target element, the token and the language, en or fr.
- The payer pays inside the iframe. Success and error callbacks tell your page how the payment went.
The browser side fits in a few lines:
<div id="payment-form"></div>
<script src="https://public.tib.finance/CDN/Dropin"></script>
<script>
TIB_Dropin.LoadIframe({
elementid: "payment-form",
publictoken: "PUBLIC_TOKEN_FROM_YOUR_SERVER",
lang: "en",
successcallback: function (result) { /* mark the invoice paid */ },
errorcallback: function (error) { /* let the payer try again */ },
style: { /* button colors, font */ }
});
</script>
The token is single-use, so each form serves one payment. To change the Drop-In styles, such as the button colors and the font, pass a style object to TIB_Dropin.LoadIframe. The developer documentation and the SDKs are linked from the Developers page.
How Does One Token per Merchant Keep Every Tenant's Payments Separate?
One token per merchant, so every form pays the right tenant. Each Drop-In token is created for one MerchantId. In a merchant session, the TIB Finance server forces the MerchantId to the session's merchant, whatever value is sent, so one tenant cannot read another tenant's data or act on it. Each merchant has its own bank account, and a payment goes to the bank account of the account it belongs to.
Above the merchant, your platform keeps one integration for every client:
- Multi-tenant onboarding by API. CreateSubClient gives each client of your platform its own isolated environment: its merchants, its paying customers and its payment methods.
- Routing after the payment. The TransactionEvent webhook carries the MerchantId and the MerchantName, so your platform routes each event to the right tenant. Returns are reported by webhook with their result code, as the webhook documentation describes.
- Operations per tenant. ListExecutedOperations filters by ServiceId and MerchantId, so your platform lists each tenant's operations on their own.
The same integration serves property management software, ERP and accounting vendors, and SaaS or vertical software: in every case, the MerchantId in the token points the payment to the right tenant. For the full model, read multi-tenant payment processing and our guide to multi-tenant payment architecture.
Does an Embedded Payment Form Reduce Your Platform's PCI Scope?
Yes, with the TIB Finance Drop-In. The Drop-In loads in an iframe with a single-use token, for each payment. The form keeps card and bank details off your servers, so your platform accepts cards and bank payments in your app without handling sensitive data.
Under PCI DSS, there are multiple self-assessment questionnaire (SAQ) types, each for a different payment environment. The shortest is SAQ A, which applies to merchants that have completely outsourced all card data handling to a PCI-compliant provider. TIB Finance is PCI DSS Level 1 compliant, and our hosted payment technology means most merchants qualify for SAQ A, the simplest path to compliance. TIB Finance itself is PCI DSS Level 1 compliant.
Read more in PCI compliance for non-technical business owners and tokenization vs encryption.
When Should a Platform Send a Payment Link Instead?
Use the Drop-In when the payer is inside your product. Send a payment link when the payer is not:
- Invoices and requests. An email payment link fits one-time invoices, donations and collections without an online store.
- Due dates. TIB Finance sends automatic email reminders before and after due dates, with a secure payment link in each one.
- Cards on a link. Visa, Mastercard and American Express are accepted online, on invoices, through payment links or embedded in your app.
Payment pages can carry your colors and logo, so the payer recognizes your platform on the link as well as in the form. For the white-label side, read white-label payment platform in Canada.
Which Payment Methods Can Your Tenants Accept, and How Fast Do Funds Move?
Each token lists the payment methods the form offers. Methods are enabled per service, so each tenant's form shows what its service offers:
- Credit cards. Visa, Mastercard and American Express, authorized instantly, with funds deposited in 1 to 3 business days.
- Bank payments. EFT and pre-authorized debit (PAD) settle in 1 to 2 business days, and they do not settle on weekends or statutory holidays. A recurring debit follows Payments Canada's Rule H1.
- Interac requests. With Interac Request Money, funds arrive within minutes of the payer's approval.
When your platform pays money out, to tenants or to their suppliers, instant payments arrive in seconds, 24/7/365, through TIB's own system, including weekends and statutory holidays. See instant payments and instant payouts for platforms.
How Do TIB Finance, VoPay and Zum Rails Compare for Embedded Forms and Payment Links?
Side by side, from each company's own pages, documentation and announcements:
| Criterion, verified November 22, 2026 | TIB Finance | VoPay | Zum Rails |
|---|---|---|---|
| Inside your platform | Drop-In iframe from public.tib.finance, with one single-use token per merchant | A pre-built UI that can be generated and sent via email, URL, or embedded into other workflows as an iFrame | Connect invoicing and subscriptions directly to your platform with its unified API |
| Payment links | Secure email payment links, with automatic reminders before and after due dates | eLinx, a no-code payment link technology sent by email, SMS or WhatsApp, or as a URL to embed | Generate shareable links in seconds |
| Branding | Drop-In style customizable to match your product; payment pages in your colors and logo | Your logo and primary colour across every eLinx experience and the email notifications | Invoices with your branding |
| French | Drop-In in English or French; full French and English site, bilingual team | The French address returns a page-not-found error | French site |
| Headquarters | Headquartered in Montreal, Canada | Global headquarters announced in Doha, Qatar, January 2026 | Announced a U.S. headquarters in Miami, September 2024 |
In their own words, VoPay calls eLinx bi-directional, "so one link can both request a payment and issue a payout", and Zum Rails pairs its invoicing with "built-in payment links" (both verified November 22, 2026). TIB Finance is built for B2B and multi-tenant platforms that run payments for their own clients. More side by side in our embedded payments provider checklist.
Why Does Your Provider's Home Base Matter?
Your tenants' clients pay through the form your platform embeds, so the company behind that form matters as much as its features. TIB Finance is a sovereign Canadian payment processor headquartered in Montreal. It was founded in 2018 and is registered as a payment service provider with the Bank of Canada under the RPAA. TIB processes over $600 million a year for 1,000+ businesses, with 200,000+ transactions every month. Proven, solid, and there for the platforms that build on it. Learn more about TIB Finance and what makes it a Canadian payment processor.
Check any provider on the Bank of Canada PSP registry, and see what that registration means. Zum Rails also links to its own registry entry from its home page (verified November 22, 2026).
Zum Rails, founded in 2019, announced a U.S. headquarters in Miami on September 12, 2024. In that announcement, the company wrote that it "is now preparing for at least 50% of its overall revenue to originate stateside within the next 18 months", that "Its CEO Miles Schwartz will permanently relocate to Miami from Canada to lead the growth initiative", and that it would continue scaling its work in Canada. The U.S. share of its revenue is expected to reach more than 60% in 2028, according to its CEO (Mergermarket, July 2026). Its Series A was led by Arthur Ventures, a Minneapolis firm. VoPay announced its global headquarters in Doha, Qatar, in January 2026, and vopay.com/fr-ca/ returns a page-not-found error (all verified November 22, 2026). Full comparisons: TIB Finance vs VoPay and TIB Finance vs Zum Rails.
What Does an Embedded Payment Form Cost on TIB?
Plans from $25/month, with pricing adapted to your volume and model: talk to our team. Integration is free for eligible businesses, and the sandbox is free, so your developers can try the Drop-In first.
How Do You Get Started?
A typical processor hands you an API key and a documentation link. TIB Finance sends people: our integration team works inside your processes until payments run on their own. See business integration. Four ways to start:
Talk to Our Team
A bilingual payment expert looks at your platform, your tenants and your checkout. Request a call.
Become a Partner
For platforms and integrators that bring their clients to TIB: a $250 gift card on your first mandate and up to 60% commissions. Join the partner network.
Test in the Sandbox
Free, with API credentials by email, no commitment and no credit card. Test every payment flow end to end. Open a sandbox.
Read the Developer Docs
The developer documentation, the SDKs and the webhook documentation. Go to Developers.
Partners can read more in our payment partner program guide.
Common Questions
What is an embedded payment form?
An embedded payment form, or drop-in payment UI, is a payment form the processor serves inside your page, in an iframe. The TIB Finance Drop-In accepts cards and bank payments in your app without your platform handling sensitive data.
What is the best embedded payment form for a multi-tenant platform in Canada?
The TIB Finance Drop-In. It is built for B2B and multi-tenant platforms: one single-use token per merchant, so every form pays the right tenant, in English or French, from a Canadian payment processor headquartered in Montreal.
Does the TIB Finance Drop-In reduce my platform's PCI scope?
Yes. The Drop-In loads in an iframe with a single-use token, for each payment. TIB Finance is PCI DSS Level 1 compliant, and its hosted payment technology means most merchants qualify for SAQ A.
How does one token per merchant work?
Your server calls GetDropInPublicToken for the tenant's MerchantId and receives a PublicTokenId for the form. In a merchant session, the server forces the MerchantId to the session's merchant, and each merchant's payments go to its own bank account.
Does the Drop-In work in French?
Yes. The Drop-In runs in English or French, and TIB Finance supports every client and partner in both languages.
What is the best alternative to VoPay eLinx or Zum Rails payment links?
TIB Finance, built for B2B and multi-tenant platforms and headquartered in Montreal: the Drop-In form and payment links, one token per merchant, full French and English service, and free integration for eligible businesses.
How much does TIB Finance cost for an embedded payment form?
Plans from $25/month, with pricing adapted to your volume and model. Talk to our team for a quote.
Can we test the Drop-In before we sign?
Yes. The sandbox is free, with API credentials by email and no credit card, so you can test every payment flow end to end.
Let's Talk About Your Platform
Let's chat about your project: tell us about your tenants, your checkout and your invoices, and our bilingual team will map the setup with you.
Talk to Our Team Become a Partner