Flywire
Flywire takes payments for application fees, registration payments and payment plan fees. The payer pays in Flywire's checkout, and Flywire notifies Full Fabric as the payment progresses, including bank transfers that are booked first and funded days later. An institution can set up several Flywire gateways, each with its own Flywire recipient, and pick a different one per application template or payment plan. See Payment providers for what all providers share.
How it works
Connecting Flywire
Go to Settings → Other integrations → Flywire. With no gateway yet, the page shows No Flywire gateways yet.
- Click Add gateway. The New Flywire gateway window opens.
- Fill in the fields and click Create gateway.
| Field | Required | Notes |
|---|---|---|
| Name | Yes | The gateway's title, and its name in the Gateway pickers |
| Recipient | Yes | The recipient code Flywire gave you for this gateway |
| Shared secret | No | Verifies the payment notifications Flywire sends. Masked once saved |
Each gateway then has its own card, with an Active or Inactive badge, an Enable or Disable button and Edit gateway. Disabling asks for confirmation: the gateway is no longer offered on payment plan templates or application fees. The card also warns when a gateway is disabled, and suggests adding a shared secret when none is saved.
There is no connection test, and gateways cannot be deleted from this page. There is no notification address to set up in Flywire: each checkout tells Flywire where to send its notifications.
Notification security
Full Fabric only accepts notifications from Flywire's IP addresses. Once any of your Flywire gateways has a shared secret, it also rejects notifications that are not signed with the shared secret of one of your gateways. A rejected notification changes nothing.
Test and live mode
There is no test-mode switch. On Full Fabric's production platform, the checkout always runs in Flywire's production environment.
What payers see
- Classic application form and payments page in the portal: a billing details form comes first, asking for first name, last name, email, phone number, address, country, city, state and zip code (the second address line and the state are optional). Submitting it opens Flywire's checkout. On the portal the button reads Pay with Flywire and the form Flywire billing details.
- New application experience: Flywire's checkout appears in the page, with the payer's name and email filled in; Flywire asks for anything else it needs.
After booking the payment, Flywire sends the payer back to the same page.
How payment status comes back
Flywire's notifications decide the outcome. Each one updates the attempt's transaction, which Full Fabric creates on the first notification:
| Flywire status | Transaction | Fee |
|---|---|---|
| Initiated | Initiated | Marked in process: a payment is on its way |
| Guaranteed | Guaranteed, with the amount Flywire reports | Marked paid, or partially paid if Flywire reports less than owed |
| Cancelled | Cancelled | Back to unpaid, unless other payments already count towards it |
| Error | Back to Initiated, unless it already is | Recalculated: unpaid unless other payments already count towards it |
When an application fee is guaranteed, the applicant receives the system email Email for candidates when a payment is received through flywire, which links to the application. Payment plan fees send no email from Flywire.
While a payment is initiated but not yet funded, the application payment page tells the applicant that it is awaiting confirmation and that they will be emailed once it has been received, and offers to pay another way.
Refunds are not available for Flywire payments in Full Fabric.
Common failures
| What you see | Usual cause | Fix |
|---|---|---|
| The payer paid, but the fee did not change | Flywire's notifications were rejected: the shared secret saved here differs from Flywire's | Save the same shared secret on both sides |
| Payments through one gateway stopped updating after a shared secret was added to another | With any shared secret saved, unsigned notifications are rejected for every gateway | Set up a shared secret for each gateway's recipient |
| A fee stays in process for days | A bank transfer was booked but Flywire has not received the funds | None: it is marked paid when Flywire guarantees the payment |
| A fee shows as partially paid | Flywire guaranteed less than the amount owed | Collect the rest |
| Online payment is not available for this application. Please contact the institution. (new application experience) | The template's Flywire gateway is disabled or has no recipient | Enable the gateway and save its recipient |
| A gateway is missing from the Gateway pickers | It is disabled | Enable it |
Permissions
The page opens with Global integrations; listing and saving gateways also needs read access to the institution settings. See Payment providers and Permissions.