RVM Responder
Overview
At present, EPC VoP is the only supported scheme using FPAD as an RVM (Routing and Verification Mechanism) as defined in the EPC VoP Rulebook allowing VoP requests to be processed to any PSPs and RVMs within the EPC Scheme.
A high-level diagram showing where the RVM fits within the end-to-end solution can be found here
How It Works
The RVM Responder feature works as follows:
-
The client sends a payee verification request.
-
The service selects the appropriate scheme for each request. Currently, this selection is fixed and always defaults to FPAD.
-
The request is sent to the scheme for payee verification.
-
The response is received and returned to the client.
Integration with the RVM Responder is handled through the Connector Framework, using an HTTP connector. More information on the HTTP connector is available here.
Configuration
The following configuration options are available for connecting to the FPAD RVM Responder:
Property Grouping: ipf.verification-of-payee.requester.responder.fpad.http.client
| Key | Description | Default Value |
|---|---|---|
ipf.verification-of-payee.requester.responder.fpad.http.client.endpoint-url |
URL for the RVM Service |
|
ipf.verification-of-payee.requester.responder.fpad.http.client.host |
Host name for the RVM Service |
|
ipf.verification-of-payee.requester.responder.fpad.http.client.port |
Host port for the RVM Service |
|
Error Handling
Startup Errors
RVM Responder performs startup validations and adopts a fail-fast strategy halting application startup if the configuration property ipf.verification-of-payee.requester.schemes[].rvm has a value other than FPAD.
Runtime Errors
The following errors may occur at runtime. When an error occurs, the service responds with the corresponding HTTP error code, as outlined in the table below.
| Error | HTTP Return Code |
|---|---|
When a request is rejected by the RVM service. This can happen if the request is malformed or contains invalid data.
Error message: |
400 |
When there’s an unexpected error from the RVM service. This can happen if the service returns a 5xx HTTP status code.
Error message: |
503 |
When the RVM service is unavailable. This can happen if there are network issues or if the service is down.
Error message: |
503 |