<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Token vs Profile in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Token-vs-Profile/m-p/78943#M49631</link>
    <description>&lt;P&gt;Working on a new project to replace an old system.&amp;nbsp; I'm told by my client that they were told by Authorize.NET that they could transfer/export all of the tokens out of their old provider (using another merchant account and payment processor) and make them available for use in their new A.NET account.&amp;nbsp; At least, that's what I've been told.&amp;nbsp; If they do that, what will it look like in A.NET?&amp;nbsp; Will they be customers in CIM with profiles and payment profiles?&amp;nbsp; Something else?&amp;nbsp; I saw in the "Charge a Tokenized Credit Card" in the A.NET API documentation, but I had planned on using profiles for the new customers that we'll be adding moving forward.&amp;nbsp; Is there a difference?&amp;nbsp; If so, is it possible to get from profiles to tokens or tokens to profiles so that all of our customers (old and new) will be charged with the same mechanism?&amp;nbsp; Instead of profiles, can I tokenize new credit cards and use tokens moving forward?&amp;nbsp; If so, how?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just looking for some more information on how these tokens are likely to come over from the old system and how I can best be prepared for the migration what it happens.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
    <pubDate>Fri, 01 Oct 2021 14:22:53 GMT</pubDate>
    <dc:creator>mattjames</dc:creator>
    <dc:date>2021-10-01T14:22:53Z</dc:date>
    <item>
      <title>Token vs Profile</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Token-vs-Profile/m-p/78943#M49631</link>
      <description>&lt;P&gt;Working on a new project to replace an old system.&amp;nbsp; I'm told by my client that they were told by Authorize.NET that they could transfer/export all of the tokens out of their old provider (using another merchant account and payment processor) and make them available for use in their new A.NET account.&amp;nbsp; At least, that's what I've been told.&amp;nbsp; If they do that, what will it look like in A.NET?&amp;nbsp; Will they be customers in CIM with profiles and payment profiles?&amp;nbsp; Something else?&amp;nbsp; I saw in the "Charge a Tokenized Credit Card" in the A.NET API documentation, but I had planned on using profiles for the new customers that we'll be adding moving forward.&amp;nbsp; Is there a difference?&amp;nbsp; If so, is it possible to get from profiles to tokens or tokens to profiles so that all of our customers (old and new) will be charged with the same mechanism?&amp;nbsp; Instead of profiles, can I tokenize new credit cards and use tokens moving forward?&amp;nbsp; If so, how?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just looking for some more information on how these tokens are likely to come over from the old system and how I can best be prepared for the migration what it happens.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 14:22:53 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Token-vs-Profile/m-p/78943#M49631</guid>
      <dc:creator>mattjames</dc:creator>
      <dc:date>2021-10-01T14:22:53Z</dc:date>
    </item>
  </channel>
</rss>

