At the core of all of Pagos’ products is our data platform. Through this data platform, we ingest and normalize data from any of your data sources. A data source provides data around transaction events with standard data attributes (e.g. acquirers, payment service providers (PSPs), 3rd party fraud providers, etc).
As a Pagos customer, you simply have to connect your data sources—via our no-code set up or custom integration—and we’ll standardize your transactions data. Once standardized, we can use this data in many capacities, such as to power payment data visualizations in Peacock or event detection and monitoring in Canary.
If your payments stack uses more than one processor, you’re probably aware of how difficult it is to resolve each processor’s unique response codes into a common form. Standardization is the foundational capability that allows you to truly understand and analyze your data. With it, you can aggregate your data and get a full picture across all data sources. Without it, you must conduct separate analyses for each data source and then attempt to compare the results.
Data harmonization is necessary in payments data because many PSPs do not use the exact same data fields to express the same information. Harmonization is the process of integrating multiple data sources together to reduce variation and increase clarity. As an example, let’s take processor response codes for transaction status. There are many types of transaction response codes, so we’ll use an abbreviated set of common responses for simplicity’s sake.
Let’s take a look at a few examples where we map the related data fields together and create a standard Pagos code:
| Pagos Code ID | Short Description | Adyen | Braintree | Stripe |
| 1 | Approved and Successfully Completed | Code: 000 Status: approved Reason: approved or completed successfully | Code: 1000 Status: authorized or settled Reason: authorized, settled, or submitted for settlement | Code: NULL Status: succeeded or paid Reason: charge / transaction was successful |
| 6 | Do Not Honor | Code: 27 Status: refused Reason: the transaction was refused | Code: 06 Status: processor_declined Reason: error – do not retry, call issuer | Code: do_not_honor Status: failed Reason: this card has been declined for an unknown reason |
| 83 | Negative CAM, dCVV, iCVV, or CVV Result | Code: 24 Status: CVC declined Reason: the specified CVC is invalid | Code: 2082 Status: processor_declined Reason: card issuer declined CVV | Code: incorrect_cvc Status: failed Reason: the CVC number is incorrect |
Most data fields in transaction data face a similar issue as the above – either the data fields themselves need to be harmonized, the response code to a data field needs to be harmonized, or both. Pagos harmonizes all connected data sources so that your payments team can get to the analysis and operational optimization faster.
Only have one data source? Don’t worry – you can still benefit from the power of Peacock visualization and event detection and monitoring in Canary!
This harmonized data sits at the core of our unified data platform. And because this unified data platform supports all of our products, you’ll often hear us refer to Pagos as a platform of microservices!
Microservices—or microservice architecture—is a software architecture approach where applications are built as small, independent services. Microservices are generally organized by capability, loosely coupled, and independently deployable.
This type of architecture drives increased flexibility and customization for our customers. You can pick and choose which services work best for your business and add as needed. All services are supported by data harmonization services, but are uniquely deployed for your needs.
Check out the Pagos website to learn more about our suite of services.
