Module Merchant Accounts

Civic Platform and Citizen Access allow agencies to use module-level merchant accounts for processing payments. This means that if an agency has separate merchant accounts for its sub-agencies or departments (or "modules"), multiple fees for various modules within a shopping cart can be submitted to the appropriate module merchant accounts. An agency has the ability to:

  • Separately process payments in a shopping cart containing records from multiple departments (or multiple sub-agencies in a multi-agency environment)
  • Use a single payment provider for all transactions, even if each agency and sub-agency department may have its own merchant account
  • Prevent citizens from making cross-agency payments in multi-agency environments
  • Configure separate merchant accounts for each department in an agency (or sub-agency in Super Agency environments). Each department is permitted to have one merchant account for fee items and one merchant account for convenience fees. For example, an agency with 3 departments can have 3 merchant accounts for fee items and 3 merchant accounts for convenience fees.

The configurations required for module merchant accounts assume that the agency is using an ePayments adapter to process payment transactions for a merchant account used with Civic Platform and/or Citizen Access. For information about ePayments adapters, see the Civic Platform ePayments SDK Development Guide included in the Epay SDK zip package.