In this guide we’ll look at how to set up integration with ParentPay using a Third Party API.
Access: The Permissions required to access System Users and Third Party Access Permissions and Logs can be found in the Setup Module from within Config > Setup > Roles and Permissions.
See Also: How to Manage Third Party Supplier’s API Access Permissions
Integrating with ParentPay
In order to integrate ParentPay with Bromcom you will first need to create a new User Account with Third Party Permissions for them.
To do this go to Modules > Setup > System Users.
Select New
In the Personal Details panel, select Create New User and then enter a First Name and Last Name for the user account.
In the User Login Details section, create a Username for the account,. We recommend against using a generic Username that could be easily guessed (for example ParentPay) to help keep your data safe.
Tick The user can log into system, enter a New Password and then re-enter this in Confirm Password. Please ensure the Password is suitably secure and cannot be easily guessed.
Make a note of the Username and Password as ParentPay will need this to access the information in your MIS.
Finally, in the Roles section, select Third Party.
Note: When assigning roles it is important that you only select Third Party as this role has been specifically set up to only allow Third Parties to view the information you select. Selecting other Roles may make sensitive information accessible.
Once you’re happy, click Save.
Next, you’ll need to assign which Third Party permissions to give to ParentPay. To do this, go to Modules > Setup > Third Party Access Permissions and Logs.
Select the Parent Pay account you created from the Third Party Account from the dropdown and select Manage Permissions.
In the pop-up that appears, use the tick boxes on the left to select which Permissions to assign. You can use the search bar in the top right hand corner to look for specific Permissions.
The latest guidance we have from ParentPay indicates that they require the following Permissions, however this is subject to change at any time so please check with them directly to confirm that no further Permissions are required.
| CollectionAssociates | PreadmissionStudents |
| CollectionExecutives | Schools |
| CollectionExecutivesRolesTypes | Staff |
| Collections | StudentContacts |
| EmployeeContacts | StudentEnrolments |
| Nationalities | StudentMealPatterns |
| People | Student Meals |
| PersonAddresses | Students |
| PersonCommunications | SubjectClasses |
| PersonMedicalConditions | Timetable |
| |
Once you’re happy click Save and the process is now Complete.
ParentPay may not see your MIS data immediately, however, the following day you can check in Modules > Setup > Third Party Access Permissions and Logs and if there are no entries in the Third Party Access Logs for the ParentPay account then you may need to contact ParentPay to troubleshoot.
For more information on managing Third Party accounts, please see How to Manage Third Party Supplier’s API Access Permissions.
FAQ’s
Q: Why aren’t future students or pre-admissions pulling into ParentPay?
A: ParentPay only looks at current data. For example they will not pull in any students that start in the future. This is a decision made by ParentPay and is out of Bromcom’s control.