Skip to content
⌘K
InboxAsk a human

What you need for platform due diligence

Updated by Kayla

Before a platform goes live on Straddle, Straddle reviews the policies your customers agree to, how you protect their data, and how your software captures ACH authorization. Use this checklist to have each document and record ready.

Documents

DocumentWhat it covers
Terms of Service, customer-facingPayment processing terms, every fee you charge your customers, refund and cancellation policies, how disputes are resolved, and how to reach your support.
Privacy PolicyThat you share customer data with Straddle to process payments, how customers ask to see, correct or delete their data, who to contact about privacy, and compliance with the state privacy laws that apply to you.
Information security policyWho on your team can access customer data, how it's encrypted, how you respond to incidents, and how you share data with third parties.
Data security policyAccess controls, encryption in transit and at rest, incident response, third-party data sharing, network security controls, and regular security assessments.
Data retention policyHow long you keep customer data and payment records, and how you delete them once that period ends.
Flow of funds diagramHow money moves between your customers, your platform and Straddle.
Proof of your ACH authorization processScreenshots of the authorization steps in your product, a walkthrough, or data logs.

If these policies are part of a master agreement or terms and conditions, provide the full document.

ACH authorization

How you capture authorization depends on how your customers pay. Each payment needs the SEC code that matches how its authorization was given.

Online authorization (WEB), for consumers who authorize in your product. Your authorization page must show:

  • Clear consent language that says you're debiting the customer's bank account.
  • The transaction details: amount, payment timing or frequency, and date.
  • The customer's name and bank account, at least the bank name and last 4 digits.
  • The customer's IP address.
  • How the customer can revoke the authorization, with a phone number or email address.

The customer must also be authenticated, for example by logging in to their account or with a code or digital signature, at the same time as they authorize.

Signed agreements, for business or recurring payments:

  • CCD, business to business: an agreement between the two companies that binds both to the Nacha Operating Rules.
  • PPD, business to consumer: a written, signed or similarly authenticated authorization.
  • Standing authorization, for recurring payments the customer starts: advance authorization for future payments, and a clear description of what the customer does to start each one.

Records to keep

  • Every authorization, so you can reproduce it when asked: the authorization language, the record of authentication, and the date and time of login and consent.
  • A complete record of each payment you process.
  • Both for at least two years after the last payment.

Common gaps

  • Consent language that doesn't clearly authorize ACH debits.
  • The wrong SEC code. Debits from business accounts should use CCD. A business's bank has two banking days to return an unauthorized CCD debit, while a consumer's bank has 60 days for an unauthorized consumer debit.
  • No authentication of the customer when they authorize.
  • Authorizations you can't reproduce when asked for them.
  • Fees your customers can't see in your terms.
  • No mention in your privacy policy that you share data with Straddle.

Every document should be current and match how you actually operate.