Payment Requests

Receiving account

Select the account that will receive the payment.

What is an account?

An account (also called portal) defines who receives the money from payments to Flywire.

You as a client registered a company with Flywire and define at least one account for this company. This account contains settings like the bank account that receives the money from payments and the currency in which Flywire takes payments from your payers.

You can have more than one account, for example one account for testing purposes and one production account. Or you could have multiple accounts because you want to receive money into different bank accounts or currencies.

Payments configuration

Payment Type

Select the Payment Request type. For more info see Payment Request Types.

If you are missing one of the Payment Request types, it might be disabled in the Payment Request settings.

Expiration date (optional)

Expiration dates limit the time a Payment Request or subscription can be paid, for example in cases like event registrations or invoices with late fees. Once expired, no payments can be made. Setting an expiration date is optional.

The expiration date applies to the entire Payment Request (or subscription), preventing any payments after it passes. In contrast, a due date applies to an individual payment within a Payment Request (or subscription), and payments can still be paid after the due date.

Filtering payment methods and currencies

It depends on the Payment Request settings if you have this option.

Help for filtering payment methods

By default, Flywire displays all payment options for a portal. In some cases, you might want to restrict the available payment options, for example if you want to accept only bank transfers for payments over a certain amount or only show card payments a certain time before a booking.

You can use two filters to restrict payment options:

• Restrict to specific types of payments

• Restrict to specific currencies

Payment method type filters Each filter you add means show this option. Each filter you leave out means hide this option. If you don't provide any filters, all payment method types will be displayed in the Commercial Payment Experience. Currency filters The filters restrict payment options based on currencies: Local Show only payment options in the payer's local currency (e.g., only GBP for a payer in the UK). Foreign Show only payment options not in the payers local currency (e.g., everything but GBP options for a payer in the UK). FX Only show payment options that are a different currency to the billing currency (e.g., everything but GBP if your billing currency is GBP). What is the billing currency? The billing currency is the currency in which the recipient of the payment is billing their payer. The billing currency depends on the portal's configuration and is defined when the portal is set up by Flywire. Non-FX Only show payment options that are in the same currency as the billing currency (e.g., only GBP if your billing currency is GBP). If you don't select any of the currency types, no filter is set, which means all available currency options will be displayed to the payer. Be careful with combining those filters. Your payer might end up not being able to pay if you restrict the options too much. As a best practice, use either local/ foreign (when you want the options to depend on the payer's country) or fx / nonFX (when you want the options to depend on your billing currency).

Amount and due date

Enter the amount and due date depending on the Payment Request type you chose:

One time payments	One time Payment Requests contain a one time payment for a specific amount. It is optional to give this payment a due date.
Installments	A Payment Request with multiple installments allows you to collect future payments with variable amounts. You can decide if you want to have due dates for all installments to collect them on specific dates or if the installments have no specific due date.
Subscriptions	Subscription payments allow you to collect future payments with a fixed amount on regular intervals.For subscriptions, you cannot create or edit installments yourself - they are automatically generated by Flywire based on the rules that have been defined for the subscription.
Scheduled charges	A Payment Request with scheduled charges allows you to collect one or more payments with variable amounts on mandatory due dates.

Pre-Authorization Payment

It depends on the Payment Request settings if you have this option.

If enabled, you have the option to create a Pre-Authorization Payments for one time Payment Request

What are Pre-Authorization Payments?

A Pre-Authorization Payment temporary reserves the payment amount on a debit or credit card. The purpose of a pre-authorization is to verify that the cardholder has sufficient credit available to cover a transaction and to temporarily set aside that amount until you capture the funds.

Pre-Authorization Payments are only available for same-currency payments, not for FX payments.

Example for a Pre-Authorization Payment:

A guest checks into a hotel for a three-night stay, and you place a pre-authorization on their credit card for the estimated cost of the stay.

1. Check-In: You pre-authorizes $600 on the guest's credit card ($150 per night plus $150 deposit). This reduces the guest's available credit by $600 but is not yet charged.

2. During the Stay: The guest orders room service for $50.

3. Check-Out: The final bill is $500 ($450 for room charges plus $50 for room service). You capture $500 from the pre-authorization. The remaining $100 from the original hold is returned to the guest's available credit.

Custom Payment Data

Custom fields are fields that are specific to your account (also called portal). Fields are defined when the account is set up by Flywire. Typically, these are fields your own system needs to be able to process and reconcile the payment.

It depends on your settings if a custom field is optional or required.

More info

There are two layers of required fields:

1) Fields that are required due to settings in your Dashboard (see settings for Payment Request)

If a field is set to required in Flywire Dashboard, you must provide it when you create the Payment Request or subscription. Optional fields can be left out.

2) Fields that are required due to settings for the portal (also called account)

If a field is required for the portal, it is required to create the payment.

If a field is not required due to Dashboard settings but is required for the portal, you can decide if you provide it or not when you create the Payment Request or subscription. If you don't provide it, your payer has to fill out the field in the Commercial Payment Experience form, since it is required to create the payment.

How to find out which fields are required for a portal

You can check which fields are required by checking your portal configuration.

Payer info

You can either use a saved contact from the dropdown or you can add a new payer and enter the payer information yourself.

Which payer fields are required for creating a Payment Request depends on your Payment Request settings.

You can save the new payer as a contact by activating the checkbox Save as contact.

Save or process the Payment Request

When you save the Payment Request, no email to the payer will be sent. You can copy the generated link and submit it to the payer yourself.

When you process the Payment Request, you can review the email to your payer and send the request. You have the option to change the email address where to Payment Request is sent to, add more email addresses, and to change the reply-to email address.