KIDUART school ERP
Fee paymentsLive

Stripe with KIDUART

Stripe suits schools that collect from international families or already run Stripe for other billing. The flow is identical to Razorpay: the parent pays from the portal, Stripe confirms through a signed webhook, and KIDUART writes the payment against the student's fee record and issues the receipt.

Payment IntentsCardsSigned webhooksRefunds

What you get

  • Card and supported local payment methods for international families
  • Signed webhook confirmation before a payment is recorded
  • Automatic receipt against the student's fee record
  • Full and partial refunds reflected in the fee ledger
  • One dues list regardless of which gateway a parent used

The connection, hop by hop

How Stripe actually works here

No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.

  1. Dues shown to the parent

    The parent portal lists the same outstanding heads the office sees, in the currency your fee structure is configured in.

  2. Payment intent created

    KIDUART creates a Stripe payment intent using your school's own secret key, stored encrypted against your school.

  3. Webhook signature checked

    Stripe's payment_intent and charge events are verified against your signing secret, so only genuine confirmations are accepted.

  4. Receipt and ledger written

    The confirmed payment posts to the student's fee record, and any refund raised later is recorded against the same entry.

Keys, data and the bill

Who holds the credentials

Your Stripe secret and webhook signing secret, encrypted per school. Publishable keys are the only values exposed to the browser.

Where the data sits

KIDUART stores the payment intent reference, amount and status. Card data stays with Stripe.

Who gets billed

Stripe's processing fee is charged on your Stripe account, and payouts land in your school's bank account.

Where it lands in the product

The modules this integration writes into

An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.

Fees & Finance

Fee Collection

Linked workflows in the product

Open Fee Collection

Fees & Finance

Finance Reports

Linked workflows in the product

Open Finance Reports

Parents

Parent Portal

Linked workflows in the product

Open Parent Portal

Setup, step by step

Connecting Stripe

  1. Choose Stripe in the finance settings of your school panel

  2. Add your Stripe publishable and secret keys

  3. Register the KIDUART webhook endpoint in your Stripe dashboard

  4. Verify a test payment appears on the student's fee record

  5. Turn on online payment for the classes you want

What you need on your side

  • An active Stripe account for the school or trust
  • Fee structures configured in KIDUART
  • Finance or school admin access to enter credentials
Scope this on a call

Questions schools ask

Stripe, answered plainly

Can we run Razorpay and Stripe together?

Most schools pick one primary gateway. If you genuinely need both for example domestic fees on Razorpay and international payments on Stripe raise it during the demo so we can configure it correctly.

Are refunds handled in KIDUART?

Refunds are recorded in the fee module so your ledger reflects them, including partial refunds, and the gateway-side refund is initiated from your Stripe dashboard.

Live demo

See Stripe in a live demo

We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product