<?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 Google Pay Direct Integration Rotation of keys in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82361#M52</link>
    <description>&lt;P&gt;I am trying to implement the Google Pay using direct integration and in the google docs it is mentioned that merchants have to manually rotate the keys. During rotation it is mentioned that Caution: You must support the old private key for decryption of payment methods for eight days after you remove the old public key.&lt;/P&gt;&lt;P&gt;Does this mean I need to support old private key even after deleting the old public key?&lt;/P&gt;&lt;P&gt;I found out that Google uses Elliptic Curve Digital Signature which is asymmetric. As far as I know in case of asymmetric algorithms only one key pair will be involved (public and private). Why does Google recommend to support old private key up to 8 days?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.handrblock.me/" target="_self"&gt;&lt;FONT size="1 2 3 4 5 6 7" color="#FFFFFF"&gt;H and R Block&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Apr 2022 11:27:05 GMT</pubDate>
    <dc:creator>Gaulke121</dc:creator>
    <dc:date>2022-04-26T11:27:05Z</dc:date>
    <item>
      <title>Google Pay Direct Integration Rotation of keys</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82361#M52</link>
      <description>&lt;P&gt;I am trying to implement the Google Pay using direct integration and in the google docs it is mentioned that merchants have to manually rotate the keys. During rotation it is mentioned that Caution: You must support the old private key for decryption of payment methods for eight days after you remove the old public key.&lt;/P&gt;&lt;P&gt;Does this mean I need to support old private key even after deleting the old public key?&lt;/P&gt;&lt;P&gt;I found out that Google uses Elliptic Curve Digital Signature which is asymmetric. As far as I know in case of asymmetric algorithms only one key pair will be involved (public and private). Why does Google recommend to support old private key up to 8 days?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.handrblock.me/" target="_self"&gt;&lt;FONT size="1 2 3 4 5 6 7" color="#FFFFFF"&gt;H and R Block&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2022 11:27:05 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82361#M52</guid>
      <dc:creator>Gaulke121</dc:creator>
      <dc:date>2022-04-26T11:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pay Direct Integration Rotation of keys</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82419#M62</link>
      <description>&lt;P&gt;The workflow is the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Define/upload a new key pair (recommended annually)&lt;/LI&gt;&lt;LI&gt;Support both New and old keys during decryption&lt;PRE&gt; String decryptedMessage =
  new PaymentMethodTokenRecipient.Builder()
     .addRecipientPrivateKey(newPrivateKey)
     .addRecipientPrivateKey(oldPrivateKey);&lt;/PRE&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;remove old key&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This is a common approach as the platform might require some time to propagate the new keys and make sure the old ones are no longer used.&amp;nbsp;You need to support the old key&amp;nbsp;deploying the code above (supporting both signatures) for some time (at least 8 days according to Google's note) and ideally&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;confirm that the old public key is no longer used to encrypt any transactions.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Sat, 30 Apr 2022 12:06:01 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82419#M62</guid>
      <dc:creator>Xamaaa</dc:creator>
      <dc:date>2022-04-30T12:06:01Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pay Direct Integration Rotation of keys</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82471#M73</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Well it would be nice to have a choice instead of having to bring my wallet and cards in case I have to use a browser based payment system like every venue in my country has now since the pandemic. It's not that much of a big deal but it would be nice to have similar functionality as other browsers.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 May 2022 12:37:09 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/82471#M73</guid>
      <dc:creator>JamesZimmerman</dc:creator>
      <dc:date>2022-05-04T12:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pay Direct Integration Rotation of keys</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/83179#M172</link>
      <description>&lt;P&gt;This is a typical methodology as the stage would demand an investment to spread the new keys and ensure the old ones are not generally utilized. You want to help the old key conveying the code above (supporting the two marks) for quite a while&amp;nbsp;(something like 8 days as indicated by Google's note) and preferably&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 10:55:01 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/83179#M172</guid>
      <dc:creator>Tonny_Robins</dc:creator>
      <dc:date>2022-06-20T10:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Google Pay Direct Integration Rotation of keys</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/83469#M220</link>
      <description>&lt;P&gt;It isn't so a very remarkable serious deal however having comparable usefulness as different browsers would be great.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 14:36:25 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Google-Pay-Direct-Integration-Rotation-of-keys/m-p/83469#M220</guid>
      <dc:creator>Tonny_Robins</dc:creator>
      <dc:date>2022-07-20T14:36:25Z</dc:date>
    </item>
  </channel>
</rss>

