Triggering Dedupe on Create Merchant

dedupe can be triggered on the docid\ u2vqnqx3q sskq3ob1mxq step of the journey it can be done in a few simple steps select the parameter on which dedupe will be triggered dedupe can be done only on 2 parameters for this right now name of the merchant/applicant and mobile number mobile number dedupe is triggered as soon as the create merchant is hit in the case of positive dedupe, we have two 'call to action' options we can select one or both of them by selecting the checkbox allow users to (select at least one) prefill applications if an applicant has begun the journey of some product, then when they apply for some other product of the same organization, they get an option to prefill the fields/ docid\ xsd0meic4aadzddtkedsy that are common in the two journeys when the dedupe is triggered prevent subflow prefilling enabling this toggle will prevent prefilling of a subflow that exists in the main flow even in the case of positive dedupe select variable to filter applications select the variable from the journey based on which applications will be filtered ex product code can be a variable/field against which applications will be filtered for now, if you don’t have any such field then you can pass a hardcoded default value which will be for each applicant (you can hide it from the user and backops) resume applications if an applicant has begun the journey of some product and has dropped mid journey, then when they apply for some other product of the same organization, they get an option to resume the journey for the previous product that they dropped off when the dedupe is triggered we can also select the information that will be visible in case of a positive dedupe by checking these checkboxes application number name status reason date of last update of application getting help please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better you can reach out to us at