-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API - REGC and PUBA location change #18459
Comments
@doug-lovett I've confirmed fee code information above. |
Same endpoint as STAT: PUBA payload example: REGC payload example: |
Verified in DEV using Postman! MHR 107855 TEST: 107289 |
In addition to the STAT document type, staff can change a location with the PUBA and REGC document types (depending on the reason for the change). Both PUBA and REGC are Swiss army knife registrations where multiple changes can be made (location, owner name and address MH status..). This ticket only covers the PUBA/REGC change of location with an optional note.
Fee codes to be provided when known:
PUBA: MHROT (if clients make a mistake PUBA should be used and a $15.00 fee should be applied)
REGC: CORLC (if staff make a mistake REGC should be used and no charge applied)
Edge Cases: In the current system there are edge cases where even if the client made a mistake no fee is charged. The current fee approach allows staff the option to choose 'No Fee' so for these PUBA scenarios we can request staff choose 'No Fee' and provide guidance in the manual.
This ticket does not cover cancelling a transport permit.
The text was updated successfully, but these errors were encountered: