> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Merchant-Managed Product Lifecycle Integration

This onboarding and monetization flow requires that the [Merchant-managed](g_partnerManagedFlow) subscriptions integrate with the MarketONE OpenAPIs. This integration has multiple steps. The following image provides a generic example of this integration in action at a high level.

<img src="https://mintcdn.com/amdocs-spbu/v6XW4z-1DbX5IGa9/marketONE/merchantOnboardingGuide/images/PartnerManagedSubscriptionsIntegration2.PNG?fit=max&auto=format&n=v6XW4z-1DbX5IGa9&q=85&s=64772ec8f975ffb004bc546f11338efd" alt="Merchant-Managed Subscriptions Integration Flow" width="1750" height="768" data-path="marketONE/merchantOnboardingGuide/images/PartnerManagedSubscriptionsIntegration2.PNG" />

For more details on the integration, see the [Merchant-Managed Use Cases](dgPartnerUseCases).

## 1. Validating the User Account

The user selects statement billing (for example: DCB) on their Merchant service. They then enter their mobile number for account validation. The Merchant sends the `POST /partnerSubscription` call with the user's mobile number as account identifier, partner code (optional) and product code (optional).

MarketONE requests the validation of the user account from the Reseller by invoking the `POST /account/validate` API call. Once the validation is finished, the Reseller notifies MarketONE with the results. In turn, MarketONE sends the results to the Merchant.

<img src="https://mintcdn.com/amdocs-spbu/-GCj74mr5p4KPy3T/marketONE/merchantOnboardingGuide/images/ottprocess_step1.png?fit=max&auto=format&n=-GCj74mr5p4KPy3T&q=85&s=ce5ec47f1fb194523b8b64d60486442e" alt="" width="1435" height="850" data-path="marketONE/merchantOnboardingGuide/images/ottprocess_step1.png" />

## 2. Validating the PIN

Once the user account is validated, MarketONE generates a one-time PIN for the user.

MarketONE then asks the Reseller (SP) to send the one-time PIN to the user by invoking the `POST /notification` API call. The user receives the PIN from the Reseller (SP) notification system.

The user enters the one-time PIN on the Merchant application, and is validated by MarketONE by invoking the `POST /partnerSubscription/{id}/validate` API call.

The user can confirm they agree to pay with their bill. This is a step that can optionally be removed through configuration.

<img src="https://mintcdn.com/amdocs-spbu/-GCj74mr5p4KPy3T/marketONE/merchantOnboardingGuide/images/ottprocess_step2.png?fit=max&auto=format&n=-GCj74mr5p4KPy3T&q=85&s=0a26628af8f935c536fe2c5f1f09e53c" alt="Generating the One-Time User PIN" width="1001" height="870" data-path="marketONE/merchantOnboardingGuide/images/ottprocess_step2.png" />

## 3. Posting the Charge

The Merchant leverages the `POST /transaction` API call to send the charge.

MarketONE leverages the `POST /transaction` API call to send the transaction to the Reseller (SP) for statement billing (for example: DCB).

<img src="https://mintcdn.com/amdocs-spbu/-GCj74mr5p4KPy3T/marketONE/merchantOnboardingGuide/images/ottprocess_step3.png?fit=max&auto=format&n=-GCj74mr5p4KPy3T&q=85&s=939139e96d4e26034cb9be6ece989474" alt="Sending the Transaction for Posting" width="854" height="538" data-path="marketONE/merchantOnboardingGuide/images/ottprocess_step3.png" />

## 4. Canceling a Subscription

In the case of a subscription cancellation, the Merchant is required to call the cancellation API for MarketONE to cancel the active subscription billing entitlement. MarketONE will inform the Reseller the customer no longer has the Partner subscription and the ability to charge for the product on their statement bill.

<img src="https://mintcdn.com/amdocs-spbu/-GCj74mr5p4KPy3T/marketONE/merchantOnboardingGuide/images/ottprocess_step4.png?fit=max&auto=format&n=-GCj74mr5p4KPy3T&q=85&s=aaeaa14d6490c08bd81e68ad59d0e6df" alt="Canceling a Subscription" width="682" height="429" data-path="marketONE/merchantOnboardingGuide/images/ottprocess_step4.png" />

**Parent topic:**[Step 1: Discovery and Education](partnerOnboardingDiscovery_r)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.