Supplemental Data Ingestion for Payment Risk Platform

With Supplemental Data Ingestion you can send supplemental dispute data to Payment Risk Platform (PRP) to be leveraged for developing risk signals, building rules, and models. Data is sent through Secure File Transfer Protocol (SFTP) using the appropriate data schemas based on the use case.

Although PRP detects suspicious authorizations in real time, it may not have full insight into post-authorization data such as dispute details, customer risk data, or any of your internal data. Integrating external data with PRP can provide a more comprehensive understanding of your customers, the merchants they transact with, and their behavior. This expanded visibility enables the detection of more sophisticated risk signals, such as cardholder dispute rates and merchant fraud rates. Supplemental Data Ingestion is especially valuable if you have additional data outside of SoFi Tech Solutions and want to develop advanced risk signals to improve your fraud-detection capabilities.

Key benefits

By pushing more data to SoFi Tech Solutions through Supplemental Data Ingestion, you enable PRP to become a single source of truth for risk management. This allows you to:

• Build rules and generate risk signals — Develop advanced risk signals and build rules to gain deeper insight into account holder behavior, helping you identify risky patterns and anomalies.
• Protect cardholders with custom blacklists — Implement custom merchant blacklists to enhance cardholder protection.
• Improve machine-learning performance — Depending on the use case, your additional data may be used in SoFi Tech Solutions' proprietary machine-learning models, keeping them fresh and accurate to detect suspicious behavior. This also enables the potential to develop your own specific machine-learning models.
• Transaction GScore — If you leverage SoFi Tech Solutions' Transaction GScore, disputes data is a critical component for machine-learning model training and tuning, and providing this data establishes the complete feedback loop necessary for continuous model improvement.

Use cases

Currently, SoFi Tech Solutions specifically supports ingesting disputes data to PRP for clients who do not process disputes through SoFi Tech Solutions but utilize PRP. This provides a crucial feedback loop for authorization into PRP, capturing the complete lifecycle of customer spending. In the future, SoFi Tech Solutions will support other data sets such as customer risk profile, and merchant blacklist/whitelists, which can be utilized to develop features, rules, and models within PRP. If you have additional supplemental data use cases, contact SoFi Tech Solutions to help assess and support your needs on an ad-hoc basis.

Implementation

Contact SoFi Tech Solutions to set up Supplemental Data Ingestion for your program.

Setup for Supplemental Data Ingestion for PRP (Custom page)
This guide describes developer implementation for Supplemental Data Ingestion for Payment Risk Platform (PRP). For general information, see Supplemental Data Ingestion for PRP.

SFTP setup

Setting up the SFTP server and providing the necessary credentials generally takes 2–3 weeks. During this setup phase, SoFi Tech Solutions requires specific information from you for IP whitelisting, SSH keys, and file encryption details. We then provide you with the encryption public key, which you must use to encrypt your files. Once testing is complete, you can begin sending files to the production folder.

You will transfer your files to the /risk-dispute folder on the SFTP server.

📘

Note

SoFi Tech Solutions handles duplicate records by taking the latest records based on the timestamp you provide in the file.

Data requirements

You are responsible for adhering to the necessary schema and generating files correctly. Any issues in the data you provide may impact PRP's performance, and corrections to data may incur fees. To prevent issues, we recommend that you share a sample file with SoFi Tech Solutions for validation before you begin pushing actual data to the SFTP server.

File format

You must adhere to a precise file naming convention: [yourname]-disputes-YYYY-MM-DD-hh-mm-ss.csv. The YYYY-MM-DD-hh-mm-ss portion represents the date and time the file was created. This timestamp helps SoFi Tech Solutions track data and investigate any future errors. All files you transfer must be CSV files with a .gpg security extension.

🚧

Warning

Only CSV files are supported for data ingestion.

Data schema

The specific data schema can vary by use case, so ask your SoFi Tech Solutions representative for the exact schema relevant to your implementation. For the dispute data use case, your CSV files will include various fields, each with specific requirements for source, data type, and format. Each field specifies its source (whether you or SoFi Tech Solutions' RDF provides the value), data type, a description of its purpose and content, whether it is required or optional, and example values.

Standard dispute reasons

These are the valid values for the dispute_reason field. String length is up to 50 characters

Standard resolution status mapping

When submitting a resolution value, align your internal resolution statuses with SoFi Tech Solutions' standard values. Use the table below to map 3rd-party dispute processor resolution values to SoFi Tech Solutions terminology.