inLeagues with existing Flagship Merchant Services (now Paysafe) accounts should contact their account representative, Edwin Alcantaro: edwin.alcantaro@paysafe.com or 857-588-9459 (Eastern Time) or our backup representative, Allen Hatfield: allen.hatfield@paysafe.com - and submit a short, summary account application. Be sure to include your current Merchant ID number. Paysafe will require 2-3 business days to process the application. Your existing FirstData account (also still through Paysafe) should remain open until you no longer need to issue refunds.
inLeague uses the Accept Customer suite to create user payment profiles securely on Authorize.net servers. These payment profiles are not visible to inLeague administrator accounts and no card data other than the last four digits is ever transmitted to inLeague or AYSO. When an inLeague user makes a payment, all card-related communication happens over a secure, encrypted link between the user's browser and the payment gateway.
Customer and payment profile data are accessible via your league's Authorize.net login under the Customer Information Manager link. Anyone with these credentials can see all transactions, as well as customer names, billing addresses, and the last four digits of the card used.
While it is possible to charge a card, issue a refund, or update a payment plan directly from Authorize.net, doing so will not update the relevant transaction or invoice records on the inLeague side, leaving the records out of sync. Authorize.net does provide some mechanisms to communicate transactions to third party providers like inLeague, and inLeague uses them – but when inLeague records a transaction, it does so with league-specific context and business logic (like the logged-in user, invoice templates, or refund messages) that are not strictly part of a payment gateway transaction. Since this information is missing when a transaction is run directly within Authorize.net, it is difficult for inLeague to interpret a handful of transaction details received out-of-context.
There are some exceptions to this rule, and inLeague Support can investigate further integration with Authorize.net webhooks. If your league needs to be able to run transactions directly in Authorize.net, please contact inLeague Support at support@inleague.io with your use case!
Your merchant services account representative will set up your account for you. inLeague is not a signatory to your account and cannot access it without your permission.
If you use inLeague's recommended provider at Paysafe, see the Ecommerce documentation support page for your account representative's contact information.
You can sign in to manage your Authorize.net account at https://account.authorize.net/
If you have more than one merchant account (e.g. a secondary account for tournaments or travel teams) then you will have separate logins for each account.
While you log in to Authorize.net with a username and password, inLeague uses special API credentials instead of a username/password combination to facilitate transactions. These credentials are generated from the Authorize.net control panel. There are several other initial settings that must be configured on the Authorize.net side.
You will enter three pieces of information from the Authorize.net API Credentials & Keys page into the inLeague Control Panel. These are your API Login ID, your Transaction Key, and your Signature Key.
Please note that the Transaction Key and Signature Key are only displayed when they are generated and that it is not possible to view them on Authorize.net after that: you can only invalidate the old ones and generate new ones. You can find your Login ID and generate your Transaction and Signature Keys from the Account menu under the API Credentials & Keys page:
These are generated in two steps: the Login ID and Transaction Key will appear together, and only after they are created can you return to the API page and generate a Signature Key. You may disregard the option to disable the 'old' key. Please Note: Authorize.net is likely to include an extra space at the beginning of the Signature Key. When copying it, please be sure not to include this extra space.
The easiest way to get these values into inLeague is to copy and paste them. Log in to your inLeague instance and navigate to Utilities → Control Panel and select the Payment Gateways tab, followed by the Add a new Gateway option. Enter any descriptive name you like for Account Name, and then paste in the values for Login ID, Transaction Key, and Signature Key. Be sure that Live Account is set to Yes (the default).
Your account is now active within inLeague, but a few other settings are needed:
On your Authorize.net control panel, navigate to Tools → Recurring Billing and look for the Automatic Retry setting. Enable this setting. Without Automatic Retry, recurring billing (payment plans) will not automatically collect missed payments if a user's credit card fails and they update their payment plan with a new one. After enabling this setting, the Recurring Billing page on Authorize.net should resemble this one:
From the same Tools menu on Authorize.net, select Fraud Detection Suite on the left navigation, and then Enhanced AVS Handling Filter. Under the setting Address and Zip Code Responses, you may configure whatever level of address verification you prefer. Please note that inLeague does not support use of Authorize and Hold for Review – transactions must be allowed or declined at the time they are made and inLeague does not make use of "authorize now, capture later."
You will want to do the same thing under the Hourly Velocity Filter, Suspicious Transaction Filter, and Transaction IP Velocity Filter – we recommend disabling these completely, but if you wish to keep any of them, it is essential that you change the response behavior from Authorize and Hold For Review to Decline.
inLeague sends email confirmations for all transactions and refunds, and these emails come "from" your league. inLeague recommends disabling automated email transaction receipts from Authorize.net, both because these receipts duplicate the inLeague receipts and because they do not have any information on the context of the transaction.
To disable Authorize.net email receipts, navigate to the Account menu and select Email Receipt under Transaction Response Settings. Un-check the box for 'Email transaction receipt to customer' so that your Email Receipts page resembles this one:
There are numerous other settings on the Authorize.net control panel. Many of them do not apply to the Accept Customer payment suite that inLeague uses. For questions about Authorize.net payment gateway settings, you may contact either your Merchant Services account representative, or inLeague Support at support@inleague.io.
Team payments and event payments are made using the merchant account configured in Competition Setup or the event details page, respectively. Each competition and each event may use any merchant account available.
Registration, donations, and sponsorships all use the system default account, which is configured in the Control Panel.