Skip to main content
The payment portal is the screen where your debtor sees what they owe and pays it. You reach it through a public URL that combines your company identifier with the end user identifier.
If you create debts or links through the API, you do not need to build this URL yourself: the paymentUrl field in the response already resolves to the portal (for debts it is also a deep link to that specific debt). This page is for when you want to build the link on your own, for example to send the user to their full portal instead of to a single debt.

​
The two formats

The portal accepts two equivalent formats. Both resolve to the same place; what changes is the prefix and the company identifier you use.
The slug is your company’s short name (for example, acme-corp). It matches the Alias field under Settings → Organization in the dashboard.Use it when you manage a single company and want readable, branded URLs.

​
URL components

​
Rules

Do not mix identifiers and prefixes. /s/ always takes the slug and /c/ always takes the companyCode. A companyCode behind /s/ will not resolve.
  • Case: the slug is lowercase. The companyCode is used exactly as assigned to you. The identifierValue may be case sensitive depending on how it was generated.
  • Separators: always use a forward slash (/) between components.
  • Domain: use app.tapipay.la. The www.tapipay.la and tapipay.la domains redirect there, so they work, but they add an unnecessary redirect hop (worth avoiding if you are going to embed the portal in an iframe).

​
Example

Both rows point to the same portal for the same end user:

​
Where the user lands

The portal base URL leads to the user’s list of debts. From there they choose what to pay and with which payment method.
If instead of the full portal you want to show only the payment methods or only autopay management inside your own site, use the SDK: Payment methods or Autopay management.