Griffin vs Increase ACH

Griffin provides banking-as-a-service infrastructure for companies embedding bank accounts, payments, and other financial products through APIs. It operates its own core banking platform and banking license. Business accounts for fintechs and venture-backed startups can be managed online or by API, while embedded savings and bank accounts support customer funds and client money. Payment features include Faster Payments, instant transfers between Griffin accounts, payment webhooks, and Confirmation of Payee. Verify automates KYC and KYB checks and provides onboarding workflows. The REST API uses JSON and includes a free sandbox without fees or an NDA. Griffin also works with tell.money on open-banking integrations. Griffin Bank is authorised by the Prudential Regulation Authority and regulated by the FCA and PRA. Security documentation cites encryption at rest and in transit, monitored access, and least privilege. Business banking starts at £100 per month; platform packages are £10,000 per month, with onboarding from £15,000 one-off.

Increase ACH is a web and API service for technology companies that originate ACH credits and debits, track returns, and store frequently used payment details. Increase says ACH is same-day by default, submitted at every Federal Reserve window, with payments potentially arriving in less than 24 hours. Next-day ACH origination is priced at $0.50, while same-day origination costs $2. ACH returns cost $5, unauthorized returns cost 15.00 USD, and late return request processing costs 25.00 USD. Unique counterparty account numbers support reconciliation. Incoming transfers can be previewed for one hour before allocation, with allow or disallow lists and other rules or limits. Return codes and standard entry class codes are exposed, returns are automatically correlated, and webhooks report transfer lifecycle events. The dashboard shows payment status, pending submissions, estimated arrival, and returns. Increase also lists PCI DSS Level I and SOC 2 audits, disk-level encryption, application-level AES 256 encryption for certain data, and HTTPS for API requests.