Skip to main content
MarketONE supports two main billing methods: Direct Carrier Billing (DCB), and Credit Cards. Users may choose to have the digital service charged to the card associated to their service, or bill it to their bill from the Reseller (Service Provider). DCB can also help when the purchase of the Merchant service is done directly from the Merchant website, instead of the Reseller (Service Provider) owned digital store (thereby allowing for additional onboarding options for the customer).

​
Supported Capabilities

Commerce Engine supports a variety of out-of-the-box (OOTB) payment methods, including Credit Card, PayPal, Google Pay, and Apple Pay. Any of these payment methods can be used as part of the MarketONE experience. Commerce Engine is Payment Card Industry (PCI) compliant and is in charge of the following: maintaining store credit card numbers, creating payment tokens, and validating credit cards. Commerce Engine also has OOTB integrations to the Amdocs Customer Experience Suite (CES) to support DCB. Credit Card Commerce Engine has a payment (PMT) iframe that is integrated into the MarketONE digital store to capture and process the credit card details for the user. The credit card details are entered directly within Commerce Engine. Once they are validated, a token is generated and sent to Storefront Gateway to be associated to the user. This association in Storefront Gateway allows for payment sharing support: users can delegate and share their validated cards to other members of the household for purchases. Multiple users with their own distinct user identity and login are able to make purchases with the same credit card. Also, since the payment token is maintained within Storefront Gateway, future purchases to retrieve the payment method will be retrieved while getting user details from Storefront Gateway without having to be call the Commerce Engine APIs. Direct Carrier Billing Commerce Engine is integrated to the Amdocs CES to support DCB. A user must associate their billing account to their digital identity for it to be used for purchases. Storefront Gateway supports account association with a variety of validation methods, like challenge questions, two-factor authentication (2FA), and one-time password (OTP). Once the user associates their account, Storefront Gateway then maintains the user-to-account mapping. At the time of purchase, while selecting the available payment methods, the account associated to the user will also be presented for selection. Upon purchase, Commerce Engine associates the subscription with an external billing payment method associated to the account. At the anniversary of every purchase date, Commerce Engine creates the charge and makes it available for the Amdocs CES system to process and apply it to the customer’s bill. If the customer terminates the subscription, the charge event will no longer be created and sent to the billing system. Parent topic:Developer Best Practices