What Are ACH SEC Codes? PPD, CCD, WEB, and TEL Explained
ACH SEC codes tell banks how you got permission to debit. Learn when to use PPD, CCD, WEB or TEL and how the wrong code raises your return risk.

Photo: Pixabay
On this page 7 sections
ACH SEC codes are three-letter labels on every ACH entry. They tell the banks two things: what kind of account the money is moving into or out of, and how you got the account holder's permission. Pick the code that matches how you actually collected authorization:
- PPD for a consumer who signed or similarly authenticated a written authorization.
- CCD for a business account under an agreement.
- WEB for a consumer who authorized online or in an app.
- TEL for a consumer who authorized by phone.
The code determines which authorization rules apply and how long the customer's bank has to send a debit back. A wrong code can leave you exposed for weeks longer than you planned.
If you're new to bank payments, start with our explainer on how ACH payments move money between business bank accounts, then come back here.
What Nacha Standard Entry Class Codes Do
Nacha standard entry class codes are defined in the Nacha Operating Rules. Nacha is the organization that governs the ACH Network, and its rules are network rules, not federal law. They bind you through the agreement you sign with your bank or payment provider. That bank is the ODFI (originating depository financial institution). The customer's bank is the RDFI (receiving depository financial institution).
When you send a batch of ACH entries, the SEC code sits in the batch header. Your gateway or accounting software usually fills it in from a setting, and that setting is where most mistakes start. A business picks one default code, often whatever the onboarding rep chose, and every debit goes out under it. That happens even when one customer signed a paper form, another clicked a box on the website and a third read their account number over the phone.
Nacha defines many codes, including some for converted paper checks and some for international transfers. For businesses collecting payments from customers, four do most of the work. Debits from consumer accounts can also be subject to federal consumer-protection law, so a consumer authorization may need to satisfy both the network rules and legal requirements. Your bank and an attorney can tell you which requirements apply to your setup.
PPD: Consumer Payments With Written Authorization
PPD (Prearranged Payment and Deposit) covers entries to consumer accounts where the authorization is in writing and signed or similarly authenticated. Typical PPD debits include:
- A parent signs a tuition payment plan at a school's front office.
- A member fills out a paper enrollment form at the gym.
- A client signs a service agreement with a bank authorization section.
PPD also carries most payroll direct deposits, which are credits rather than debits.
A PPD authorization can cover one payment or a standing series. For recurring debits, a well-built authorization spells out the amount (or how it's calculated), the timing, the account being debited and how the customer can revoke it. The customer also gets a copy. Variable amounts, such as usage-based billing, can trigger advance-notice obligations before each debit. Get the exact requirements from your ODFI and the current Nacha rules before you finalize your form. Our guide to billing recurring customers by bank instead of card covers the business side of that decision.
PPD vs. CCD: Code From the Account Type
CCD (Corporate Credit or Debit) covers entries to business accounts. A common example is a wholesale distributor debiting a retailer's operating account under terms the retailer accepted in its credit application. CCD requires an agreement between the two companies. It doesn't carry the consumer-style form and disclosure expectations that PPD does. CCD entries can also include remittance details such as invoice numbers in an addenda record, which helps the receiving company's accounts payable team match the payment. Ask your bank how much remittance data its CCD setup supports.
The PPD vs. CCD question trips people up because they look at who the customer is instead of where the money comes from. Two cases show the difference:
- A sole proprietor pays your invoice from a personal checking account. The customer is a business, but the account is a consumer account, so the debit needs a consumer code.
- A homeowner pays from their LLC's account. The customer is a consumer, but the account belongs to a business.
When you're unsure, add a question to the authorization form asking whether the account is personal or business, and code from the answer.
Some originators are tempted to code consumer debits as CCD to get the shorter corporate return window. That doesn't work. The consumer's bank can still return the debit as unauthorized under consumer timeframes. Coding to sidestep consumer protections also breaks the agreement you signed with your bank, and banks review originators whose return patterns point that way.
WEB and TEL: Online and Phone Authorizations
The WEB ACH code covers consumer debits authorized over the internet or a wireless network, as long as the authorization isn't spoken. Examples include:
- An online checkout.
- A donation form.
- A membership signup inside an app.
- A payment link the customer completes on their phone.
A recurring debit authorized online stays WEB for the life of the authorization. A monthly subscription set up on your website is WEB in month one and still WEB in month twelve.
WEB carries security expectations that PPD doesn't. Your bank will want to know how you screen online authorizations for fraud, whether you validate a customer's account number before the first debit, how you protect account data in transit and how often you review your data security. Get the current WEB requirements from your bank's origination agreement instead of guessing. Account validation is the piece most businesses can act on right away: instant bank account verification stops ACH returns before you debit and gives you a record that you checked.
TEL ACH authorization covers consumer debits authorized by phone, and the capture method depends on whether the payment is single or recurring. For a one-time TEL debit, you can either record the customer's spoken authorization or send written notice confirming the terms before the debit settles. The written-notice option does not cover recurring signups. Recurring phone authorizations face a stricter standard for how the call is captured and what copy of the authorization the customer receives. Get your bank's current requirements in writing before you script a recurring phone enrollment.
In both cases, your bank will expect the script to cover the specifics: the date, the amount, the account being debited, a phone number for questions and how to revoke. TEL is meant for calls where you already have a relationship with the customer or the customer called you. A cold call to a stranger doesn't produce a valid TEL authorization.
Return Windows by ACH SEC Code
Returns fall into two groups. Administrative returns, such as insufficient funds, a closed account or an invalid account number, generally come back within a couple of banking days whatever the code. Unauthorized returns are where the SEC code changes your exposure.
| Code | Account type | How authorization was collected | Window for an "unauthorized" return |
|---|---|---|---|
| PPD | Consumer | Signed or similarly authenticated writing | Extended: runs for weeks after settlement |
| WEB | Consumer | Online or app, non-voice | Extended: runs for weeks after settlement |
| TEL | Consumer | Recorded call or written confirmation | Extended: runs for weeks after settlement |
| CCD | Business | Agreement between the companies | Short: a couple of banking days |
The exact day counts are set by the Nacha rules and can change, so confirm them in the current rules or with your bank.
On consumer accounts, a customer who says they never authorized a debit can claim the money back long after you've shipped the order or delivered the service. Your defense is the authorization record. Each unauthorized return also counts toward your unauthorized return rate, which your bank monitors against Nacha thresholds. Our guide to ACH return codes like R01, R10 and R29 explains which codes count toward that rate and what each one tells you.
Example: A Nonprofit Choosing the Right Code for Donations
Here's an illustrative case. A regional food bank collects recurring gifts through four channels, and all of them feed one donor database. The assumptions:
- Annual gala: donors fill out paper pledge cards with a signed monthly bank-debit section.
- Website: a monthly giving form where donors type in their routing and account numbers.
- Spring phone drive: donors call a hotline, and volunteers enroll them on recorded lines.
- Local sponsors: businesses pay sponsorships from business checking under signed sponsorship agreements.
The right codes follow from the authorization channel and the account type:
| Donation channel | Account debited | SEC code |
|---|---|---|
| Gala pledge card, signed | Personal checking | PPD |
| Website monthly form | Personal checking | WEB |
| Phone drive, donor called in, recorded | Personal checking | TEL |
| Sponsorship agreement | Business checking | CCD |
| Gala pledge card, donor's family business account | Business checking | CCD |
The last row repeats the PPD vs. CCD lesson: the same pledge card, a different account and a different code. The phone drive deserves a second look too. These are recurring gifts, so the food bank should confirm with its bank that its recording and confirmation process meets the recurring TEL requirements before the drive starts. If volunteers later start calling past donors to re-enroll them, ask the bank before anyone dials whether a prior gift counts as an existing relationship. Purchased lists of non-donors should never be used for phone enrollment.
The practical fix is to store the enrollment source and account type on each donor record and have the gateway send the code from that field instead of a single default. The same approach works for schools with tuition plans and for subscription businesses with mixed signup channels. Our page on payment processing for nonprofits and churches covers the giving setups we support.
Authorization Records You Must Keep
The Nacha rules require you to keep each authorization for a set period after it ends or is revoked, and your bank can ask for a copy on short notice. If a donor or customer disputes a debit and you can't produce the record, you will usually lose. What to keep depends on the code:
- PPD: the signed paper form or the e-signature record, plus the copy you gave the customer.
- CCD: the signed agreement, any updated terms, and the name of the person at the business who authorized the debit.
- WEB: the exact authorization language shown on screen, the customer's acceptance with a timestamp, the account validation result and how you confirmed who the customer was.
- TEL: the audio recording or, for single payments, the written confirmation notice and proof of when you sent it. Also keep the call script in use that day.
For wording, sample forms and storage practices, see ACH authorization requirements: forms, wording and proof. This article is general information, not legal advice. Confirm your obligations with your bank and a qualified attorney, especially for recurring consumer debits.
Your first task this week: export every active recurring ACH authorization and add two columns, one for how it was collected and one for whether the account is personal or business. Then compare each row with the SEC code your system actually sends. Every mismatch is a return risk you can fix before a customer's bank finds it. If you're reviewing your payment setup at the same time, you can request a free quote from a MannyPay specialist and hear back within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


