Monetization Web Docs | Tridens Technology – System Configuration

Docs: Taxation Gateways

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in Monetization, from the Menu, select System configuration, and click Taxation gateways.

Monetization supports two taxation gateways out-of-the-box, which are:

SureTax
Avalara

Note:

A customer can only use one taxation gateway provider at a time in Monetization. Using multiple taxation gateways simultaneously is not supported.

Information:

In Monetization, taxation occurs as soon as rating happens. For instance, suppose a customer calls for 100 minutes; once the call is rated, the configured taxation gateway is immediately called to get the tax rate.

SureTax

Suretax is a cloud-based tax calculation software provider that offers businesses a comprehensive platform for managing tax compliance processes.

To configure, click SureTax; insert your API key and company identifier. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with SureTax.

Note:

Clicking Test Connection will try a test request to the taxation gateway provider to confirm that the connection with the inserted keys is okay.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Avalara

Avalara is a cloud-based tax compliance software provider that offers businesses a comprehensive platform for managing tax compliance processes. Its solutions automate tax calculation, filing, and remittance, making it easy for businesses to comply with complex tax regulations.

To configure, click Avalara; insert your API key, company identifier, client ID, and client profile ID. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with SureTax.

Note:

Clicking Test Connection will try a test request to the taxation gateway provider to confirm that the connection with the inserted keys is okay.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Docs: Payment Gateways

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in Monetization, from the Menu, select System configuration, and click Payment gateways.

Monetization supports eight payment gateways out-of-the-box, which are:

Braintree
Authorize.Net
Paypal
Stripe
CyberSource
Bankart
Tranzila
Adyen

Note:

A customer can only use one payment gateway provider at a time in Monetization. Using multiple payment gateways simultaneously is not supported.

Information:

You can integrate with a custom third-party payment gateway provider in Monetization. For more information, see Custom payment gateway.

Braintree

Braintree provides businesses with an online merchant account and payment gateway to accept credit card payments, including Visa, MasterCard, Discover, American Express, JCB, and Diners.

To configure, click Braintree; insert your merchant ID, public key, and private key. In addition, choose the appropriate environment, whether sandbox (test) or production.

Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Braintree.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Authorize.Net

The Authorize.Net Payment Gateway can help you accept credit card payments quickly and affordably.

To configure, click Authorize.Net; insert your login ID and transaction key. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Braintree.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Paypal

PayPal is a technology company that offers online payment solutions to individuals and businesses worldwide. It provides a platform for sending and receiving payments securely, with support for various payment methods.

To configure, click Paypal; insert your client ID and client secret. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Paypal.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Stripe

Stripe is a technology company that provides a suite of payment APIs for businesses of all sizes. It enables businesses to accept and manage payments online, including credit card, Apple Pay, and Google Pay, among others.

To configure, click Stripe; insert your stripe API key. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Stripe.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

CyberSource

CyberSource is a payment management company that provides a range of services to help businesses process online payments securely and efficiently. It offers a suite of payment APIs that enable businesses to accept payments from multiple channels, including mobile, web, and point-of-sale systems.

To configure, click CyberSource; insert your merchant ID and key. Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with CyberSource.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Bankart

Bankart is a Slovenian payment processor that provides a range of services to banks and merchants in the European market. Their platform enables businesses to accept various payment methods, including debit and credit cards, contactless payments, and mobile payments, making it a comprehensive payment processing solution.

To configure, click Bankart; insert your API username and password, shared secret, and API key. In addition, choose the appropriate environment, whether sandbox (test) or production.

Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Bankart.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Tranzila

Tranzila is an Israeli payment gateway that provides businesses with an easy-to-use platform to process online payments. Their platform supports various payment methods, such as credit cards, PayPal, and Google Pay, making it a versatile solution for businesses of all sizes.

To configure, click Tranzila; insert your terminal, credit password, and API password. In addition, choose the appropriate environment, whether sandbox (test) or production.

Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with Tranzila.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Adyen

Adyen is a financial technology platform that provides end-to-end payments, data, and financial management in a single platform. It can offer a wide range of payment options for your business.

Custom payment gateway

The custom payment gateway allows you to integrate with a payment gateway that Monetization does not support out-of-the-box.

To configure, click Third Party; insert your URL and API key. To include some additional information that the third-party payment gateway needs, click Headers. The information should be in key-value pairs.

Note:

To learn how Monetization enables payment processing support for third-party payment providers not supported out-of-the-box or for cases where you decide to handle payment processing logic outside of Monetization via your integration processes, see Custom Payment Integration.

Use the Active toggle switch to activate/deactivate the configuration. Once activated and configured, Monetization can communicate with the payment gateway.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Docs: Custom Attributes

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in Monetization, from the Menu, select System configuration, and click Custom attributes. A paginated list of all custom attributes is shown in a tabular format.

Information:

You can filter for custom attributes by an entity.

Four actions/subpages can be performed/viewed under this section, namely:

Create a custom attribute
Details custom attribute page
Update custom attribute
Delete custom attribute

Create a custom attribute

Under custom attributes, to create a custom attribute, click Create new. Provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the Monetization API.

A custom attribute can have one out of four data types, which are:

Numeric (Number)
String (Text)
Boolean (True/False)
Datetime (Timestamp)

Note:

The data type specifies how the custom attribute will appear on the user interface in Monetization.

The entity specifies the object to which the custom attribute belongs.

Details custom attribute page

Under custom attributes, to see the full details of a custom attribute, click Details. It contains the following:

Name
Code
Data type
Entity
Mandatory
Included on invoice

Update custom attribute

Under custom attributes, to update a custom attribute, first, click Details; it shows the details of the custom attribute. Then to update, click Update.

Note:

All information filled out under the create a custom attribute section can be updated, except for the Code and Entity.

Delete custom attribute

Under custom attributes, to delete a custom attribute, click Delete.

Note:

Deleting a custom attribute already used in other parts of Monetization cannot be done. Every particular reference to the custom attribute first has to be deleted.

Docs: Notifications

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Notifications
Platforms
- Twilio
- Firebase (FCM)

To access this section in Monetization, from the Menu, select System configuration, and click Notifications.

Notifications

To access this section, click Notifications. A paginated list of all notifications is shown in a tabular format.

Four actions/subpages can be performed/viewed under this section, namely:

Create notification
Details notification page
Update notification
Delete notification

Create notification

Under notifications, to create a notification, click Create new. Provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the Monetization API.

Publishers are used for configuring what type of notification to be sent: SMS, push notification, URL, Email, and Log. It is also used to configure where the notification will be sent using Receivers.

To create a publisher, under Publishers, click Add publisher. The action and number of retries specify the type of notification that will be sent and how many times to resend in case of a failure—for instance, sending out an email that will resend three times, suppose it fails.

Information:

The template is configured in Monetization, under Business configuration Templates. For more information, see Template.

Note:

The URL action means the notification will be sent as an API request to the URL, while the Log action means the logging service will add a log entry whenever the notification is triggered.

Under each publisher are Receivers. The Receivers refers to where the notification will be sent. It can be a URL or a customer (if it is an email or SMS).

The Scope typifies what will trigger the notification, which can be that of subscription, billing, rating, or exporting.

Once a specific action from the scope occurs, you can add filtering options. To add a filter, under Filters, click Add filter.

Details notification page

Under notification, to see the full details of a notification, click Details. It contains the following information:

Name
Code
Action
Scope
Publishers
Filters (if any)

Update notification

Under notification, to update a notification, first, click Details; it shows the details of the notification. Then to update, click Update.

Information:

All information filled out under the create notification section can be updated except for the Code.

Delete notification

Under notification, to delete a notification, click Delete.

Platforms

To access this section, click Platforms.

This section shows different platforms that enable the delivery of notifications, which Monetization is integrated with. It includes Twilio for text messages and Firebase for push notifications.

Note:

You need to set up the services to use it in Monetization.

Twilio

Twilio is a cloud communication platform that provides businesses with a suite of APIs for building messaging, voice, and video communication applications. Its platform enables businesses to send text messages as notifications from Monetization.

To configure, click Twilio; insert your Client ID and Client secret.

Information:

Once configured, you can edit and delete the configuration. To delete, click Delete.

Firebase (FCM)

Firebase Cloud Messaging (FCM) provides a reliable and battery-efficient connection between your server and devices, allowing you to deliver and receive messages and notifications on iOS, Android, and the web at no cost.

Docs: CRM Integrations

Mon, 01 Jan 0001 00:00:00 +0000

Docs: ERP Integrations

Mon, 01 Jan 0001 00:00:00 +0000

Quickbooks Online

QuickBooks Online is a cloud-based accounting software that provides businesses with a platform to manage their financial processes, including invoicing, billing, and expense tracking. Its platform also includes features such as bank reconciliation and financial reporting, enabling businesses to streamline their accounting operations.

Xero

Xero is a cloud-based accounting software that provides businesses with a platform to manage their financial processes. Its platform also includes features such as bank reconciliation, payroll management, and financial reporting.

Create a Xero App

Go to the Xero Developer Portal and log in with your Xero account.
Navigate to the My Apps section and click on New App.
Fill in the required details (App name, company or application URL, Redirect URL, etc.).
- For App name set Tridens Monetization
- For the Integration Type choose Web app
- For Company or application URL please set https://<your-subdomain>.tridenstechnology.com
- For Redirect URI please set https://app.tridenstechnology.com/monetizaton/gw-erp/auth-exchange?erp-provider=xero&tenant=<your-subdomain>

Please note that this is set for your production environment. If you would like to use Xero on your sandbox environment please create separate organization in Xero and go to Xero Developer Portal, My Apps > Select Tridens Monetization > Configuration and click on Add Another URI and set it as https://app.tridenstechnology.com/monetizaton/gw-erp/auth-exchange?erp-provider=xero&tenant=<your-sandbox-subdomain>

Figure: Xero developer portal

Netsuite

NetSuite is a cloud-based enterprise resource planning (ERP) software that provides businesses with a suite of tools to manage their financial, accounting, inventory, and order management processes.

Docs: Automation

Mon, 01 Jan 0001 00:00:00 +0000

Zapier

Zapier is a web-based automation tool that enables businesses to connect various applications and automate repetitive tasks without coding or technical skills. Its platform offers a wide range of integrations with various web-based applications, such as Gmail, Slack, and Trello, among others.

Docs: Data Warehouses

Mon, 01 Jan 0001 00:00:00 +0000

The Tridens Monetization Data Warehouse Integration feature allows you to seamlessly export your subscription, billing, usage, and revenue data from Tridens to your preferred analytics platforms. This guide provides a clear roadmap for setting up and managing this integration, focusing on scalability for high-volume usage-based billing in industries like telecom, energy, and electric vehicles.

Topics on this Document

Introduction & Overview
Architecture & Components
Supported Data Sources & Targets
- 3.1 Tridens Data Sources
- 3.2 Target Data Warehouses
Data Modeling & Schema Mapping
- 4.1 Definition of Objects/Tables Exposed
- 4.2 Data Types Supported and Conversion Logic
Data Sync Modes & Strategies
Security, Authentication & Credentials
- 6.1 Credentials, Storage, Rotation
Permissions & Encryption
- 7.1 Permissions Required in Target Warehouse
- 7.2 Encryption in Transit SSL, TLS, Certificate Trust
Usage / Configuration Guide
- 8.1 Step by Step Setup for Datawarehouses
Limitations, Caveats, and Best Practices

1. Introduction & Overview

1.1 Purpose and Use Cases

The Tridens Monetization Data Warehouse Integration automates the extraction, transformation, and loading (ETL) of operational data from Tridens Monetization into customer-owned data warehouses. This enables advanced analytics, BI reporting, and machine learning workflows outside the native Tridens analytics module.

Key Use Cases:

Revenue Analytics: Sync subscription metrics (e.g., MRR, churn rates) for cohort analysis in SaaS or media companies.
Usage Pattern Insights: Load real-time IoT meter data (e.g., energy consumption) into PostgreSQL for predictive billing in utilities.
Compliance Reporting: Export audited billing records to MS SQL for IFRS15/ASC 606 reconciliation.
Custom Integrations: Feed anonymized usage events into dashboards via generic JDBC.

Data warehouse integration reduces manual exports (like CSV/API dumps), minimizes analytics latency, and supports schema evolution without downtime—critical for dynamic pricing models.

1.2 Supported Platforms

Supports direct connectors to the following targets, leveraging Tridens RESTful APIs and JDBC/ODBC standards:

Platform	Integration Type	Supported Deployments
Snowflake	Native connector via Snowpipe for staged loads	Account & warehouse-level
PostgreSQL	JDBC	On-prem, AWS RDS, GCP SQL
Microsoft SQL Server (MS SQL)	JDBC	Azure SQL, On-prem, Always Encrypted
MySQL	JDBC	AWS Aurora, GCP SQL, Self-hosted
Generic JDBC	Custom driver	Any JDBC-compliant data warehouse (e.g., BigQuery, Redshift)

1.3 Key Features

Incremental Syncs: Low-latency updates.
Schema Evolution: Handles field additions/removals automatically.
Scalability: Serverless execution, 1M+ events/day.

2. Architecture & Components

2.1 High-Level Architecture

The Data Warehouse Integration follows a modular ETL pipeline design:

Source (Tridens Monetization) → Integration Engine → Target Data Warehouse

This architecture ensures scalability, resilience, and low-latency data movement across Tridens services and supported data warehouses.

Architecture Overview

Source: Tridens Monetization microservices expose REST APIs and event logs for data extraction.
Integration Engine: The ETL process runs on AWS Lambda or Kubernetes Pods to extract, transform, and load data efficiently.
Target: Data warehouses like Snowflake, PostgreSQL, or MS SQL store structured analytics-ready data.

Architecture Diagram

2.2 Data Flow

Extract: Pull data from Tridens APIs.
Transform: Apply in-memory mappings to target data warehouse objects.
Load: Bulk upsert to target data warehouse with transaction boundaries.

2.3 Components/Modules Involved

Extractor: Tridens Monetization notifications.
Loader: Java-based JDBC handler using bulk operations.
Transformation Engine: Transforms DTOs to data warehouse compatible objects.

2.4 Data Flow / Pipeline Steps

Initialization: Validate config, acquire locks.
Extract: Fetch data from DTO and prepare for data warehouse structure.
Transform: Apply anonymization rules.
Validate: Schema and row-level checks.
Load: Transactional insert/update.
Commit: Update metadata and emit metrics.

3. Supported Data Sources & Targets

3.1 Tridens Data Sources

Extracts from core Tridens entities via REST APIs:

Entity	Description
Subscriptions	Plans, amendments, status
Usage Records	Metered events (e.g., calls, sms, data usage, energy)
Billing/Invoices	Charges, payments
Customers/Accounts	Hierarchies, balances

API Reference: Tridens API Documentation

3.2 Target Data Warehouses

Target	Min Version	Driver
Snowflake	N/A	Snowflake JDBC 3.13+
PostgreSQL	12	pgJDBC 42.5+
MS SQL	2019	MS JDBC 12.4+
MySQL	8.0	Connector/J 8.1+
Generic JDBC	N/A	Custom

4. Data Modeling & Schema Mapping

4.1 Definition of Objects / Tables Exposed

Tridens exposes over 17 core data tables.

Primary Tables:

Subscriptions
Balances
Events
Bills
Invoices
Payments
Customers
…

5. Data Sync Modes & Strategies

5.1 Data Frequency

Tridens Monetization provides real-time data delivery, leveraging event-driven architecture and change data capture (CDC) for near-instant updates.

Mechanism:

Notifications ensure sub-second latency.
Ideal for use cases such as:
- Real-time billing adjustments
- Fraud detection
- Instant customer insights

5.2 Handling Deletes, Updates, Inserts

Operation	Strategy
Inserts	New rows created with unique primary keys.
Updates	Performed via `MERGE` or `UPSERT` on primary key columns.
Deletes	Handled as soft deletes, depending on target warehouse support.

6. Security, Authentication & Credentials

6.1 Credentials Storage, Rotation, and Encryption

Security Mechanism	Description
Storage	Credentials stored on Tridens Monetization (encrypted)
Encryption	All payloads encrypted with AES-256 during transit and at rest.

7. Permissions

Minimal Access Required:

CREATE TABLE on schema
INSERT, UPDATE, DELETE on target tables

Role-Based Example:

GRANT USAGE ON DATABASE analytics_db TO ROLE tridens_role;
GRANT CREATE SCHEMA ON DATABASE analytics_db TO ROLE tridens_role;

8. Usage / Configuration Guide

8.1 Step-by-Step Setup for Data Warehouse

Navigate to System Configuration → Data Warehouse Integration.
Select your warehouse type (e.g., Snowflake).
Enter your JDBC/ODBC credentials and test the connection.
Save configuration.