Advanced Vault for Merchant Aggregators

Advanced Vault offers many value adds for merchants to improve their payments outcomes, and Merchant Aggregators who extend these services to their sub-merchants can increase the value their platform provides. In order to do this, Merchant Aggregators require more control to selectively offer these value adds, and access reporting to properly associate costs to a specific sub-merchant.

Advanced vault is fully Merchant Aggregator compatible, allowing Merchant Aggregators the ability to scalably enable/disable AV and its subfeatures, and report on usage data for specific sub-merchants.


In order to fully offer all features of Advanced Vault, Merchant Aggregators should maintain a unique Environment for each sub-merchant.

Lifecycle Management Support for Merchant Aggregators

Historically, opting-in to the Lifecycle Management has been controlled at the Organization level, which affects ALL environments within the organization. Alternatively, the service can be controlled down to an individual payment method (card) as well. However, these options can either be too broad or too narrow to effectively and efficiently enable Account Updater for customers of merchant aggregators.

To support easier control at the sub-merchant level, Merchant Aggregators can enable/disable LCM at environment level, offering the ability to enable the service for specific segments of their business and for individual merchants when they use a 1:1 relationship with environments. For specifics on enabling LCM at the environment level, see here.

Network Tokenization Support

While provisioning and transacting with Network Tokens will always be done at payment method and transaction level, there are special considerations for Merchant Aggregators who want to offer Network Tokenization to their Sub-Merchants.

As discussed here, a Token Requestor ID is merchant specific, as are the network tokens that are provisioned under that TRID. As such Network Tokens for the submerchant must be generated in a Merchant Aggregator's Advanced Vault using a TRID obtained with the submerchant's details. Spreedly supports this use case by offering the ability to apply a unique TRID at the environment level.

If you have a submerchant use case:

  1. You or the sub-merchant may submit the Advanced Vault onboarding with their details
  2. You will then inform Spreedly Support of the environment key being used for this submerchant
  3. Spreedly Support will request a TRID for the submerchant
  4. Spreedly Support will enable NT for the environment you have indicated with the unique TRID