Please see the Fall 2020 Payment System Update for details on the transition from FirstData to Authorize.net
inLeague's current recommendation for Merchant Services is Paysafe:
Backup contact: Allen Hatfield, 617-337-3995 - email@example.com
General Sales/Support: 877-884-7477
The inLeague system is designed to broker transactions between leagues and participants (parents and volunteers). This means that we package up all the relevant data for a transaction and send it to your credit card processor, and then record the response. We do not charge a fee for this service; it is part of your regular subscription to our software.
inLeague does not ever store credit card or billing data beyond the absolute minimum required to facilitate transactions between your league and your merchant account.
inLeague does not have a relationship with any merchant services provider and receives no incentives for steering leagues to one provider over another. Given the importance of processing credit cards to every organization that collects fees, we have an interest in a smooth and successful business relationship between our constituent leagues and their merchant services provider. To that end, we periodically act as a consensus-gatherer and representative on our leagues' behalf so that we might leverage the buying power of all of our customers. This is a service we provide as a courtesy; inLeague does not process credit cards, collect fees for processing credit cards, or hold any capacity beyond advice with respect to your league's merchant services account.
There are dozens (if not hundreds) of companies providing merchant services on the Internet. It makes no difference to inLeague which merchant service provider you use; however, they must support Authorize.net as a payment gateway. Please note that support for Firstdata merchant accounts is ending on December 31, 2019.
There are three advantages to using the same merchant services provider as other inLeague regions:
The rates depend on your merchant services provider, the type of agreement your league has with that provider, and the type of card being processed.
Most merchant providers will offer two types of pricing structures. Please note that the following examples are meant only to illustrate concepts; please consult your merchant services representative for an explanation appropriate to your service.
(May 2020 Update): Please note that Authorize.net has temporarily suspended the Expanded Credit Capability program due to increased fraud stemming from the pandemic. If your account currently has ECC capability, you should expect that it will be suspended. If it does not, you will not be able to receive it until further notice. We are working with Paysafe and Authorize.net to find a new solution, but at this time none is forthcoming and the expectation should be that any refund outside of 120 days must be done via paper check.
When a transaction is first submitted, it goes into an "unsettled" batch. While e-commerce transactions are approved or rejected right away, approved transactions only "settle" once a day. The exact time that they settle is determined by your merchant services provider.
Prior to a transaction settling, it may be voided, and no transaction fees should be incurred. After it has settled, without special arrangements, a transaction may be refunded within 120 days. This is a very common restriction in the credit card industry as the payment processors do not want to keep card numbers on file for longer than that. This restriction is not put in place or enforced by inLeague. The only way around it (if Authorize.net is your payment gateway) was to apply for Expanded Credit Capabilities ("ECC") which allow arbitrary (or "unlinked") refunds to be issued against any card. inLeague will still constrain refunds such that they can only be issued against existing transactions.
Almost all refunds are "linked" to the original transaction and can only be applied to the card used for that transaction. If a card expires and is re-issued with a new expiration date, typically this will not prevent refund processing; the account number is the same and the payment gateway considers it the same card; expiration dates can be validated for payments but they are not validated for refunds.
If a card has been canceled or re-issued due to fraud such that the card number has changed, then the original account is no longer active and refunds cannot be issued through the normal mechanism. The only way to issue a refund to a new card is to use the ECC process described above, but also to issue the refund directly through the payment gateway. inLeague will not allow you to enter a new card number for an "unlinked" refund, but the payment gateway will; this is a security consideration since numerous people in a league may have access to issue refunds from inLeague, while only one or two will have a login to the payment gateway. Refunds issued in this manner will not "show" on inLeague, so we recommend entering these as check refunds so that the amount is recorded on the inLeague side as well as in the payment gateway.
Yes. inLeague has the following mechanisms to collect funds:
Unless otherwise specified, all payments will be submitted by the merchant account configured in your inLeague control panel as the system default. Team-level payments, also called tournament payments, may be configured to use separate merchant accounts in the Competition Setup function for each competition -- in other words, you can have funds submitted for teams in your travel program processed separately from funds submitted for teams in your core program.
Similarly, individual events may be configured to use any available merchant account on the 'new event' or 'edit event' pages.
To segregate donations or sponsorships into separate accounts, please contact inLeague Support.