<?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: authorize.net-hosted iframe duplicate transactions in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90789#M57070</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hosted payment requests rely on the token generated by the 'getHostedPaymentPageRequest' request. This token is valid for a single transaction, so any resubmitted payment should result in the message "&lt;STRONG&gt;A duplicate transaction has been submitted.&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;If a user goes back and submits again, a new token will be generated, potentially causing a duplicate transaction.&lt;/P&gt;&lt;P&gt;I would appreciate details about the transaction and the timestamp it occurs so we can debug this issue.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Nov 2024 05:46:29 GMT</pubDate>
    <dc:creator>dipespat</dc:creator>
    <dc:date>2024-11-21T05:46:29Z</dc:date>
    <item>
      <title>authorize.net-hosted iframe duplicate transactions</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90783#M57064</link>
      <description>&lt;P&gt;hello&lt;BR /&gt;&lt;BR /&gt;We have an issue with&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;authorize.net-hosted iframe that produces duplicate transactions from time to time&lt;BR /&gt;&lt;BR /&gt;How to prevent it?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Payment managed by&amp;nbsp;&amp;nbsp;authorize.net-hosted iframe&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 14:40:22 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90783#M57064</guid>
      <dc:creator>Umbraco</dc:creator>
      <dc:date>2024-11-20T14:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: authorize.net-hosted iframe duplicate transactions</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90789#M57070</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hosted payment requests rely on the token generated by the 'getHostedPaymentPageRequest' request. This token is valid for a single transaction, so any resubmitted payment should result in the message "&lt;STRONG&gt;A duplicate transaction has been submitted.&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;If a user goes back and submits again, a new token will be generated, potentially causing a duplicate transaction.&lt;/P&gt;&lt;P&gt;I would appreciate details about the transaction and the timestamp it occurs so we can debug this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Nov 2024 05:46:29 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90789#M57070</guid>
      <dc:creator>dipespat</dc:creator>
      <dc:date>2024-11-21T05:46:29Z</dc:date>
    </item>
    <item>
      <title>Re: authorize.net-hosted iframe duplicate transactions</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90813#M57089</link>
      <description>&lt;P&gt;(we are working with the OP)&lt;/P&gt;&lt;P&gt;Here are two examples:&lt;BR /&gt;80682192108 and 80682202471&lt;BR /&gt;80568841789 and 80568831444&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 16:57:25 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/authorize-net-hosted-iframe-duplicate-transactions/m-p/90813#M57089</guid>
      <dc:creator>vrapp</dc:creator>
      <dc:date>2024-11-22T16:57:25Z</dc:date>
    </item>
  </channel>
</rss>

