Rapyd

Prev Next

Use this step-by-step guide to connect your Rapyd acquiring agreement in Frisbii so you can accept card payments from your customers.

Limitations

  • You need a live Frisbii Pay account. The agreement doesn’t work in test mode.

  • You need an active acquiring agreement with Rapyd. With Rapyd, this is a tripartite agreement between you, Rapyd, and Frisbii, which must be signed before Rapyd can approve your application.


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 Rapyd as your card acquirer

From the list of available acquirers, click on Rapyd.

You’ll be taken to a new configuration page specifically for setting up your Rapyd agreement.


Step 3: Choose the processor mode

At the top of the configuration page, choose between:

  • Recommended (preselected): Uses Frisbii’s standard setup for Rapyd.

  • 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 Rapyd:

  • Name: An internal label for the agreement (e.g., My Rapyd Agreement).

  • Rapyd agreement id: The ID of your agreement in the Rapyd portal. If you settle in several currencies or to several bank accounts, each agreement has its own ID, and you create one agreement in Frisbii for each.

  • Merchant name, city, and country: Make sure these match your registration with Rapyd.

  • Merchant Category Code (MCC): The four-digit Merchant Category Code that describes your business type.

  • Merchant terminal id: Your Rapyd terminal ID, usually 8 digits. You find it on the Terminals tab in the Rapyd portal.

  • Merchant website: Your official business website. Remember to include https://, like: https://my-company-website.com.

  • Amex merchant ID (optional): Only needed if you’re set up to accept American Express.

These details are required to connect Frisbii to your Rapyd 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 Rapyd.


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 Rapyd agreement for use in your Frisbii checkout.

Your integration is now live, and you’re ready to start accepting card payments through Rapyd.


✅ Setup complete!

Your Rapyd 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 Rapyd 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 Rapyd, and DKK to another acquirer.

Each Rapyd agreement settles in one currency to one bank account. If you need to settle in several currencies or to several bank accounts, you need one Rapyd agreement for each. Agreements that settle only in DKK can’t process transactions in other currencies.


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 Rapyd 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 Rapyd 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 Rapyd uses for all merchants, so you don’t need to enter anything.

Don’t change these values unless Rapyd or Frisbii support asks you to. A wrong BIN makes 3D Secure fail, and your customers can’t complete their card payments.


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 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.


Reference templates

This section allows you to define exactly what identifier Frisbii sends to Rapyd for each transaction. The value you set here will appear in Rapyd’s reporting and settlement files, making it easier to match payments with internal records like invoices or subscriptions.

By default, Frisbii uses the invoice handle (e.g., inv-123456) as the identifier.

You can customize:

  • Order ID template – Controls what Frisbii sends as the primary order reference.

  • Soft description template – Optional. Used for descriptors on cardholder statements, if supported.

Both fields support dynamic tags such as {{invoice_number}}, {{account_name}}, and {{transaction_id}}.

This customization helps streamline reconciliation and accounting by aligning Frisbii transactions with your financial reporting and Rapyd payout files.