... | @@ -38,8 +38,8 @@ inLeague recommends the use of holdbacks whenever possible and as we migrate our |
... | @@ -38,8 +38,8 @@ inLeague recommends the use of holdbacks whenever possible and as we migrate our |
|
Beginning in 2025, leagues may now accept payments via ACH Direct Debit. These payments have greatly reduced fees, but work slightly differently from credit card transactions. The biggest difference is that credit card transactions are approved or declined instantly: ACH Direct Debit has **variable settlement timing**, described in detail in the [Stripe Documentation. ](https://docs.stripe.com/payments/ach-direct-debit)Typically, funds are debited from the customer's account one business day after the transaction is processed, and then settle in your league's Stripe account 4 business days after the transaction is processed. The exact timing depends on the customer's bank and may be faster, but is unlikely to be slower. Other significant differences:
|
|
Beginning in 2025, leagues may now accept payments via ACH Direct Debit. These payments have greatly reduced fees, but work slightly differently from credit card transactions. The biggest difference is that credit card transactions are approved or declined instantly: ACH Direct Debit has **variable settlement timing**, described in detail in the [Stripe Documentation. ](https://docs.stripe.com/payments/ach-direct-debit)Typically, funds are debited from the customer's account one business day after the transaction is processed, and then settle in your league's Stripe account 4 business days after the transaction is processed. The exact timing depends on the customer's bank and may be faster, but is unlikely to be slower. Other significant differences:
|
|
|
|
|
|
* Before a customer can pay via ACH Debit, they must **verify** their bank account when they add it as a payment method to their inLeague account. This only needs to be done once: after an account is verified, it can be used to make any payment through inLeague. There are two types of verification:
|
|
* Before a customer can pay via ACH Debit, they must **verify** their bank account when they add it as a payment method to their inLeague account. This only needs to be done once: after an account is verified, it can be used to make any payment through inLeague. There are two types of verification:
|
|
* **Instant Verification** through which the customer logs into their bank and establishes a direct link between Stripe and their bank (which may only be used by your league). This allows the customer to pay via ACH Debit immediately, but carries a fee of **$1.50**, regardless of whether or not the customer actually pays via direct debit, or even pays at all. **Not all banks support instant verification.**
|
|
* **Instant Verification** through which the customer logs into their bank and establishes a direct link between Stripe and their bank (which may only be used by your league). This allows the customer to pay via ACH Debit immediately, but carries a fee of **$1.50**, regardless of whether or not the customer actually pays via direct debit, or even pays at all. This $1.50 fee is a standalone deduction from your Stripe balance rather than a fee on any one transaction, and so it will not appear in your inLeague transaction ledger. Additionally, **not all banks support instant verification.**
|
|
* **Manual verification** in which the customer enters their account and routing number and Stripe then makes **microdeposits** -- usually two transactions of less than $1. This can take 1-2 days and the customer cannot pay via ACH Debit (and potentially not complete registration or whatever payment they were attempting) until it is complete.
|
|
* **Manual verification** in which the customer enters their account and routing number and Stripe then makes **microdeposits** -- usually two transactions of less than $1. This can take 1-2 days and the customer cannot pay via ACH Debit (and potentially not complete registration or whatever payment they were attempting) until it is complete. Microdeposit / manual verification does not incur a fee.
|
|
* Payments may be **declined** after they are initiated, meaning a registration could be activated based on the presumption of a successful payment, but then canceled if the customer's bank reports insufficient funds or incorrect account details. If a payment fails in this manner, Stripe will assess a fee of **$4.00** to the league (not to the customer).
|
|
* Payments may be **declined** after they are initiated, meaning a registration could be activated based on the presumption of a successful payment, but then canceled if the customer's bank reports insufficient funds or incorrect account details. If a payment fails in this manner, Stripe will assess a fee of **$4.00** to the league (not to the customer).
|
|
* Because payments may be initially accepted (e.g. the account is verified) but declined after one or more business days, this introduces a delay in successful processing for the related inLeague transaction: player registrations, event signups, or invoice payments are not activated until the customer's bank confirms the transaction. When this happens, the 'date of registration' will still be the date the payment was submitted (not when it was confirmed).
|
|
* Because payments may be initially accepted (e.g. the account is verified) but declined after one or more business days, this introduces a delay in successful processing for the related inLeague transaction: player registrations, event signups, or invoice payments are not activated until the customer's bank confirms the transaction. When this happens, the 'date of registration' will still be the date the payment was submitted (not when it was confirmed).
|
|
* ACH Direct Debit is not yet supported for donations, sponsorships, team-level payments, or invoice template payments (aside from registration payments using invoice templates). Support for these mechanisms will be added in 2025.
|
|
* ACH Direct Debit is not yet supported for donations, sponsorships, team-level payments, or invoice template payments (aside from registration payments using invoice templates). Support for these mechanisms will be added in 2025.
|
... | | ... | |