Merchant Groups

use merchant groups to manage multiple psp connections this is especially handy when you need to settle funds from the same currency into bank accounts merchant groups enable you to set up different groups of psp connections, and then assign those groups to different payments and authorisations think of them as containers for your psp connections also, multi merchant integrations support different paypage templates for merchant groups customisation options include paypage logos, colours, and styles merchant groups is available for customers using asperato v2 13 onwards how it works create groups in the asperato setup tab, you create merchant groups (e g , "store a," "store b") add psps you add your specific psp connections (e g , your stripe gbp account for store a) to the relevant merchant group assign to payments/authorisations when processing a payment, you specify which merchant group it should use, picking it up from a list this determines which psp connection is used use cases the most common use case is with different legal entities a franchise for example may have a single salesforce org managing a few hundred stores across a region, and each of those stores would have their own merchant psp accounts the merchant group functionality facilitates this use case by allowing a new merchant group to be set up per store another use case could be when a merchant has a requirement to settle funds into separate bank accounts each with the same psp and currency for regulatory reasons, for example paying household rent and deposit payments into separate bank accounts create a merchant group on the asperato setup tab, click the new merchant group button enter a name for your merchant group and then click the create new merchant group button after selecting the merchant group, you add your psp connections these will be assigned to that merchant group repeat this process for as many merchant groups as you require assign merchant group assign a merchant group to a payment or authorisation the merchant group field is a picklist in the payment and authorisation records populated by the values on the asperato setup tab if the merchant group field is left blank, the default merchant group will be assigned and used instead to ensure backward compatibility for versions earlier than 2 20, the merchant group field appears as a free text field and has to be populated manually or using a flow with the correct merchant group for each payment and versions assign a merchant group to a repeat payment for a merchant group to be assigned to a repeat payment (a payment attached to an authorisation), then the merchant group field on both the payment and authorisation objects must match exactly if they do not, then the payment will not be processed but instead, return a failure status of merchant groups must match assign merchant group to a payment schedule there is no need to assign a merchant group to a payment schedule directly the merchant group used will be the one that is set on the authorisation record(s) attached to the payment schedule rename merchant groups merchant groups cannot be renamed, as this would break any established automation that relied on the merchant group's name if the group has to be renamed, it should be first deleted, then a new one created with the correct name, then the psp connections re established against the new group if you are creating authorisation records for repeat collections, then you will need to contact support\@asperato com mailto\ support\@asperato com to help you with this change set the default merchant group you must set the default merchant group by record type for both the asperato authorisation and payment objects if you are not using outbound payments, you only need to perform these steps for the inbound record type in salesforce, navigate to setup > object manager choose either the authorisation or payment object in the left hand navigation menu, click record types choose the relevant record type (either inbound or outbound , or both if applicable) in the picklists available for editing section, find merchant group and click edit choose what merchant groups to include in the picklist at the bottom of the picklist, check the default box next to the merchant group you wish to use as the default click save to finish repeat these steps for the other object (either payment or authorisation) and for the relevant record type(s) after completing these steps, the selected merchant group will be the default for new records of the specified type licensing the asperato multi license allows up to 6 connected payment service providers (psps) settled into separate bank accounts of different currencies for example, you may have a stripe account for gbp and eur card payments, a gocardless account for gbp and eur direct debit payments and a cybersource account for usd card payments however, if you require settling into multiple bank accounts of the same currency (as in the case you need to connect a second stripe account to use for a subset of gbp card setup) then an asperato multi merchant license is required the merchant groups feature is used to manage this requirement