In issuing environment we need to account for:

  1. Transaction data
  2. Cardholder information
  3. Account details
  4. Network (schema / association)
  5. Correspondence
  6. Miscellaneous

Transaction data

Every dispute begins with the selection of a transaction (or multiple). Lean has over the years developed an understanding of how various transaction warehouses supply information, in fact we even partner with a company that supplies them (ACI Worldwide). Whether we work utilize an intermediate Enterprise Service Hub or connect directly with a transaction warehouse, we ensure that every analyst (and logical algorithm) has the critical details they need to make decisions.

Cardholder information

Disputes wouldn’t exist if it weren’t for cardholders, Lean uses your cardholder detail storage systems to gather names, addresses, emails and phone numbers to give analysts the necessary information to contact a cardholder or allow our automated correspondence systems to generate documents with appropriate information to route them accurately to the cardholder.

Account details

AdjustmentHub you to automatically take care of credits, and debits to a cardholder account. Of course, the off-setting suspense accounts / general ledger accounts will be notified to balance finances.

Network (schema / association)

As an issuer, you are you are gathering the relevant network data required to create a formal dispute with the network. That means combining the required data as well as the network specific reason codes. AdjustmentHub allows you to do this automatically to save significant amount of time.


Correspondence to a cardholder can be issued and received in several ways, be it mail, email, through a card holder’s online or mobile account, notifications via SMS or mobile applications. In order to communicate efficiently, AdjustmentHub will interface with your enterprise communication tools and document warehouses.


This is a rather odd interface! But one thing we’ve learned is that every issuing bank has unique systems and internal requirements for their needs, and as a result you may have certain systems that need reporting to (e.g. for fraud) or reporting from (e.g. for fraud!) or whatever it maybe. The point is, we understand we might not have covered everything in the list above, but rest assured, we won’t leave any stone unturned.