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.
Important: It may be necessary to define subscriber information, such as a customer ID, in the subscriber database and identical information in the Payment Service payment gateway. For information about registering subscribers and configuring your specific
implementation of the Payment Service to communicate with RS Gateway, see the discussion about configuring the Payment Service in MATRIXX Configuration and
contact your MATRIXX representative.
Figure 1 shows the main components that form the MATRIXX Pay Now functionality and how messages are sent and received from each component. RS Gateway communicates with MATRIXX Engine.
The process steps described here refer to Figure 1.
- The client uses the MtxRequestSysCreateClientToken API to request a client authorization token.
- The client communicates directly with the Payment Gateway Provider and retrieves a payment nonce using the Payment Gateway Provider gateway-specific APIs. The payment nonce is a single-use BLOB that is passed to the Payment Service.
- The client sends the nonce to RS Gateway.
- The Payment Service uses the nonce to request a long-lived payment method token from the Payment Gateway Provider.
- The client uses the payment_token REST
APIs to add the payment method token to the subscriber or group wallet. The
client can also use the JAVA API to communicate directly with the MDC Gateway to manage the subscriber or group.
See Pay Now SubMan APIs for a description of the Pay Now management APIs.
Pay Now is now configured to begin the authorization process described in the discussion about the Pay Now authorization process.
