<?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 Re: How I can ger KeySet ID for Google Pay in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/95674#M59052</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/34513"&gt;@dblaze&lt;/a&gt; did it work for you in Production?&lt;/P&gt;&lt;P&gt;Currently it is accepting *anything* as Key Set ID, example `test`. And it seem to not matter, for TEST environment at least. I am able to integrate Google Pay with Authorize.net in TEST environment without using that KeySet ID anywhere. But I don't know if they require this for PRODUCTION.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jul 2026 10:04:00 GMT</pubDate>
    <dc:creator>Deepam</dc:creator>
    <dc:date>2026-07-23T10:04:00Z</dc:date>
    <item>
      <title>How I can ger KeySet ID for Google Pay</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/83783#M52840</link>
      <description>&lt;P&gt;In the documentation it says:&lt;BR /&gt;To sign up for Google Pay:&lt;BR /&gt;Step 1. In the Authorize.Net Merchant Interface &lt;A href="https://login.authorize.net" target="_blank"&gt;https://login.authorize.net&lt;/A&gt;, navigate to Account &amp;gt; Settings &amp;gt; Digital Payment Solutions. The available digital payment solutions appear.&lt;BR /&gt;Step 2. In the Google Pay section, click Sign Up.&lt;BR /&gt;Step 3. Enter your KeySet ID and generate a Signature Key if you haven't yet done so.&lt;/P&gt;&lt;P&gt;But no any information where and how I can get KeySet ID. Can any body help me in this?&lt;/P&gt;</description>
      <pubDate>Sun, 14 Aug 2022 06:00:09 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/83783#M52840</guid>
      <dc:creator>yhartonuk</dc:creator>
      <dc:date>2022-08-14T06:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: How I can ger KeySet ID for Google Pay</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/83818#M52858</link>
      <description>&lt;P&gt;So nobody setup&amp;nbsp;Google Pay through&amp;nbsp;Authorize.Net yet ?&lt;BR /&gt;Also&amp;nbsp;Authorize.Net&amp;nbsp;gateway is missing on&amp;nbsp;the list of the &lt;A href="https://developers.google.com/pay/api/web/guides/tutorial#tokenization" target="_self"&gt;certified&amp;nbsp;Google Pay gateways table&lt;/A&gt;&amp;nbsp;so I think&amp;nbsp;Google Pay functionality is not available for&amp;nbsp;Authorize.Net and this is funny thing in 2022. Good luck&amp;nbsp;Authorize.Net )&lt;/P&gt;</description>
      <pubDate>Wed, 17 Aug 2022 21:13:41 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/83818#M52858</guid>
      <dc:creator>yhartonuk</dc:creator>
      <dc:date>2022-08-17T21:13:41Z</dc:date>
    </item>
    <item>
      <title>Re: How I can ger KeySet ID for Google Pay</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/88694#M55890</link>
      <description>&lt;P&gt;I haven't finished the process yet, but go to &lt;A href="https://developers.google.com/pay/api" target="_blank"&gt;https://developers.google.com/pay/api&lt;/A&gt;. Click on &lt;EM&gt;Manage integrations in console&lt;/EM&gt;. Set-up your business profile and complete the form. I was able to get a &lt;STRONG&gt;Payments profile ID&lt;/STRONG&gt;, which I used as the Key Set ID. It seemed to accept it, so I will keep you posted if this does not work.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 18:08:50 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/88694#M55890</guid>
      <dc:creator>dblaze</dc:creator>
      <dc:date>2024-01-25T18:08:50Z</dc:date>
    </item>
    <item>
      <title>Re: How I can ger KeySet ID for Google Pay</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/90075#M56707</link>
      <description>&lt;P&gt;Hello dblaze, Were you able to setup and use Google Pay with Authorize.net?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2024 22:56:14 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/90075#M56707</guid>
      <dc:creator>neerajjain</dc:creator>
      <dc:date>2024-08-30T22:56:14Z</dc:date>
    </item>
    <item>
      <title>Re: How I can ger KeySet ID for Google Pay</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/95674#M59052</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/34513"&gt;@dblaze&lt;/a&gt; did it work for you in Production?&lt;/P&gt;&lt;P&gt;Currently it is accepting *anything* as Key Set ID, example `test`. And it seem to not matter, for TEST environment at least. I am able to integrate Google Pay with Authorize.net in TEST environment without using that KeySet ID anywhere. But I don't know if they require this for PRODUCTION.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2026 10:04:00 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-I-can-ger-KeySet-ID-for-Google-Pay/m-p/95674#M59052</guid>
      <dc:creator>Deepam</dc:creator>
      <dc:date>2026-07-23T10:04:00Z</dc:date>
    </item>
  </channel>
</rss>

