--- description: Learn how payment teams handle Chase stop payment ACH and card declines, isolate hard revocation codes, and prevent Nacha fines with smart retry logic. title: Chase Stop Payments: How to Handle ACH and Card Declines image: https://cdn.smartretry.com/cdn-cgi/image/width=1200,height=630,quality=85,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Fhandling-chase-stop-payment-ach-declines.jpg --- Payment Approval Optimization # Managing Chase Stop Payments: Why Recurring Billing Retries Backfire Published October 31, 2026 Last updated October 31, 2026 ![Reading time](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fclock.337f-cmnyb532.svg)10 min ![](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=85,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Fhandling-chase-stop-payment-ach-declines.jpg) ## Still letting failed transactions slip through? SmartRetry turns declines into approvals - automatically, intelligently, and without changing your payment provider. Table of Contents ![](https://cdn.smartretry.com/cdn-cgi/image/width=48,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Fblog_star.1bil3v51fayky.svg) When a subscriber asks their bank to halt an upcoming debit, automated dunning logic often mistakes the block for a soft decline. Recognizing a **Chase stop payment** early allows recurring billing teams to suppress illegal retries and protect their merchant processing accounts. Key Takeaways 1. Receiving a **Nacha return code R08** signifies a formal stop payment that prohibits any reinitiation without explicit new consent. 2. Retrying stopped ACH debits can breach Nacha's strict **0.5 percent threshold** for unauthorized returns, risking processor suspension. 3. Card network responses like **Visa code R0** or Mastercard 04 represent hard revocations that must immediately halt recurring retries. 4. Proactively resolving stop payments via **plain-text communication** prevents consumers from escalating billing stops into costly chargebacks. When a customer tells Chase Bank to block your upcoming debit, your automated billing logic faces an immediate test. A stop payment is not a temporary hiccup like insufficient funds but a formal revocation of permission. If your system treats that response like a routine declined payment and schedules another attempt, you risk regulatory penalties, network fines, and processor intervention. Subscription businesses need to recognize these signals early and halt automated retries on that payment method immediately. **When Chase Bank Says Stop: The Hidden Traps of Recurring Billing** For teams managing recurring revenue, the instinct is almost always to recover the transaction. Conventional subscription wisdom says that when a payment fails, you wait a few days and try again. That works when a paycheck is delayed by a weekend or a card briefly hits its limit. But when a consumer skips your cancellation page and asks their bank to block a debit, the rules change completely. In fact, half of Gen Z consumers report blocking payments to cancel a subscription. As one of the largest retail banks and card issuers in the United States, JPMorgan Chase represents a substantial share of almost every domestic merchant’s recurring portfolio. When a customer places a stop payment through Chase, whether on a checking account or a credit card, the bank translates that request into specific network signals. Understanding how those signals reach you through your payment processor is essential for keeping recovery operations compliant and effective. ## How a Chase Stop Payment ACH Order Actually Works Behind the Scenes Blocking a transaction through a bank’s app or customer service line is simple for consumers. Behind that clean interface, though, the mechanics depend on the payment rail. An [Automated Clearing House (ACH)](https://www.smartretry.com/glossary/automated-clearing-house) transaction falls under a completely different regulatory framework than a [Visa](https://www.smartretry.com/payment-providers/visa) or [Mastercard](https://www.smartretry.com/payment-providers/mastercard) transaction, even when Chase issues both. When a consumer initiates a chase stop payment ach request, they are exercising a right protected by the Electronic Fund Transfer Act (EFTA) and the operating rules of Nacha, which governs the ACH network. To block a preauthorized recurring transfer, the consumer can notify the bank orally or in writing at least three business days before the scheduled transfer date. In practice, a customer usually logs into Chase or calls a representative, identifies the merchant from a past statement, and requests the block. Merchants see none of this and get no early warning. You submit your recurring debits as usual, and a few days later the transaction bounces back through the network. That return carries Nacha return reason code R08, Payment Stopped. Unlike R01 (Insufficient Funds) or R09 (Uncollected Funds), R08 means the account holder deliberately blocked that specific debit. It is also worth distinguishing R08 from R07 (Authorization Revoked by Customer). An R08 stop payment on ach technically applies to a single upcoming debit, or a defined series depending on how the bank configures the block. An R07 means the customer has formally ended the standing authorization with the merchant. Day to day, though, treating an R08 with the same caution as a full revocation is the safest approach. ![Diagram illustrating the routing sequence of a Chase ACH stop payment order returning code R08 to merchant billing logic.](https://cdn.smartretry.com/uploads/2026/10/chase-ach-stop-payment-return-flow-768x429.jpg) ## Navigating ACH Stop Payment Rules Without Triggering Network Fines The rules for handling returned bank debits are strict, and Nacha monitors return rates closely through acquiring banks and processors. Under standard ach stop payment rules, once an entry is returned with an R08 code, the merchant cannot reinitiate it unless the consumer provides a new authorization. Why is the network so protective? ACH runs on trust and batch processing rather than real-time authorization, so the receiving bank (in this case, Chase) generally assumes the merchant holds a valid authorization. When the consumer overrides that trust with a stop payment, the network steps in to protect them from unwanted withdrawals. If your billing engine ignores an R08 and retries on the same schedule it uses for insufficient funds, several risks emerge: * **Unauthorized Return Thresholds:** If you reinitiate a stopped payment without new permission, the consumer is likely to report it as unauthorized (return code R10). Under Nacha rules, sanctions for a Class 3 violation can reach up to $500,000 per occurrence [(Source)](https://www.nacha.org/rules/reversals-and-enforcement). Nacha also enforces a 3% threshold for administrative return codes [(Source)](https://www.checkout.com/blog/ach-returns-explained). * **Originator Watchlists:** Payment service providers watch for merchants who keep submitting entries after hard return codes. Automated retries on R08 returns are an easy pattern for risk teams to spot and often lead to reserve requirements or account termination. To stay compliant, your integration must parse the specific three-character Nacha return code instead of lumping all bank failures under a generic status. The moment an R08 arrives, billing for that mandate should pause until the customer explicitly authorizes a new payment. ## Chase Recurring Billing on Cards and the Nuance of Card Decline Codes The term stop payment comes from paper checks and bank transfers, but consumers bring the same mindset to their cards. When a cardholder calls Chase to block a subscription on a Sapphire or Freedom card, or uses digital tools to manage stored credentials, the result looks very different in your gateway logs. On cards, a request to halt Chase recurring billing does not generate an R08\. It flows through the Visa or Mastercard rails during real-time authorization and comes back as specific [card decline codes](https://www.smartretry.com/blog/card-declines-guide). Merchants were left to guess whether the customer was over their limit, traveling abroad, or actively trying to cancel. In recent years, Visa and Mastercard have overhauled their issuer response frameworks to give merchants clearer signals. Today, when a Chase cardholder blocks a recurring merchant, you are much more likely to see one of these responses: * **Revocation of All Authorizations Order (Visa R1 / R3):** The customer has asked the bank to block all recurring billing on their account, or has closed out a series of recurring credentials. The networks pair these clearer codes with strict retry rules. Visa and Mastercard separate [soft declines](https://www.smartretry.com/blog/hard-vs-soft-declines-retry-strategy), such as insufficient funds or system timeouts, from hard declines like invalid account numbers or revoked authorizations. Retrying a card after a revocation code violates network rules and incurs non-compliance fees for every subsequent attempt. Repeated retries after a hard decline also drag down your approval rate, which can affect how issuer fraud models score your legitimate transactions over time. ![Visual depiction of account authorization degradation and penalty assessment following recurring hard declines on Chase cards.](https://cdn.smartretry.com/uploads/2026/10/card-authorization-degradation-hard-declines-768x429.jpg) ## Chargebacks vs Stop Payments: Timing Is the Only Difference Payment operations teams often treat stop payments and chargebacks as separate buckets, one in the billing and recovery workflow, the other with the risk and disputes team. In reality, chargebacks vs stop payments are two sides of the same consumer intent. The main difference is the clock. A stop payment is proactive. The consumer knows a recurring charge is coming, perhaps from a renewal reminder or last month’s charge, and asks Chase to put up a wall before the money leaves their account. A chargeback is reactive. The consumer sees the posted transaction, decides they did not want it or thought they had already canceled, and asks Chase to claw the money back. Why go to Chase instead of clicking cancel on your website? Sometimes they forgot their password, or your cancellation flow requires a phone call during business hours they cannot make. Others simply trust their banking app as the control center for their finances. In fact, 85% of consumers want to manage subscriptions through their banking app [(Source)](https://www.paymentsjournal.com/the-tools-unlocking-next-gen-digital-banking-experiences/). Furthermore, 52% of consumers desire the ability to cancel subscriptions directly in their banking app [(Source)](https://www.paymentsjournal.com/the-tools-unlocking-next-gen-digital-banking-experiences/). If a merchant works around a stop payment, for example by falling back to a secondary payment method without telling the user or altering the merchant descriptor so a retry slips past the bank’s filter, the victory is short-lived. Once that charge posts, the stop payment becomes a chargeback. Because the customer already told their bank to block you, the dispute will carry an unauthorized transaction or canceled recurring transaction reason code. Those are nearly impossible to win without proof the customer re-authorized the charge after their stop payment order. ![Conceptual visualization of a bypassed stop payment escalating into an unauthorized chargeback dispute.](https://cdn.smartretry.com/uploads/2026/10/stop-payment-chargeback-escalation-cycle-768x429.jpg) ## Building Smarter Retry Rules and Recovery Flows The takeaway is not that you must abandon all revenue when a stop payment occurs. You must change the channel, shifting immediately from automated retries to transparent customer communication. To handle subscription payment issues without running afoul of Chase or the networks, teams need to audit how their systems ingest and act on failure data. A basic billing system treats a declined transaction as binary, failed or succeeded. An optimized architecture looks at the exact type of failure before deciding what to do next. Today, more than 90% of eCommerce merchants employ authorization-boosting tools such as automated retries [(Source)](https://info.merchantriskcouncil.org/hubfs/Reports/Fraud%20Reports/2024%5FGlobal%5FPayments%5Fand%5FFraud%5FReport.pdf). Here is how experienced payment teams structure retry rules and recovery flows around stop payment signals: ### 1\. Map Gateway Translations to Raw Network Codes Many payment service providers simplify bank responses into friendly categories like declined or bank\_error. That helps on a checkout screen but can hide critical compliance signals in recurring billing. Make sure your engineers pull the raw Nacha return code (like R07 or R08) and the raw card network response codes (like R0, R1, or Mastercard’s [Merchant Advice Codes](https://www.smartretry.com/blog/merchant-advice-codes)) from the webhook payload. ### 2\. Isolate Hard Declines in Your Retry Logic Once you can see the raw codes, build a hard stop into your scheduling. If a transaction returns an R08 on ACH or a revocation code on card rails, the system should cancel all scheduled retries for that invoice and pause the subscription. Platforms like SmartRetry analyze real-time issuer response codes and Nacha return reasons, suppressing retries on revoked authorizations and focusing retry schedules on recoverable soft declines so merchants can safely improve payment optimization. ### 3\. Audit Your Fallback Payment Logic Many subscription platforms let users store a backup payment method. If a primary card expires, falling back to a secondary card is a great way to reduce involuntary churn. But if the primary method failed because of a stop payment order, charging the backup invites an immediate chargeback and an angry customer. Configure fallback logic so revocation codes pause billing for the entire account, not just the individual payment instrument. ### 4\. Shift to an Empathetic Out-of-Band Recovery Email Not every stop payment is hostile. A customer may see an unfamiliar corporate legal name on their statement, not recognize your brand, and ask Chase to block future charges out of caution. Globally, 25% of consumers have blocked a payment they believed was fraudulent [(Source)](https://www.mastercard.com/us/en/news-and-trends/Insights/2026/the-future-of-subscription-management.html). Or a joint account holder blocks a charge without realizing their partner signed up for your service. Instead of retrying the card, send an automated plain-text email the moment an R08 or revocation code is recorded. Explain that their bank blocked the recent billing attempt at their request, confirm that you have paused their subscription so no further attempts will be made, and include a simple link to confirm the cancellation or update their payment method if the block was a mistake. This transparency builds trust, clears up descriptor confusion before it becomes a dispute, and occasionally wins back a customer who blocked the charge by accident. ## The Strategic Value of Knowing When to Walk Away In recurring revenue, it is easy to fixate on maximizing every approval. Teams spend months fine-tuning retry cadences, testing [account updater services](https://www.smartretry.com/glossary/account-updater), and routing transactions to cut declines by fractions of a percent. Yet a mature payment strategy is defined as much by the transactions you choose not to send as by the ones you recover. When a customer goes to the trouble of placing a stop payment on ach or asking a Chase representative to revoke a card authorization, the payment rails are doing their job by passing that message back to you. Listening the first time protects your merchant accounts from network fines, preserves your standing with major issuers, and keeps recovery focused on customers who genuinely want to keep paying you and just need help getting past a temporary failure. ### Frequently asked questions about this topic How do ACH stop payment rules apply to recurring billing retries? Under Nacha rules, merchants cannot reinitiate an ACH debit returned with code R08 without obtaining fresh authorization from the consumer. Automated retries violate network rules and trigger compliance fines. What happens when a customer initiates a Chase stop payment ACH request? Chase blocks the preauthorized recurring debit under EFTA rules, returning the transaction with Nacha code R08\. Merchants receive no advance warning before the returned payment bounces back through the ACH network. When is an ACH stop payment form required by a bank? Banks like Chase often require consumers to submit a written confirmation or stop payment form within 14 days of an oral request to keep the debit block active across subsequent billing cycles. What is the operational risk of placing a stop payment on ACH transactions? Retrying an account after an ACH stop payment risks pushing unauthorized return rates above Nacha's 0.5% threshold, leading to processor penalties, rolling reserve mandates, or origination termination. #### Share this article [![Share on X](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ftwitter.21z6yr9njnznr.svg)](https://twitter.com/intent/tweet?text=Managing%20Chase%20Stop%20Payments%3A%20Why%20Recurring%20Billing%20Retries%20Backfire&url=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fchase-stop-payment-ach-rules "Share on X")[![Share on Facebook](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Ffacebook.3sbfjbsxa26qg.svg)](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fchase-stop-payment-ach-rules "Share on Facebook")[![Share on LinkedIn](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Flinkedin.09sdc8tnlrn4a.svg)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.smartretry.com%2Fblog%2Fchase-stop-payment-ach-rules "Share on LinkedIn") Make us your preferred source ![Kyle Regacho](https://cdn.smartretry.com/cdn-cgi/image/width=256,quality=75,format=auto,fit=cover/https%3A%2F%2Fsecure.gravatar.com%2Favatar%2Faa4329c7f45a68c68f2fbccab899d0f43f3740f3f9e92d5c6ea711171fc1a35f%3Fs%3D96%26d%3Dmm%26r%3Dg) Author ##### Kyle Regacho Marketing Developer [![LinkedIn](https://cdn.smartretry.com/cdn-cgi/image/width=32,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2F_next%2Fstatic%2Fmedia%2Flinkedin.09sdc8tnlrn4a.svg)Find me on Linkedin](https://www.linkedin.com/in/kdregacho/) Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue [Read all articles >](/authors/kyle-regacho) ## Join our newsletter! Real strategies to recover lost revenue - straight to your inbox ## Articles you may find interesting: [View all](/blog) [![Verifying Your Payment Security Posture to Protect Authorization Rates](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Fverify-payment-security-posture-authorization-rates-hero.jpg) October 22, 2026 Verifying Your Payment Security Posture to Protect Authorization Rates Outsourcing checkout does not eliminate PCI obligations. Learn how verifying your payment posture, isolating card data, and auditing scripts safeguards issuer trust and prevents avoidable card declines across your payment pipeline.](/blog/verify-payment-security-posture-authorization-rates)[![The Hidden Mechanics of Recovering Failed PayPal Transactions](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Frecovering-failed-paypal-transactions-hero.jpg) October 19, 2026 The Hidden Mechanics of Recovering Failed PayPal Transactions Discover the underlying mechanics of digital wallet failures on PayPal and how dynamic recovery strategies protect recurring subscription revenue from churn.](/blog/recovering-failed-paypal-transactions)[![Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Fcvv-errors-causes-merchant-solutions-hero-1.jpg) September 15, 2026 Solving CVV Mismatch Declines: Root Causes and Practical Remediation for Merchants Discover why CVV mismatch errors trigger costly false declines across gateways. Learn how to refine risk thresholds, implement dynamic validation, and leverage network tokens to recover revenue without sacrificing security.](/blog/cvv-errors-causes-merchant-solutions)[![Why Good Transactions Go Bad: Unpacking Payment Failures and How to Fix Them](https://cdn.smartretry.com/cdn-cgi/image/width=3840,quality=75,format=auto,fit=cover/https%3A%2F%2Fcdn.smartretry.com%2Fuploads%2F2026%2F10%2Fpayment-failures-issuer-declines-recovery.jpg) October 27, 2026 Why Good Transactions Go Bad: Unpacking Payment Failures and How to Fix Them Payment failures are rarely simple rejections. Discover how leading fintech teams eliminate false declines, optimize network tokens, and deploy intelligent recovery to protect recurring revenue and preserve issuer relationships.](/blog/fix-payment-failures-decline-recovery) --- ```json {"@context":"https://schema.org","@type":"BlogPosting","headline":"Managing Chase Stop Payments: Why Recurring Billing Retries Backfire","url":"https://www.smartretry.com/blog/chase-stop-payment-ach-rules","datePublished":"2026-10-31T07:17:24.000Z","dateModified":"2026-10-31T07:24:03.000Z","image":"https://cdn.smartretry.com/uploads/2026/10/handling-chase-stop-payment-ach-declines.jpg","description":"Learn how payment teams handle Chase stop payment ACH and card declines, isolate hard revocation codes, and prevent Nacha fines with smart retry logic.","publisher":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry","https://github.com/smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.smartretry.com/blog/chase-stop-payment-ach-rules","name":"Managing Chase Stop Payments: Why Recurring Billing Retries Backfire"},"inLanguage":"en","author":{"@type":"Person","@id":"https://www.smartretry.com/authors/kyle-regacho","name":"Kyle Regacho","url":"https://www.smartretry.com/authors/kyle-regacho","jobTitle":"Marketing Developer","image":"https://secure.gravatar.com/avatar/aa4329c7f45a68c68f2fbccab899d0f43f3740f3f9e92d5c6ea711171fc1a35f?s=96&d=mm&r=g","sameAs":["https://www.linkedin.com/in/kdregacho/"]},"articleSection":"Payment Approval Optimization","wordCount":1978,"keywords":"chase stop payment ach, ach stop payment rules, stop payment on ach, ach stop payment form, Nacha return code R08, recurring billing retry logic, Chase, card decline codes"} {"@context":"https://schema.org","@type":"FAQPage","author":{"@type":"Organization","@id":"https://www.smartretry.com/#organization","name":"SmartRetry","url":"https://www.smartretry.com","logo":{"@type":"ImageObject","url":"https://cdn.smartretry.com/logo.png","width":{"@type":"QuantitativeValue","value":175,"unitCode":"PX"},"height":{"@type":"QuantitativeValue","value":29,"unitCode":"PX"}},"description":"SmartRetry is a smart payment recovery platform that helps businesses save revenue from failed payment transactions and reduce false declines.","sameAs":["https://x.com/smartretry","https://www.facebook.com/smartretry","https://www.instagram.com/smartretry","https://www.linkedin.com/company/smartretry","https://www.youtube.com/@smartretry","https://github.com/smartretry"],"contactPoint":{"@type":"ContactPoint","contactType":"customer support","availableLanguage":["Hebrew","English"],"url":"https://www.smartretry.com/contact"},"address":{"@type":"PostalAddress","streetAddress":"Menachem Begin","addressLocality":"Tel Aviv-Yafo","addressCountry":"IL"}},"mainEntity":[{"@type":"Question","name":"How do ACH stop payment rules apply to recurring billing retries?","acceptedAnswer":{"@type":"Answer","text":"Under Nacha rules, merchants cannot reinitiate an ACH debit returned with code R08 without obtaining fresh authorization from the consumer. Automated retries violate network rules and trigger compliance fines."}},{"@type":"Question","name":"What happens when a customer initiates a Chase stop payment ACH request?","acceptedAnswer":{"@type":"Answer","text":"Chase blocks the preauthorized recurring debit under EFTA rules, returning the transaction with Nacha code R08. Merchants receive no advance warning before the returned payment bounces back through the ACH network."}},{"@type":"Question","name":"When is an ACH stop payment form required by a bank?","acceptedAnswer":{"@type":"Answer","text":"Banks like Chase often require consumers to submit a written confirmation or stop payment form within 14 days of an oral request to keep the debit block active across subsequent billing cycles."}},{"@type":"Question","name":"What is the operational risk of placing a stop payment on ACH transactions?","acceptedAnswer":{"@type":"Answer","text":"Retrying an account after an ACH stop payment risks pushing unauthorized return rates above Nacha's 0.5% threshold, leading to processor penalties, rolling reserve mandates, or origination termination."}}]} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.smartretry.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.smartretry.com/blog"},{"@type":"ListItem","position":3,"name":"Managing Chase Stop Payments: Why Recurring Billing Retries Backfire","item":"https://www.smartretry.com/blog/chase-stop-payment-ach-rules"}]} ```