Use this step-by-step guide to connect your Elavon acquiring agreement in Frisbii so you can accept card payments from your customers. Each step includes helpful context to explain what you’re doing and how it affects your setup.
Limitations
You need a live Frisbii Pay account. The agreement doesn’t work in test mode.
You need an active acquiring agreement with Elavon.
Step 1: Go to the configuration area
Start by navigating to the correct section in your Frisbii admin:
Click Configurations in the left-hand menu.
Under Configurations, click on Checkout Management and Payment methods.
Click on Credit card agreement.
This brings you to a page showing all the supported card acquirers in Frisbii.
This is where you manage and set up the agreements that allow you to accept card payments in your checkout.
Step 2: Select Elavon as your card acquirer
From the list of available acquirers, click on Elavon.
You’ll be taken to a new configuration page specifically for setting up your Elavon agreement.
Each acquirer has its own setup process.
Step 3: Choose the processor mode
At the top of the configuration page, choose between:
Recommended (preselected): Uses Frisbii’s standard setup for Elavon.
Custom: Allows manual configuration for special cases.
Unless you have specific technical needs, stick with Recommended.
This determines how your payments are processed. The recommended option is optimized for simplicity and compatibility.
Step 4: Fill in your company and agreement details
Now complete the form with the details provided by Elavon:
Name: An internal label for the agreement (e.g., Elavon 2026-10).
Merchant ID: Your Elavon merchant ID (MID). Elavon sends you this number.
Merchant terminal ID: Enter seven zeros followed by the last digit of your Elavon terminal ID. For example, if your terminal ID is 76831212, enter
00000002. The last digit is usually 1 or 2.Merchant name: Your trading name (DBA name) as registered with Elavon.
Merchant address, city, and country: The address where your company is registered.
Merchant Category Code (MCC): The four-digit Merchant Category Code that Elavon assigned to your business.
Merchant website: The website you registered with Elavon. Remember to include
https://, like:https://my-company-website.com.3D Merchant id: Enter your Elavon merchant ID again.
Amex merchant ID (optional): Only required if you select Amex in the card brands. Elavon sends you these details if you have an American Express agreement.
These details are required to connect Frisbii to your Elavon merchant account so payments can be processed and settled correctly.
Step 5: Select which card brands to accept
In the Cards payment methods section, choose the card types your business supports. You can check them one by one or use the Select all option.
Common card brands to enable include:
Visa
Visa Electron
Mastercard
Maestro
Optional cards: Amex
This controls which cards your checkout will display to customers. Make sure to only select the cards you’re allowed to accept through Elavon.
Step 6: Set up token requestor IDs
Under Token requestor configuration, connect the necessary token IDs:
For Visa and Mastercard, select your Token Requestor ID from the dropdown.
If you haven’t created one yet, click Create Visa token requestor ID or Create Mastercard token requestor ID.
These identifiers enable you to securely process payments through network tokenization. The primary advantage is that Frisbii can automatically update saved cards for you, meaning your customers won’t have to update their card details—helping you reduce involuntary churn.
Step 7: Review optional advanced settings
At the bottom of the page, click Show advanced settings if you need to enter specific parameters or adjust default behavior.
Most users don’t need to touch this section, but it’s there if you’ve been given technical requirements or special instructions.
Step 8: Save and activate your setup
Finally, click the green Create button at the top right.
This saves your configuration and activates your Elavon agreement for use in your Frisbii checkout.
Your integration is now live, and you’re ready to start accepting card payments through Elavon.
✅ Setup complete!
Your Elavon agreement will now appear under your list of credit card agreements. You can return to this section at any time to make updates or enable additional cards.
🔧 Need more control? Explore the advanced settings
If your business setup requires more specific routing, authentication, or branding behavior, you can expand the advanced settings when configuring your Elavon agreement in Frisbii. These options give you the flexibility to adapt your checkout flow based on how and where transactions happen.
These advanced features are optional and best used by teams who understand how payments are routed and handled. If unsure, default settings are a safe starting point.
Click Show advanced settings to reveal the following configurable options.
Currencies
Choose whether this agreement should:
Use all currencies (default)
Or only apply to specific currencies you define
Frisbii uses this setting to determine which acquiring agreement to route a payment through. For example, you can send EUR transactions to Elavon, and DKK to another acquirer.
Payment methods
Select whether this agreement applies to:
All payment methods (default)
Or only selected methods, such as Card, MobilePay, Apple Pay, Google Pay, or Vipps.
This allows you to assign a specific Elavon agreement to just Apple Pay, for instance, while using a different acquirer for regular card transactions.
Strong customer authentication (SCA)
Fine-tune your authentication rules:
Enable or disable 3D Secure
Enable 3D Secure for recurring
Disallow 3D Secure attempted
Require SCA by default
BINs (Bank Identification Numbers)
When you select Set custom settings under Strong customer authentication, the fields Visa BIN, MasterCard BIN and Amex BIN appear. These acquirer BINs identify Elavon as your acquirer during 3D Secure authentication, so the card issuer can process the authentication correctly. Frisbii pre-fills the fields with the standard values that Elavon uses for all merchants, so you don’t need to enter anything.
Don’t change these values unless Elavon or Frisbii support asks you to. A wrong BIN makes 3D Secure fail, and your customers can’t complete their card payments.
Payout
You have the option to enable Payout functionality, which allows you to send funds directly to saved cards using Visa Direct and Mastercard Send.
This feature supports use cases such as:
Marketplaces
Customer refunds
Vendor disbursements
In-app wallet withdrawals
Payouts are initiated from within Frisbii and rely on card tokens previously stored during transactions.
To use this feature:
It must be enabled by Elavon on your merchant account
Special pricing applies from both Frisbii and Elavon
You must store customer cards in Frisbii to issue payouts
Enable the toggle “Enable payout” only if you’ve received confirmation from both Frisbii and Elavon that your setup is approved for outbound card payouts.
CIT COF payments
CIT COF payments (customer-initiated transactions with a card on file) are payments your customer starts themselves with a card they saved earlier, for example a one-click purchase.
By default, Frisbii selects the card agreement for a CIT COF payment based on your currently active agreements. The payment therefore doesn’t necessarily go through the agreement the card was saved on.
Turn on Use saved card agreement for CIT COF payments if CIT COF payments should use the agreement the card was saved on instead.
You only need this setting if you have several card agreements and more than one token requestor configuration. In this setup, the agreement Frisbii selects can belong to a different token requestor than the one the card was tokenized with, and the payment can fail. If you have only one card agreement or one token requestor configuration, leave the toggle off.
Also leave the toggle off if CIT COF payments should follow your current routing, for example when you switched acquirers and want saved cards to be charged through the new agreement.