<?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: Do I need to setup a Visa Click to Pay account just to bypass a button? in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Do-I-need-to-setup-a-Visa-Click-to-Pay-account-just-to-bypass-a/m-p/96242#M4599</link>
    <description>&lt;P&gt;You should not need a separate Click to Pay account if you only take cards.&lt;/P&gt;&lt;P&gt;Try removing Click to Pay from allowedPaymentTypes in your capture context and ask support to confirm it is disabled on your merchant account, as that button usually appears when the wallet option is still turned on.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Nov 2026 02:27:22 GMT</pubDate>
    <dc:creator>zainab34</dc:creator>
    <dc:date>2026-11-19T02:27:22Z</dc:date>
    <item>
      <title>Do I need to setup a Visa Click to Pay account just to bypass a button?</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Do-I-need-to-setup-a-Visa-Click-to-Pay-account-just-to-bypass-a/m-p/96240#M4598</link>
      <description>&lt;P&gt;I've been relying on Google to help me through the integration with cybersource using their Unified Checkout screen on my company's web site. I have a button on my screen that opens the Unified Checkout screen and at present, we are only accepting credit cards. The sidebar that opens shows a button "Pay with Card" and displays the icons for what cards we will accept. My client doesn't want the end users to have to click an additional button just to move to the card entry screen, so I looked into how to bypass the button (since the sidebar opens into its own iframe, I can't trigger the button click automatically). Google, said that I needed to add to the CLICKTOPAY entry in the Capture Context -&amp;gt;&amp;nbsp;allowedPaymentTypes. Which I did and still got the button. A little more research says that I have to also configure Click to pay in the portal, but that option isn't present. When I found out how to enable it, it is basically saying that I need to setup an account with Visa Click to Pay. Do I really need to go through all this just to avoid a button click?&lt;/P&gt;&lt;P&gt;At one point, Google had suggested using Trigger rather than createCheckout on the javascript side but I could never get the configurations correct to get that to work (it would usually complain about a missing or undefined item called Telegraph (or Telegram, I can't remember now) when I thought I had the configurations the way I needed them).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2026 13:55:26 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Do-I-need-to-setup-a-Visa-Click-to-Pay-account-just-to-bypass-a/m-p/96240#M4598</guid>
      <dc:creator>jroa</dc:creator>
      <dc:date>2026-11-18T13:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: Do I need to setup a Visa Click to Pay account just to bypass a button?</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Do-I-need-to-setup-a-Visa-Click-to-Pay-account-just-to-bypass-a/m-p/96242#M4599</link>
      <description>&lt;P&gt;You should not need a separate Click to Pay account if you only take cards.&lt;/P&gt;&lt;P&gt;Try removing Click to Pay from allowedPaymentTypes in your capture context and ask support to confirm it is disabled on your merchant account, as that button usually appears when the wallet option is still turned on.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 02:27:22 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Do-I-need-to-setup-a-Visa-Click-to-Pay-account-just-to-bypass-a/m-p/96242#M4599</guid>
      <dc:creator>zainab34</dc:creator>
      <dc:date>2026-11-19T02:27:22Z</dc:date>
    </item>
  </channel>
</rss>

