This next post event says they are using a "shared vault payment profile nonce" and there is a reply from Auth.net administrator seeming to confirm this. Maybe this isn't what I'm lookinfor but if anyone has any more info on how my scenario can be accomplished or point me to documentation I need it would be much appreciated.
If this feature doesn't exist, would the alternative be to use AIM to vault each customer payment info across all our gateway CIMs in the case that a different merchant account needs to use it in the future? I say AIM because I'm guessing using the hosted form to save the payment data wouldn't allow to store it in the other gateway.
Thanks for any help from the community on this one.