Deregistration
Deregistration is used to deactivate a proxy from NAD. Once deregistration is successful, the proxy will not be allowed to be used for Pay by Proxy
Participant will allow Customer to deregister Active or Suspended proxy provided that the proxy is suspended by the Customer. For proxy that is suspended by the Participant, Customer will only be able to see the proxy and not allowed to perform any changes on it
In NAD deregistration, Enquiry by Secondary ID request is initiated first to retrieve all the Customer’s registered proxies in NAD. Participant will display the list of proxies for the Customer – proxies where the status is Active, Suspended (by the Customer) and Suspended (by the Participant)
If there is no record to be displayed, Participant will display a message to the Customer Please note that Customer should not be able to deregister a proxy that is registered with another Participant or Suspended by Participant
Successful End-to-End Proxy Deregistration Flow
Step | Sender | Receiver | Processes |
---|---|---|---|
1 | Customer | Issuer (OFI) | Customer logs into Online Banking or Mobile Banking app and initiates a Proxy Deregistration via corresponding menu/link |
2 | Issuer (OFI) | RPP | Issuer (OFI) performs the following:
|
3 | RPP | Issuer (OFI) | RPP performs the following:If any of the validations are not successful:
|
4 | Issuer (OFI) | Customer | OFI performs the following:If all validations are successful:
|
5 | Customer | Issuer (OFI) | Customer performs the following:
|
6 | Issuer (OFI) | RPP | OFI performs the following:
|
7 | RPP | Issuer (OFI) | RPP performs the following:If any of the validations are not successful:
|
8 | Issuer (OFI) | Customer | OFI performs the following:If all validations are successful:
|