Stripe

Stripe takes card payments, and iDEAL payments in euros, for application fees, registration payments and payment plan fees. The payer pays in a Stripe form embedded in Full Fabric; Stripe then tells Full Fabric the result through a webhook, and the fee is marked paid. Stripe is also the only provider whose payments staff can refund from Full Fabric. See Payment providers for what all providers share.

How it works

Connecting Stripe

Go to Settings → Other integrations → Stripe.

The API keys card holds the values from your Stripe dashboard. Click Add keys (or Update keys), fill in the fields and click Save keys.

Field Notes
Publishable key Loads Stripe's payment form for the payer
Secret key Creates payments and refunds. Masked once saved
Signing secret Verifies the webhook events Stripe sends. Masked once saved

The Payment methods card lists Cards, always available, and iDEAL, which you switch on or off; the switch saves straight away. iDEAL is only offered when the fee is in euros.

Click Enable in the page header to offer Stripe. There is no connection test: a wrong key shows up when a payer opens the payment form.

Webhook

Stripe reports every payment result to Full Fabric through a webhook, so the fee is only marked paid once the webhook arrives. In your Stripe dashboard, add a webhook endpoint at your Full Fabric address followed by /h/stripe/events, and send it these events:

Event What Full Fabric does
charge.succeeded Marks the transaction Succeeded and the fee paid
charge.failed Marks the transaction Failed and the fee unpaid
charge.refunded Marks the transaction Refunded

Copy the endpoint's signing secret into Signing secret.

Warning: Without a saved signing secret, Full Fabric accepts webhook events without checking that they come from Stripe.

Test and live mode

There is no test-mode switch in Full Fabric. Payments run in the Stripe mode of the keys you save, so save the keys and signing secret from the same mode.

What payers see

  • Classic application form: pay with Card, and pay with iDEAL for a euro fee when iDEAL is on. The card form opens in the page.
  • New application experience: Stripe's payment form, with a tab per method (card, plus iDEAL for a euro fee when iDEAL is on), and a pay button showing the amount.
  • Payments page in the portal: Pay with Stripe on an unpaid payment plan fee opens Stripe payment details, a card form. After paying, students see Your payment was processed; an external payer's page reloads.

Full Fabric asks Stripe to request 3D Secure on every card payment. iDEAL sends the payer to their bank to authorise the payment, then back to the same page.

On each payment Full Fabric passes Stripe the fee description and the applicant's or student's name and email (the email is also Stripe's receipt email), and attaches the payment to a Stripe customer for that person. The customer is created on their first payment and reused afterwards.

How payment status comes back

The webhook decides the outcome, not the payer's browser:

  • A transaction is recorded in state Created each time the payment form loads. An abandoned form leaves it Created.
  • When Stripe sends charge.succeeded, the transaction becomes Succeeded and the fee is marked paid. A repeated event is ignored.
  • When Stripe sends charge.failed, the transaction becomes Failed and the fee is marked unpaid again.

The new application experience waits up to a minute for the confirmation after Stripe accepts the payment, then tells the applicant to refresh the page in a few minutes.

Refunds

Open the profile's Financials → All transactions. A refund action appears on a Stripe transaction that is Succeeded and was made in the last 30 days, for staff allowed to refund.

  1. Click the refund action. The Refund transaction window opens.
  2. Choose a Reason: Duplicate payment, Fraudulent payment or Requested by customer, and add a Description.
  3. Click Refund transaction. Full Fabric asks Stripe to refund the whole payment.

The transaction shows Waiting for refund, with the description under it, until Stripe sends charge.refunded; it then shows Refunded. If Stripe refuses the refund, the window stays open and nothing changes.

A refunded payment no longer counts towards a payment plan fee, which then owes that amount again. An application fee stays marked paid after a refund.

Common failures

What you see Usual cause Fix
The payer paid, but the fee is unpaid and the transaction stays Created. The new application experience says We are still confirming your payment. Refresh this page in a few minutes to submit your application. The webhook is missing, points at the wrong address, lacks the charge.* events, or its signing secret differs from the saved one Fix the endpoint in Stripe and save its signing secret
We could not load the payment form. with Try again (new application experience), or the card form does not appear on the classic form Stripe refused to start the payment, for example because the secret key is wrong Update the keys
Please try again, or contact support if you continue to have issues. on the classic form Stripe rejected the payment's details; the attempt is recorded as Failed Look the request up in your Stripe dashboard
Payment Processing Failed on the classic form, back from iDEAL The payer did not complete the iDEAL payment The payer tries again
Online payment is not available for this application. Please contact the institution. Stripe is disabled, or no publishable key is saved Save the keys and enable Stripe
A card error under the card form Stripe declined the card The payer uses another card
No iDEAL option The fee is not in euros, iDEAL is off, or the payer is on the portal's payments page, which takes cards only Switch iDEAL on for euro fees
No refund action Not a Stripe payment, not Succeeded, older than 30 days, or no refund permission Refund in your Stripe dashboard

Permissions

The page opens with Global integrations; see Payment providers for what saving it takes. Refunds need core.institutions.profile_transactions_refund, see Permissions.