<?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 Looking for Custom API Solution: Auto-Retry Failed Payments Using Secondary Card/s in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Looking-for-Custom-API-Solution-Auto-Retry-Failed-Payments-Using/m-p/94814#M4062</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We’re looking for guidance and/or a &lt;STRONG&gt;developer referral&lt;/STRONG&gt; for a &lt;STRONG&gt;custom Authorize.Net API solution&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Our setup:&lt;/STRONG&gt;&lt;BR /&gt;• &lt;STRONG&gt;WooCommerce Subscriptions&lt;/STRONG&gt; manages recurring billing&lt;BR /&gt;• &lt;STRONG&gt;Authorize.Net&lt;/STRONG&gt; stores customer payment profiles with &lt;STRONG&gt;multiple cards on file (CIM)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Requirement:&lt;/STRONG&gt;&lt;BR /&gt;When a subscription payment fails on the default card, we want to automatically attempt charging another saved card under the same customer profile in Authorize.Net, without manual intervention.&lt;/P&gt;&lt;P&gt;We understand this is not a native feature in Authorize, and we’re specifically exploring whether this can be done via custom API logic.&lt;/P&gt;&lt;P&gt;We’d appreciate help with:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Confirmation that this workflow is technically feasible via Authorize.Net APIs&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Any known limitations or best practices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Recommendations or contact from certified developers who have built similar solutions&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jan 2026 13:32:07 GMT</pubDate>
    <dc:creator>DANNAV0210</dc:creator>
    <dc:date>2026-01-06T13:32:07Z</dc:date>
    <item>
      <title>Looking for Custom API Solution: Auto-Retry Failed Payments Using Secondary Card/s</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Looking-for-Custom-API-Solution-Auto-Retry-Failed-Payments-Using/m-p/94814#M4062</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We’re looking for guidance and/or a &lt;STRONG&gt;developer referral&lt;/STRONG&gt; for a &lt;STRONG&gt;custom Authorize.Net API solution&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Our setup:&lt;/STRONG&gt;&lt;BR /&gt;• &lt;STRONG&gt;WooCommerce Subscriptions&lt;/STRONG&gt; manages recurring billing&lt;BR /&gt;• &lt;STRONG&gt;Authorize.Net&lt;/STRONG&gt; stores customer payment profiles with &lt;STRONG&gt;multiple cards on file (CIM)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Requirement:&lt;/STRONG&gt;&lt;BR /&gt;When a subscription payment fails on the default card, we want to automatically attempt charging another saved card under the same customer profile in Authorize.Net, without manual intervention.&lt;/P&gt;&lt;P&gt;We understand this is not a native feature in Authorize, and we’re specifically exploring whether this can be done via custom API logic.&lt;/P&gt;&lt;P&gt;We’d appreciate help with:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Confirmation that this workflow is technically feasible via Authorize.Net APIs&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Any known limitations or best practices&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Recommendations or contact from certified developers who have built similar solutions&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Thank you in advance!&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 13:32:07 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Looking-for-Custom-API-Solution-Auto-Retry-Failed-Payments-Using/m-p/94814#M4062</guid>
      <dc:creator>DANNAV0210</dc:creator>
      <dc:date>2026-01-06T13:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Custom API Solution: Auto-Retry Failed Payments Using Secondary Card/s</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/Looking-for-Custom-API-Solution-Auto-Retry-Failed-Payments-Using/m-p/94950#M4124</link>
      <description>&lt;P&gt;Hi! Yes, what you’re looking to do is technically feasible with a custom solution. You’d need to implement backend logic that:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Detects when a subscription payment fails via webhook or API response.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Pulls the customer’s saved payment profiles from Authorize.Net (CIM).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Attempts charging the next available card automatically.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Updates the subscription status based on the outcome.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;It’s important to handle retries carefully to avoid multiple declined charges and ensure compliance with payment rules. Others have discussed similar auto-retry workflows for recurring payments, which might be helpful:&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;A href="https://community.developer.cybersource.com/t5/Integration-and-Testing/Retry-failed-ARB-payments/td-p/65135" target="_self"&gt;https://community.developer.cybersource.com/t5/&lt;/A&gt;&lt;A href="https://realestateagentslondon.co.uk/" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;visit site&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="https://community.developer.cybersource.com/t5/Integration-and-Testing/Retry-failed-ARB-payments/td-p/65135" target="_blank" rel="noopener"&gt;Integration-and-Testing/Retry-failed-ARB-payments/td-p/65135&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 14:29:14 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/Looking-for-Custom-API-Solution-Auto-Retry-Failed-Payments-Using/m-p/94950#M4124</guid>
      <dc:creator>johncarter12</dc:creator>
      <dc:date>2026-03-04T14:29:14Z</dc:date>
    </item>
  </channel>
</rss>

