Skip to content
⌘K
InboxAsk a human

Send proof of authorization (POA) for a payment

Updated by Kayla

Proof of authorization (POA) is the record that shows your customer agreed to a specific payment. When Straddle asks for it, send the record for that payment so Straddle can release the payment or answer the bank that asked. This article is for whoever on your team keeps your customers' authorization records, usually operations or compliance.

When Straddle asks for POA

Straddle asks for POA in three situations, and each sets its own deadline.

  • A payment is over your processing limits. Straddle holds the payment for review until it receives POA. Send the full authorization record for that payment as soon as you can, and within 24 hours (one business day). See Manage your processing limits.
  • A bank asks for proof against a dispute. Straddle's bank partner or your customer's bank can ask for POA when a customer disputes a payment, a payment is returned (for example, with return code R05, R07, R10, R29, or R51), or a customer signs a written statement of unauthorized debit (WSUD). The bank's request sets the deadline. Most WSUD responses must reach the bank within 10 banking days of its request, so send yours as soon as Straddle asks.
  • An audit or spot check. Straddle, its bank partner, or a regulator can ask for the authorization records for a sample of your payments. The request states the deadline.

What to send

What counts as POA depends on two things: how your customer authorized the payment, online or signed (including e-signature), and whether your customer is a consumer or a business. Together they set the payment's SEC code and the records you need.

Your customerHow they authorizedTypical SEC codeWhat to send
ConsumerOnline, on the web or in a mobile app (clickwrap)WEB (debit)The authorization language they saw, a record of how you authenticated them (digital signature, PIN, shared secret, biometric, or a similar method), and their IP address, device, and timestamp
ConsumerSigned, on paper or by e-signaturePPD (debit)The signed authorization, as the original or an e-signed copy from DocuSign, Adobe Sign, or a similar service, with clear terms
BusinessSigned contractCCD (debit)The signed trading partner or service agreement that binds your customer to the Nacha Rules and contains the authorization terms
BusinessOnline, with no signed contractCCD (debit)The same records as a consumer online payment
ConsumerOral (credits only)PPD (credit)A note of the oral authorization, or other non-written proof, such as a voided check

Straddle sends every business payment as CCD. How your business customer authorized it, by signed contract or online, decides which records you send as proof.

Online authorization

For a payment your customer authorized on the web or in an app, send all five of these records:

  • Authorization language: the exact text your customer agreed to, as it appeared on screen when they agreed. It must include express authorization to debit the account (and to credit it, where that applies), the amount and frequency (single, recurring, or standing), your customer's right to revoke and how to do it, and your business name and support contact.
  • Authentication record: evidence that identifies your customer and shows their consent, linked to the authorization. Accepted forms are a digital signature, a secure code or PIN, a shared secret (for example, an account credential pass-through), and biometric verification.
  • Payment details: the date and timestamp of consent, your customer's IP address and device details, the email address or phone number they used, the bank name and last four digits of the account, and the item purchased or reason for the debit.
  • Customer details: the name on the account, the shipping or billing address, and any other identity verification you used.
  • Receipt: evidence that you sent your customer a receipt or confirmation, such as an email send log or a capture of the on-screen confirmation.

Signed (PPD or CCD) authorization

For a payment your customer authorized by signature, send these records:

  • Signed authorization or agreement: the original or an e-signed copy. For CCD, a trading partner agreement that binds your customer to the Nacha Operating Rules is enough. It doesn't need an authorization for each payment, but it must address authorization.
  • Clear, legible terms: the amount, frequency, how to revoke, and your business name.
  • Who signed: the full legal entity name for a business, or the consumer's full name and account information.
  • Signature evidence: an image of the wet signature, an e-signature certificate, or a similar audit trail.

For a dispute

When a bank asks for proof against a dispute, send the authorization record above plus the payment's transaction history, its IP and device signals, and any correspondence about revoking the authorization.

Send your POA

  1. Gather the records for the payment Straddle named, using the lists above.
  2. Save them as a PDF, PNG, JPG or JPEG, DOC, or DOCX file of up to 10 MB.
  3. Upload the file to the payment through the API, as Provide proof of authorization describes. If you aren't integrated with the API, send the file by email to compliance@straddle.com, and Straddle attaches it to the payment for you.

What happens next

  • A held payment: Straddle releases it in the next ACH window after it receives compliant POA. If Straddle receives the POA by 8:00 PM ET on the same business day, your funding isn't delayed. If you don't send POA, or it isn't compliant, the payment is voided. See ACH cut-off times and funding targets for the windows.
  • A file uploaded through the API: the charge or payout lists it under documents, and the charge and payout webhooks carry the same list, so you can confirm Straddle has it without polling.

Questions about a POA request go to compliance@straddle.com.