<?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 1. Issue Accessing External URL During Cybersource Integration in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/1-Issue-Accessing-External-URL-During-Cybersource-Integration/m-p/94673#M4010</link>
    <description>&lt;P&gt;Hi — I’m working on integrating your payment gateway with my custom platform, but when I try to access this external site for payment-related features: &lt;STRONG&gt;&lt;A class="" href="https://summertimesagasdl.com/?utm_source=chatgpt.com" target="_new" rel="noopener"&gt;https://summertimesagasdl.com/&lt;/A&gt;&lt;/STRONG&gt; I get a message “Verifying that you are not a robot…” and then it doesn’t proceed. Has anyone used a similar link/site with Cybersource? Could this be causing payment-processing or tokenization issues? If yes — how do you handle or bypass such “bot verification” pages while remaining compliant with security and gateway requirements?&lt;/P&gt;</description>
    <pubDate>Sat, 06 Dec 2025 20:27:48 GMT</pubDate>
    <dc:creator>finallen1231</dc:creator>
    <dc:date>2025-12-06T20:27:48Z</dc:date>
    <item>
      <title>1. Issue Accessing External URL During Cybersource Integration</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/1-Issue-Accessing-External-URL-During-Cybersource-Integration/m-p/94673#M4010</link>
      <description>&lt;P&gt;Hi — I’m working on integrating your payment gateway with my custom platform, but when I try to access this external site for payment-related features: &lt;STRONG&gt;&lt;A class="" href="https://summertimesagasdl.com/?utm_source=chatgpt.com" target="_new" rel="noopener"&gt;https://summertimesagasdl.com/&lt;/A&gt;&lt;/STRONG&gt; I get a message “Verifying that you are not a robot…” and then it doesn’t proceed. Has anyone used a similar link/site with Cybersource? Could this be causing payment-processing or tokenization issues? If yes — how do you handle or bypass such “bot verification” pages while remaining compliant with security and gateway requirements?&lt;/P&gt;</description>
      <pubDate>Sat, 06 Dec 2025 20:27:48 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/1-Issue-Accessing-External-URL-During-Cybersource-Integration/m-p/94673#M4010</guid>
      <dc:creator>finallen1231</dc:creator>
      <dc:date>2025-12-06T20:27:48Z</dc:date>
    </item>
  </channel>
</rss>

