title: Handle storing card details when using multiple payment providers
body: <p>It's a common feature for payment providers to have a medium to store card details(which returns a reference you can always use to charge a card).</p>
  
  <p>We plan on leveraging multiple payment providers, considering that our product is used by various regions (both to support the locally available cards and alongside maintain low payment charges incurred by the customer, based on their location).</p>
  
  <p>Now the challenge is that each time we integrate a new payment provider, it'll require that we replicate/store all of our existing users' card details (already stored on other payment providers we leverage on) on the new provider we'll be integrating with. </p>
  
  <p>Knowing fully well that:</p>
  
  <ul>
  <li>We don't store users' card</li>
  <li>Previously integrated payment providers don't return complete card details (just reference).</li>
  <li>Payment providers cannot allow transferring card details to another provider.</li>
  </ul>
  
  <p>I'm hereby seeking an alternative solution (that doesn't require storing card).</p>
  
  <p>I saw something close to what we could rely on(<a href="https://www.spreedly.com/" rel="nofollow noreferrer">https://www.spreedly.com/</a>). Are there also alternatives to this?</p>