Home
MATRIXX Pay Now
Pay Now Overview
MATRIXX Pay Now enables the Charging Server to request immediate payment for product offer and bundle purchases, postpaid balance payments, and recharges from a Payment Gateway Provider. Subscribers can make quick and secure purchases using payment methods such as credit and debit cards.
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.
Payment Service Recurring Override
You can set a property, recurringOverride, with a _glossary/mdc.html Boolean-type field name in an MtxChargeMethodExtension MDC that sets the Braintree recurring flag. This flag overrides the system ECI recurring flag.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
- About MATRIXX Pay Now
  MATRIXX Pay Now describes the tasks required to configure MATRIXX Pay Now and the MATRIXX Payment Service that enables Pay Now and provides overviews, recommendations, and conceptual discussions to help you understand these tasks.
- Pay Now Overview
  MATRIXX Pay Now enables the Charging Server to request immediate payment for product offer and bundle purchases, postpaid balance payments, and recharges from a Payment Gateway Provider. Subscribers can make quick and secure purchases using payment methods such as credit and debit cards.
  - Pay Now Components
    Pay Now involves multiple components that work together to recognize immediate payment for one-time _glossary/product_offer.html and _glossary/bundle.html purchases.
  - 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.
    - Payment Service for Multiple Sub-Domains
      In a MATRIXX environment where multiple customer sub-domains are implemented in separate engine chains, you can configure the Payment Service with a request-response queue pair for each engine.
    - Payment Service Merchant Account Mapping
      A typical Payment Gateway Provider supports different merchant accounts to which the payment is requested. A Payment Gateway Provider might also support sub-accounts from which payments of a similar category can be made. For example, a merchant might want all payments by credit card processed by merchant account A and everything else processed by merchant account B. However, both merchant account A and merchant account B exist under a parent account X. The Payment Service determines the merchant account to use when it receives a payment request.
    - Payment Service Recurring Override
      You can set a property, recurringOverride, with a _glossary/mdc.html Boolean-type field name in an MtxChargeMethodExtension MDC that sets the Braintree recurring flag. This flag overrides the system ECI recurring flag.
    - Payment Service User-Defined Fields (UDFs)
      Configure User-Defined Fields (UDFs) to map fields in the MtxChargeMethodExtension object in an incoming payment request to the fields in the message sent to the Payment Gateway Provider. A Payment Gateway Provider may add additional fields in a message structure to allow merchants to specify additional values. Some providers allow you to add new fields or replace existing ones.
  - Pay Now Payment Process
    Before beginning the Pay Now authorization process, the client must request a client authorization token from the Payment Service and the Payment Service must request a payment method token from the Payment Gateway Provider.
  - Pay Now Payment Methods
    Payment tokens represent payment methods, such as a credit card number, but do not contain actual payment information. They are generated by the Payment Service and must be added to subscriber or group wallets using the SubMan APIs.
  - Pay Now Catalog Item Purchases
    When purchasing catalog items, there are multiple options for specifying how payments are made.
  - Pay Now Payments and Recharges
    Use Pay Now to make one-time top-ups to prepaid actual currency balances (recharges) or one-time payments to postpaid main balances.
  - Pay Now Automatic Recharge
    Automatic recharge makes immediate payments to subscriber and group wallets according to a predefined schedule, automatically based on recurring billing and purchased item cycles, or when a balance threshold is triggered due to a balance increase.
  - Pay Now Refunds
    Using the SubMan APIs, you can request a subscriber or group Pay Now payment refund to prepaid or postpaid main balances. The Payment Service also supports partial refunds for the Braintree Payment Gateway Provider.
  - Pay Now Normalization
    Normalizers can be applied on the temporary MtxEventChargeNormalizationInfo MDC to use different General Ledger (GL) account names and GL transaction types based on the payment type, update type, event type, and tax class.
  - Pay Now Operations
    A Pay Now operation can be initiated by multiple actions, such as a purchase authorization, settlement, and refund.
- Configuring Pay Now
  System administrators must configure the Payment Service to enable communication between Apache ActiveMQ, MATRIXX Engine, and the Payment Service. In addition, they must configure the Payment Service third-party Payment Gateway Provider properties file location.
- Manage the Payment Service
  This procedure describes how to run the Payment Service as a service.
- Pay Now Payment Gateway Adapters
  Each Payment Gateway Adapter can support multiple features, operations, and payment methods.
- Pay Now APIs
  Each client that communicates with the Payment Service has different requirements based on the payment gateways that it supports. Client developers should contact MATRIXX Support for information specific to their client implementation.
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Payment Service Recurring Override

You can set a property, recurringOverride, with a MATRIXX Data Container (MDC) Boolean-type field name in an MtxChargeMethodExtension MDC that sets the Braintree recurring flag. This flag overrides the system ECI recurring flag.

The MtxChargeMethodExtension is an empty MDC that can be extended to hold user-defined fields. You must create an MtxChargeMethodExtension custom field and set the value of that field to true or false.

In the /opt/mtx/conf/payment-service.yaml file, set the recurringOverrideFieldName value to the custom field in MtxChargeMethodExtension. If the recurringOverrideFieldName value is not set, the value of the system ECI recurring flag is used.

For example, create an MtxChargeMethodExtension MDC field named RecurringOverride of type Boolean and set the value of this field to true. In the /opt/mtx/conf/payment-service.yaml file, add the following:

payment:
  gateway:
    braintree:
      configs:
        default:
          recurringOverrideFieldName:RecurringOverride

The payment request sent to the Braintree Payment Gateway Provider indicates that this is a recurring payment.