Skip to main content

Deregistration

See also API reference for NAD

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

Sample Use Cases

Sample Participant Proxy Deregistration

Proxy Deregistration Conditions

Proxy ExistsExists in the same ParticipantSame AccountProxy StatusAction By RPPAction by Participant
No---Scenario is not applicable-
YesYes-SUSPENDED (by Customer)Deregister ProxyDisplay Deregistration Accepted
YesYes-SUSPENDED (by Participant)Scenario is not applicable. Record can only be viewed-
YesYes-ACTIVEDeregister ProxyDisplay Deregistration Accepted
YesNo-INACTIVEScenario is not applicable-
YesNo-SUSPENDED (by Customer)Scenario is not applicable. Record can only be viewed-
YesNo-SUSPENDED (by Participant)Scenario is not applicable. Record can only be viewed-
YesNo-ACTIVEScenario is not applicable. Record can only be viewed-

Successful End-to-End Proxy Deregistration Flow

StepSenderReceiverProcesses
1CustomerOFICustomer logs into Online Banking or Mobile Banking app and initiates a Proxy Deregistration via corresponding menu/link
2OFIRFIOFI performs the following:
  • Authorize and validate the Proxy menu request
  • Any other validations
If all validations are successful:
  • Send Enquiry by Secondary Id message request
3RPPOFIRPP performs the following:If any of the validations are not successful:
  • Send a NEGATIVE/REJECT response
If all validations are successful:
  • Send all registered proxies along with related account information
4OFICustomerOFI performs the following:If all validations are successful:
  • If SUCCESSFUL response is received:
    • Display a successful message to the Customer
  • If UNSUCCESSFUL response ** received:
    • Display an error message to the Customer
Notes:
  • OFI will not be able to modify proxy under Suspended status. This will only be displayed for Customer to view
  • OFI will not be able to modify proxy belonging to another Participant. This will only be displayed for Customer to view
5CustomerOFICustomer performs the following:
  • Review the information
  • Select the proxy to be updated
  • Confirm the proxy to be updated
6OFIRPPOFI performs the following:
  • Authorize and validate the Proxy Deregistration request
  • Any other validations
If all validations are successful:
  • Send Proxy Deregistration message request
7RPPOFIRPP performs the following:If any of the validations are not successful:
  • Send a NEGATIVE/REJECT response
If all validations are successful:
  • Deregister the proxy and account from NAD
  • Set the status to Inactive
  • Send Proxy Deregistration message response
8OFICustomerOFI performs the following:If all validations are successful:
  • If SUCCESSFUL response is received:
    • Display a successful message to the Customer
  • If UNSUCCESSFUL response is received:
    • Display an error message to the Customer

Notes:

  • The exception scenarios will be handled similarly to Account Enquiry flows

Exception Conditions

Rejected by RPP

Below are some of the conditions that the request may be rejected

NoConditionDescriptionAction
1Message Validation ErrorAn invalid message was sent to RPP. Some of the possible causes are:
  • Unknown inbound message is received
  • Message signature could not be verified
  • Failed in message parsing
  • Mandatory field validation has failed
RPP will not send the request to RFI. A REJECT response will be returned to OFI Notes: A copy of the request message in FULL will be returned in the REJECT response in <AddtlData> field. This can be used by the sender to investigate the issue with the message
2Proxy Validation ErrorRPP performs the following business validations:
  • Customer has at least one registered proxy
  • Proxy is registered in NAD
  • Proxy is active
A NEGATIVE response will be sent to the OFI

Timeout

Below are some of the conditions that a timeout could occur

NoConditionDescriptionAction
1RPP failed to receive any incoming request from OFIRequest was sent by OFI but RPP failed to receive the requestOFI will display timeout error message to the Customer
2OFI failed to receive or process response from RPPRPP has responded to the OFI but OFI failed to receive the responseOFI will display timeout error message to the Customer
Notes:
It is recommended to perform an enquiry to check on the status of previous request

Message Schema

Below illustrates the message schema to be used for each transaction leg. For actual schema and message version, please refer to the API specifications instead

NoConditionScenarioSenderReceiverMessage Schema

Out: From Sender
In: To Receiver
1Proxy Deregistration Accepted-OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
-RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
-OFIRPPOut: prxy.001.001.01
In: prxy.001.001.01
-RPPOFIOut: prxy.002.001.01
In: prxy.002.001.01
2Message Validation Failure 1Request from OFI:
  • Signature could not be verified
  • Message parsing failed
  • Mandatory fields level validation failed
  • Unknown inbound message
OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: admi.002.001.01
In: admi.002.001.01
OFIRPPOut: NA
In: NA
RPPOFIOut: NA
In: NA
3Message Validation Failure 2Request from OFI:
  • Signature could not be verified
  • Message parsing failed
  • Mandatory fields level validation failed
  • Unknown inbound message
OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: prxy.001.001.01
In: prxy.001.001.01
RPPOFIOut: admi.002.001.01
In: admi.002.001.01
4Message Validation Failure 3Enquiry response from RPP:
  • Signature could not be verified
OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: NA
In: NA
RPPOFIOut: NA
In: NA
5Message Validation Failure 4Modification response from RPP:
  • Signature could not be verified
OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: prxy.001.001.01
In: prxy.001.001.01
RPPOFIOut: pxy.002.001.01
In: prxy.002.001.01
6Proxy Validation Failure 1Proxy validation includes:
  • Customer has at least one registered proxy
  • Proxy is registered in NAD
  • Proxy is active
RPP returns a negative response due to duplicate proxy
OFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: prxy.001.001.01
In: prxy.001.001.01
RPPOFIOut: pxy.002.001.01
In: prxy.002.001.01
7Timeout 1RPP did not receive requestOFIRPPOut: prxy.005.001.01
In: NA
RPPOFIOut: NA
In: NA
OFIRPPOut: NA
In: NA
RPPOFIOut: NA
In: NA
8Timeout 2RPP did not receive requestOFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: prxy.001.001.01
In: NA
RPPOFIOut: NA
In: NA
9Timeout 3OFI did not receive responseOFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: NA
OFIRPPOut: NA
In: NA
RPPOFIOut: NA
In: NA
10Timeout 4OFI did not receive responseOFIRPPOut: prxy.005.001.01
In: prxy.005.001.01
RPPOFIOut: prxy.006.001.01
In: prxy.006.001.01
OFIRPPOut: prxy.001.001.01
In: prxy.001.001.01
RPPOFIOut: prxy.002.001.01
In: NA

See also