Your own sender header
Messages carry a header registered to your organisation. Nobody else sends under it.
Exclusively for JPRAXC clients
Available on request
SMS
Transactional messaging for the ERP you already run — one-time codes, fee receipts and attendance notices — sent under your own registered sender header, with a balance and a rate you can see before you spend them.
Your own sender header · Registered templates · OTP, transactional and service · Wallet and rate card · Delivery reporting
01 / What you get
Messaging your accounts department can reconcile.
SMS is sold only to organisations already running a JPRAXC product, so it arrives knowing your organisation and connects to the ERP you already use.
Registered templates
Message templates are registered and approved before they can be used, and versioned when they change.
One-time codes
Sign-in codes and confirmations, sent as a transactional category rather than mixed with notices.
Fee receipts and notices
Receipts, dues and attendance messages raised by the ERP itself, without anybody re-typing them.
Wallet and rate card
A balance you top up, a rate card you can read, and a spending cap you set.
Delivery reporting
Delivered, failed, expired or unresolved — per message, with the supplier's own reference kept beside it.
Send API
A signed API so any JPRAXC product, and your own systems, can send through the same account.
Limits you control
Daily and monthly ceilings, permitted categories and destinations, set on your licence.
Accounted for
Every message keeps the rate version that priced it, so a rate change never rewrites an old charge.
Message length and cost preview
The send preview measures message encoding and segment count, including Unicode text, and calculates the estimated charge before a batch is submitted.
Duplicate-send protection
A repeated submission with the same request key returns its recorded result, helping prevent a connection retry from sending the same SMS twice.
Recipient and content checks
Mobile numbers and required template values are checked before submission. Invalid recipients, missing details and suppressed numbers are identified during preparation.
02 / How it works
Registered first, then sending.
Apply with your licence
Submit the request with your existing JPRAXC licence reference. SMS is exclusive to current clients.
Register the sender
Your sender header and message templates are registered and approved before anything can be sent under them.
Top up the wallet
Buy a pack. The invoice is raised by JPRAXC Sales and the balance is credited once the payment is confirmed.
Send from the ERP
Your ERP sends through the same account, and every message is reported and reconciled against the balance.
03 / What you receive
A messaging account, not an allowance somebody else controls.
The header is yours, the templates are yours, and the balance is yours to see, spend and account for.
Service outcomes
- Messages sent under your own name, not a shared one
- A balance and a rate you can see before you spend it
- Every message accounted for, delivered or not
- A send API shared by every JPRAXC product you run
- One accountable team for delivery, billing and support
Prepare your setup
Make the sender and the purpose clear.
- Confirm your sender identity
Prepare the organisation details and preferred sender header for registration review.
- Prepare message examples
List the OTPs, reminders or notices you plan to send so the required templates can be agreed.
Already a JPRAXC client?
