Payment providers
Full Fabric takes online payments through four payment providers: Stripe, PayPal, Flywire and Adumo. An administrator connects the institution's account with each provider once. Staff then choose which provider, or gateway, collects each application fee or payment plan, and applicants, students and external payers pay on that provider's checkout. Full Fabric records every attempt as a transaction and marks the fee paid when the provider confirms the payment.
This section covers connecting each provider and what happens to a payment. Fees, payment plans, discounts and external payers are covered in Finance.
| Provider | What staff enter | Page |
|---|---|---|
| Stripe | API keys, signing secret, iDEAL on or off | Stripe |
| PayPal | API credentials, with a connection test | PayPal |
| Flywire | One or more gateways, each with a recipient code and shared secret | Flywire |
| Adumo | Endpoint, merchant and application IDs, secret | Adumo |
Where to find them
Go to Settings → Other integrations. The Payments group lists Stripe, PayPal, Flywire and Adumo, and only appears while the institution has the finance module.
The Stripe, PayPal and Adumo pages share one layout:
- The header shows the provider, an Active or Inactive badge and an Enable or Disable button. Disabling asks for confirmation, warning that applicants and students will no longer be able to pay fees with that provider.
- Saved values are shown read only. Secret values are masked, with a control to reveal them; empty ones show Not set.
- The card's update button opens the fields. Secret fields open empty: leave them empty to keep the saved value. Nothing is written until you save.
Flywire is different: it holds a list of gateways, each with its own name, credentials and Enable or Disable button. See Flywire.
Which payments each provider can take
| Where the payer pays | Stripe | PayPal | Flywire | Adumo |
|---|---|---|---|---|
| Application fee, classic application form | Card, plus iDEAL for euro fees | Yes | Yes | Card |
| Application or registration payment, new application experience | Card, plus iDEAL for euro fees | Application fee only | Yes | No |
| Payment plan fee, payments page in the portal | Card | No | Yes | No |
Registrations always use the new application experience; applications use it when the institution has turned it on.
Warning: The payment plan template's Gateway list offers every enabled provider, PayPal and Adumo included, but neither has a checkout for payment plan fees. Fees on such a plan cannot be paid online. Use Stripe or Flywire for payment plans.
Choosing the provider for a fee
A provider is offered in the gateway pickers only while it is enabled. A disabled Flywire gateway is not offered either.
- Application templates, for the application fee: on the template's Payment tab, pick the Gateway. Until one is picked, the tab warns that the payment page will not appear and applicants can submit without paying. On an institution-wide template whose fee depends on the programme choice, each programme's fee can name its own gateway.
- Payment plan templates, for payment plan fees (registrations included): under Payment settings, choose Process and track payments in Full Fabric as the Payment process, then pick the Gateway. When no gateway at all is enabled, that option is unavailable and shows No payment gateways are set up.
Besides the four providers, the pickers can list External, for payments taken outside Full Fabric. See Finance for the rest of these settings.
What happens to a payment
Every attempt is recorded as a transaction on the applicant's or student's profile, under Financials → All transactions, with a Gateway column naming the provider. How the confirmation reaches Full Fabric differs:
| Provider | How the result comes back | Transaction states |
|---|---|---|
| Stripe | Webhook from Stripe | Created, Succeeded, Failed, Waiting for refund, Refunded |
| PayPal | The payer's return from PayPal | Pending, Succeeded, Failed |
| Flywire | Notifications from Flywire, possibly days later for bank transfers | Initiated, Guaranteed, Cancelled |
| Adumo | The payer's return from Adumo | Succeeded, Failed |
A Stripe transaction is recorded as soon as the payment form loads, and a PayPal one as the payer leaves for PayPal. An abandoned attempt stays Created or Pending: it is not money on its way.
Full Fabric sends Stripe, PayPal and Adumo the fee's amount and currency, and Flywire the amount. It does not restrict currencies, except that iDEAL is only offered for euro payments.
Refunds
Refunds can be issued from Full Fabric for Stripe payments only. See Refunds.
Common failures
| What you see | Usual cause | Fix |
|---|---|---|
| A provider is missing from the Gateway list | It is disabled, or (Flywire) the gateway is disabled | Enable it on its settings page |
| No payment gateways are set up on a payment plan template | No gateway is enabled | Connect and enable at least one provider |
| Payers see no way to pay a plan fee online | The plan's gateway is PayPal or Adumo | Switch the plan to Stripe or Flywire |
| A payer paid but the fee is still unpaid | The provider's confirmation did not reach Full Fabric | See the provider's page: Stripe webhook, Flywire shared secret, PayPal return |
Permissions
The pages under Payments open for staff with Global integrations while the finance module is on; see Permissions. That feature does not save them on its own: the Stripe, PayPal and Adumo details are written to the institution settings, which needs permission to change institution settings, and the Flywire gateways are read and saved with read access to the institution settings (core.institutions.institutions_settings_access).
Refunding a Stripe payment needs core.institutions.profile_transactions_refund.