Payment Service

The Payment Service delivers messages between MATRIXX Charging Application and a Payment Gateway Provider. Messages include authorization requests and responses. Authorization requests include the current subscriber or group payment token.

Each client that uses Pay Now has different requirements based on each Payment Gateway Provider that it supports. Client developers should contact MATRIXX Support for information specific to their client implementation.

The Payment Service communicates with the following components:

  • MATRIXX Charging Application — The Payment Service receives payment authorization and settlement requests from MATRIXX Charging Application, transforms the messages, and sends them to the Payment Gateway Provider through the Payment Gateway Adapter.
  • Payment Gateway Provider — The Payment Gateway Provider maintains private subscriber data, including credit card information, and evaluates authorization and settlement requests from MATRIXX Charging Application. The Payment Service receives authorization and settlement response messages from the Payment Gateway Provider, transforms them and sends them to MATRIXX Charging Application.
  • (Optional) A proxy server that communicates with a Payment Gateway Provider.

The Payment Service receives and sends messages through Apache ActiveMQ. MATRIXX Engine retrieves payment authorization result messages sent by the Payment Service to Apache ActiveMQ. When a payment authorization request is successful, an MtxPaymentAuthorizationEvent EDR is generated. If the payment authorization is unsuccessful, the result in the answer message is PAYMENT_AUTHORIZATION_FAILED (52).

Clients (such as custom Java and REST applications) that update subscriber payment methods (tokens) and purchase product offers or bundles must communicate directly with a Payment Gateway Provider to create subscriber payment methods, which include private subscriber information such as credit card numbers. MATRIXX Charging Application and the Payment Service keep no records of private subscriber payment information. The Payment Gateway Provider must give a payment nonce representing the payment method, which the Payment Service uses to request a payment token. This token is then passed to MATRIXX Charging Application through subscription management operations for setting up or updating a subscriber or group. For information about configuring the Payment Service for communication with Apache ActiveMQ, see the discussion about how to configure the Payment Service in MATRIXX Configuration.

Note: If the Payment Service has custom MDCs, you must start MATRIXX Engine before starting the Payment Service or the Payment Service must be able to access the mdc_config_custom.xml file during start-up.

By default, the Payment Service logs messages to /var/log/mtx/payment-service.log (or the value of MTX_LOG_DIR). The log rolls over when it reaches 2MB and a maximum of 10 logs are saved. For more information, see the discussion about Payment Service logging in MATRIXX Monitoring and Logging.