<?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 Accept Hosted Card Code validation for existing payment profiles in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-Hosted-Card-Code-validation-for-existing-payment-profiles/m-p/62323#M36673</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working on implementing Accept Hosted in place of our current&amp;nbsp; CIM integration.&amp;nbsp; In our current application, when a user attempts to make a payment with an existing payment profile.&amp;nbsp; We validate that the cvv/cvc matches when we process&amp;nbsp;the transaction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to keep this functionality with the Accept Hosted implementation.&amp;nbsp; I have been able to pull back the most recent profiles.&amp;nbsp; However, setting cardCodeRequired to true, doesn't seem to force a user to enter their cvv for an existing profile.&amp;nbsp; Is this possible with Accept Hosted&lt;/P&gt;</description>
    <pubDate>Mon, 26 Mar 2018 20:08:59 GMT</pubDate>
    <dc:creator>jwh31579</dc:creator>
    <dc:date>2018-03-26T20:08:59Z</dc:date>
    <item>
      <title>Accept Hosted Card Code validation for existing payment profiles</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-Hosted-Card-Code-validation-for-existing-payment-profiles/m-p/62323#M36673</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are working on implementing Accept Hosted in place of our current&amp;nbsp; CIM integration.&amp;nbsp; In our current application, when a user attempts to make a payment with an existing payment profile.&amp;nbsp; We validate that the cvv/cvc matches when we process&amp;nbsp;the transaction.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to keep this functionality with the Accept Hosted implementation.&amp;nbsp; I have been able to pull back the most recent profiles.&amp;nbsp; However, setting cardCodeRequired to true, doesn't seem to force a user to enter their cvv for an existing profile.&amp;nbsp; Is this possible with Accept Hosted&lt;/P&gt;</description>
      <pubDate>Mon, 26 Mar 2018 20:08:59 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-Hosted-Card-Code-validation-for-existing-payment-profiles/m-p/62323#M36673</guid>
      <dc:creator>jwh31579</dc:creator>
      <dc:date>2018-03-26T20:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: Accept Hosted Card Code validation for existing payment profiles</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-Hosted-Card-Code-validation-for-existing-payment-profiles/m-p/62372#M36710</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This feature is coming in a future release, right now the cardCodeRequired flag specifies whether&amp;nbsp;CVV is required when a customer enters their credit card information (i.e. not using a stored customer profile card).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the next release this same flag will also force a prompt from the hosted form to enter the CVV of the selected card.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll update this thread when we have firmer idea of timelines.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the feedback.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 17:41:56 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Accept-Hosted-Card-Code-validation-for-existing-payment-profiles/m-p/62372#M36710</guid>
      <dc:creator>brianmc</dc:creator>
      <dc:date>2018-03-28T17:41:56Z</dc:date>
    </item>
  </channel>
</rss>

