Import Mappers
Category:
Topics in this document:
- Where to Find Mappers
- Import Mapper Types
- Adding a New Import Mapper
- Example Use Case
- Available Tabs Overview
- Best Practices
Import mappers in Tridens Monetization allow you to transform and align external data (CSV, flat files, etc.) into system-compatible formats. Whether importing payment data, events, or bank transactions, import mappers ensure that the system correctly interprets and ingests structured data from external platforms.
Where to Find Mappers
Navigate to:Business Configuration > Import
Figure 1: Import Mappers default page
Import Mapper Types
At the top of the Import Mappers screen, you’ll find four tabs — each representing a different data domain. All tabs share the same configuration structure:
- Payment Mappers
- Direct Debit Mappers
- Event Mappers
- Bank Mappers
Each tab allows you to Add a new mapper using a form like the one shown in the screenshot.
Adding a New Import Mapper
Click the Add button in any of the four tabs to open the Create Mapper form. The fields you must complete are identical across all mapper types.
Required Fields
Table 1: Required Fields
| Field | Description |
|---|---|
| Name | A unique, descriptive name for the mapper (e.g. Bankart Payment Mapper) |
| Code | A system identifier used internally (e.g. BANKART_01) |
| Description | Optional. Add notes about the purpose or source of this mapper |
| Prefix | Optional. Used to append unique values during mapping |
| Import Mode | Defines the structure of the input file. Options: Single or Multi |
| Delimiter | File delimiter, typically comma ,, tab \t, or semicolon ; |
| File | Upload the mapping template file (usually CSV or TXT format) |
Figure 2: Create Import Mapper page
Example Use Case
You’re importing a CSV file from a payment provider (e.g. Stripe) that includes columns for transaction ID, customer ID, amount, and status.
You’ll create a Payment Mapper to align those columns with the fields expected in Tridens.
Available Tabs Overview
Each tab under Import Mappers accepts the same fields:
1. Payment Mappers
Used for importing raw transaction data from external payment systems.
2. Direct Debit Mappers
Maps debit order or mandate data from banks or PSPs.
3. Event Mappers
Imports events (e.g., usage events, triggers) that affect rating or charging logic.
4. Bank Mappers
Used for integrating imported bank statements or reconciliation files.
Best Practices
Info “Tip” - Use consistent naming conventions for codes and prefixes. - Always test your mapping file in a sandbox environment before production use. - Choose the correct delimiter based on your data source (CSV, TSV, etc.). - Keep backup copies of mapping templates and test files.
