Skip to main content
You can show the payment portal inside your own site with an iframe, instead of sending the user to app.tapipay.la. The user sees their debts and pays without leaving your page.

​
Minimal iframe

That is all you need. The src follows the same structure as a payment link, so you can also identify your company by companyCode:

​
The attributes that matter

​
"payment"
Enables the Payment Request API inside the iframe, which is what wallet payment methods rely on. The SDK always sets it, so it is worth setting it on a hand-built iframe too for the same behavior.
​
number
The iframe does not resize itself. Pick a value that fits the longest list of debts you expect (700px is a reasonable starting point) or let the SDK handle the height, which it does automatically.
​
string
default:"100%"
With 100% the portal adapts to its container width. The portal is responsive: check how it looks on both mobile and desktop.

​
Iframe or SDK

The manual iframe is the simplest route, but the SDK handles things you do not get by hand:
Use the manual iframe if you want the full portal (debt list included) inside a static page. Use the SDK if you need to react to the payment from your code, if you are in a SPA, or if you want to show only the payment methods step.

​
Considerations

Use the app.tapipay.la domain in src. The www.tapipay.la and tapipay.la domains redirect there, and a redirect inside an iframe adds latency to the first render.
  • One iframe per user. The identifierValue in the src determines whose debts are shown. Build it on your server using the identifier of the user with the open session.
  • No credentials in src. The portal URL carries no tokens or API keys. Do not add yours: the portal is a public screen that resolves access from the identifier.