Pay Now Components

Pay Now involves multiple components that work together to recognize immediate payment for one-time product offer and bundle purchases.

Pay Now includes the following components:
  • MATRIXX Engine — Generates Pay Now payment authorization request messages and payment settlement request messages that are sent to Apache ActiveMQ. The engine retrieves payment settlement result messages sent by the Payment Service to Apache ActiveMQ. When a payment settlement request is successful, an MtxPaymentSettlementEvent Event Detail Record (EDR) is generated. If the payment settlement is unsuccessful, an error is logged.

    If an authorization or settlement request is not successful, an MtxPaymentAuthorizationEvent EDR or MtxPaymentSettlementEvent EDR is generated with the failure status. The status can be SUCCEEDED, REJECTED_BY_PAYMENT_GATEWAY, or TIME_OUT.

  • Payment Service — 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).

    The Payment Service retrieves payment authorization requests from the message broker. After receiving a payment authorization response from the payment gateway, the Payment Service sends a payment authorization result message to the message broker indicating whether the payment authorization succeeded.

    For information about installing the Payment Service, see MATRIXX Installation and Upgrade.

  • A message broker — Apache ActiveMQ implements Java Message Service (JMS) and handles messages sent from MATRIXX Engine and received from the Payment Service. For more information about ActiveMQ configuration, see the discussion about ActiveMQ Gateway configuration in MATRIXX Configuration.
    Note: The activemq.log file, queues, and topics should be monitored for any errors. For more information, see Apache ActiveMQ in MATRIXX Administration.
  • Clients — Custom applications (JAVA, REST, and so forth) that update subscriber payment methods (tokens) and purchase product offers or bundles.
  • Third-party payment gateways — E-commerce application service providers that authorize payments for product offer or bundle purchases using payment methods such as credit or debit cards. Payment gateways generate payment tokens, which are added to subscriber or group wallets using the SubMan APIs. Payment gateway adapters are interfaces that extend Pay Now support to a particular payment gateway. See the discussion about Pay Now payment gateway adapters for more information.

Pay Now Components illustrates the Pay Now components.

Figure 1. Pay Now Components
Message Flow from MATRIXX Engine to ActiveMQ to Payment Service to Payment Gateway Provider

For more information about how these components work together, see the discussion about the Pay Now payment process.