Products
Pagos Customization: Built to Fit How You Already Work


Your payments setup is unique to your business. The tools and vendors you employ, the countries you operate within, the payment methods you accept, and even the data you pass with transactions depend entirely on the type of business you run and the KPIs you've set for yourself. It's easy to think your payments setup is too custom for a third-party tool, and you may instead choose to aggregate, harmonize, and analyze your payments data all on your own.
We understand how merchants can draw that conclusion, but there are two flaws in the logic. First, aggregating transaction event data and cost metrics across processors requires immense expertise, and payments are rarely a merchant’s core competency. When merchants build in-house solutions, they often end up settling for late or incomplete data, which means tracking fewer KPIs with less detail and identifying issues slower. Even well-resourced engineering teams struggle to keep pace with constantly shifting network rules and industry regulations.
The second flaw is simple: you're not too custom for Pagos.
Custom Data Ingestion
Regardless of the PSPs you employ, Pagos can ingest your comprehensive payments data and quickly harmonize it into a single clean and usable dataset, organized and enhanced down to the BIN level. This includes all the data you’d expect, such as transaction amount, decline reason code, and chargeback status, along with any additional fields you use to segment, monitor, and analyze your payment operations. If it’s information you care about, Pagos can ingest it and present it back to you.
Say you pass custom metadata or soft descriptors with your transactions; maybe you tag retry attempts so you can measure how they're performing, or attach a campaign ID to transactions coming from a specific marketing push. We pull that information in automatically through your existing data connections, and the context arrives in Pagos exactly as you sent it.
If you're not already passing that data, or you want to add more context after the fact, you can do just that with our Enrichment API. Most of what merchants add this way lives outside the transaction itself, including lifetime value, whether a customer has since canceled, or their original acquisition source. This internal data comes from your own systems directly into Pagos, where it sits right next to the payment it's tied to. For more examples of how to use the Pagos Enrichment API, check out this blog post.
You can then use built-in metadata and soft descriptor filters to segment your payments data in Pagos Insights by specific tags. The Custom Data dashboard even keeps a record of everything you've sent us, including plain-text descriptions, so the rest of your team knows what each field means without having to ask you.
Build Your Own Dimensions in Charts
The Charts section of Pagos Insights lets you segment and analyze your payments data however you need. Whether you need to see your transaction count broken down by processor and card brand across time, or a pie chart of your decline code mix across all accepted payment methods, you can build it in Charts.

Beyond the built-in dimensions available, we can help you build custom ones specific to your business, based on data you're already sending us. Turn any custom metadata field into a dimension, and unify it even when processors label it differently (e.g. one processor sends payment_channel and another sends processing_channel). You can even define your own categories of parameters within existing filters to match your internal structure; for example, sorting issuing banks into categories of “favorite” and “non-favorite.”

You'll work with your account manager to build these out, and each dimension supports up to 10,000 unique values, which covers nearly any way you need to slice your data.
Map Your MIDs Into Custom Hierarchies
Your payments data isn’t the only customizable aspect of Pagos; we can also tailor your Pagos account structure to match that of your business. If your MIDs are organized into separate brands or business units, for example, we'll help you build a custom MID hierarchy inside Pagos Insights. Once it's built, your team can filter the entire Pagos Service Panel down to just the MIDs tied to one business unit, and admins can restrict individual users to only the business units they need to see.
This is especially helpful when team members outside your payments organization need access to payments data. Instead of handing out processor login credentials or turning your team into a permanent go-between pulling reports on request, you can give them access to the right MIDs in Pagos and let them pull whatever they need on their own. Your payments team doesn’t need to be a bottleneck for the unbeatable context harmonized payments data can provide.
Your custom MID hierarchy can have up to two tiers; a global brand might use one tier for the brand and a second for country, for example. You'll work with your Pagos account manager to define both tiers, then map your MIDs into them in your account settings. From there, it’ll only take you a few clicks to go from viewing approval rate stats for Brand A in Brazil to a cost analysis of Brand B in France.
Custom Doesn't Mean DIY
The Pagos team has spent their careers untangling exactly the kind of bespoke payments stack you're worried won't fit. That expertise is baked into the features we just walked through, ensuring you always have a dataset that’s clean, harmonized, and tagged the way your business actually operates.
With trustworthy data comes the ability to navigate through curated dashboards in Pagos Insights to monitor and analyze your entire payments stack. That same dataset also powers something more direct: Pagos AI draws on it to answer your payments data questions in plain language. Ask about your fee breakdown last quarter or why approval rates dipped in a specific market segment, and you get an answer built on the same custom metadata, hierarchies, and dimensions you set up.
Better monitoring, sharper analysis, and real optimization are possible, and you don't have to build it yourself. You just have to configure it with Pagos. Contact us to get started.
By submitting, you are providing your consent for future communication in accordance with the Pagos Privacy Policy.

