Pymble — Integrations

Integration Overview

#	External System	Direction	Type	Status
INT-001	Data warehouse (Pymble internal)	Inbound	File (Excel export)	Active
INT-002	My Pymble parent portal	Bidirectional	Custom URL + JWT SSO	Active
INT-003	eway (credit card)	Outbound	API	Active
INT-004	Bank (direct debit / ABA)	Outbound	File (ABA)	Active
INT-005	Edstart	Outbound	Edstart platform	Active
INT-006	B Pay	Outbound	Reference number	Active

INT-001: Data Warehouse (Billing Instructions Source)

Purpose

Provides student and billing data used to build billing instructions in Excel, which are then imported into the Family Billing Profile custom record in NetSuite.

Technical Details

• Protocol: File-based (Excel export from data warehouse)
• Direction: Data warehouse → Excel → NetSuite (Family Billing Profile)
• Frequency: Per billing cycle
• Data: Student records, year levels, student type flags (scholarship, indigenous, etc.), billing amounts

Flow

1. Export student data from Pymble's data warehouse
2. Build billing instructions in Excel
3. Import Excel file into the Family Billing Profile custom record in NetSuite
4. Verify via review suitelet before execution

INT-002: My Pymble Parent Portal

Purpose

The My Pymble portal is the primary parent-facing interface. It displays billing and payment information. When a parent clicks "Pay Now," they are redirected to the Feoda payment suitelet via a unique URL with SSO authentication.

Technical Details

• Protocol: Custom URL generation + JWT SSO
• Direction: Feoda → My Pymble (debtor code + billing order ID); My Pymble → Feoda (JWT token on redirect)
• Built By: URL generation / authentication — Sarah Shalfoun (Head of Technology)
• Authentication: SSO via JWT token — My Pymble's portal authenticates the parent and passes a JWT to the Feoda suitelet
• Data sent to portal: Debtor code + transaction ID (billing order internal ID)
• Data received from portal: JWT token for authentication

Flow

1. Feoda sends debtor code and billing order ID to My Pymble
2. Portal displays billing summary to parent
3. Parent clicks "Pay Now"
4. My Pymble redirects parent to Feoda payment suitelet URL with JWT token
5. Feoda suitelet validates JWT and displays billing/payment screens
6. Parent completes payment setup → RPS created in NetSuite
7. Feoda sends invoice back to portal for parent visibility (in progress)

Post-Payment

Feoda is working on sending completed invoices back to the My Pymble portal so parents can view payment confirmation and history within the portal.

INT-003: eway (Credit Card Processing)

Purpose

Processes credit card payments from parents as part of the daily RPS run.

Technical Details

• Protocol: API (eway payment gateway)
• Direction: NetSuite → eway
• Trigger: Daily scheduled script, per RPS processing date
• Response: Authorization code — 00 = approved; other codes = declined

Flow

See RPS Payment Processing for full details.

INT-004: Bank — Direct Debit (ABA File)

Purpose

Processes direct debit and bank payments from parents via ABA file upload to the school's bank portal.

Technical Details

• Protocol: File-based (ABA format)
• Direction: NetSuite → ABA file → Bank portal
• Trigger: Daily scheduled script, per RPS processing date

See RPS Payment Processing for full details.

INT-005: Edstart

Purpose

Allows parents to pay fees via the Edstart third-party education fee payment platform.

Technical Details

• Direction: Parent-initiated via Edstart platform
• Details: To be documented.

INT-006: B Pay

Purpose

Allows parents to pay via B Pay using a reference number through their bank.

Technical Details

• Direction: Parent-initiated via their bank's B Pay facility
• Reference: B Pay biller code and reference number generated per family/invoice
• Details: To be documented.

Authentication Summary

Method	Used For
SSO via JWT token	Parent access to payment suitelet (via My Pymble portal)
Unique URL	Each family receives a unique URL generated from debtor code + billing order internal ID