Skip to main content
Charge correlation lets resellers compare charge and refund data from their billing systems with the corresponding records held by DVM. Use the results to identify missing transactions and values that differ before starting reconciliation.

​
Send charge correlation data to DVM

Upload charge correlation files to the Amazon S3 bucket provided during onboarding. Files can cover daily, weekly, or monthly periods. The correlation process can receive either:
  • One file containing transactions across multiple content providers
  • Separate files for each payment gateway used by the reseller
Upload files to:
If a payment gateway cannot be identified, the transactions are placed under an Unknown folder.

​
File naming

Use the following naming convention:
Files must use RFC 4180 CSV format and UTF-8 encoding. Use UTC for timestamps.

​
Input file format

​
Correlation processing

DVM compares the following transaction values.

​
Correlation results

Each detailed output record contains the reseller values, the correlation result, and the corresponding DVM values where a matching DVM transaction exists. An OK result can be either an exact match or a match within an accepted date variance. Typical error reasons include:
  • Transaction missing from DVM
  • Extra transaction in DVM
  • Transaction type differs
  • Transaction identifier differs
  • Customer identifier differs
  • DVM user identifier differs
  • Offer or consumer offer identifier differs
  • Response code differs
  • Amount or currency differs
  • Billing period differs
  • External transaction or subscription identifier differs
  • Multiple differences

​
Output reports

Charge correlation produces three types of output.

​
Detailed files

Detailed files use:
{corr_result} can be Matched, Mismatched, BangoOnly, PartnerOnly, or All. Output is published to:

​
Summary files

Detailed summary files use:
Overall summary files use:
The summary reports include counts and rates for successful correlations, differences, partner-only transactions, and DVM-only transactions.

​
Output configuration

DVM correlation output can be configured to:
  • A single consolidated detailed output
  • Separate files by correlation result
  • Separate files by payment gateway
  • Partner-specific field mappings
  • Charge and refund status mappings
  • Delivery location
  • File splitting for large datasets
Configuration is agreed during onboarding and can be updated through Bango Support.

​
Next step

Use the correlation results to identify where transaction data differs, then follow the reconciliation process to investigate and correct the relevant data.