BIC Enrichment Service
Determine missing BICs to guarantee correct EDS routing
The challenge
When a Verification Of Payee (VOP) request is routed via the EPC Directory Service (EDS), a Bank Identifier Code (BIC) is required to determine where the request should be sent.
In practice, PSPs do not always receive a BIC from their customers. As the BIC is not mandatory for standard SEPA payments, most systems are not designed to supply this information by default in the VOP request.
This leads to operational complexity and increased risk of failed requests when:
- A BIC is required but not provided
- (Manual) enrichment processes are needed
- Multiple systems require configuration
- Not being able to correctly route a VOP requests generates liability issues
The solution
The SurePay BIC Enrichment Service ensures that, when a BIC is required but not present in a VOP request, it is automatically added before the request is routed.
This allows PSPs to submit VOP requests with or without a BIC field. If enrichment is needed, it is handled automatically within the SurePay platform, based on trusted and validated data in line with EPC Rulebook requirements.
Key benefits
-
No structural changes to request format
The BIC field becomes optional when using this service. -
Supports regulatory alignment
Helps ensure requests are properly routed via the EDS under the EPC Rulebook. -
Reduces manual effort
No need to build or maintain separate enrichment logic. -
Logged and auditable
Enrichment activity is recorded and visible in the Match Audit Dashboard.
How it works
BIC Enrichment is applied only when necessary and based on routing logic:
- VOP request routed via EDS and no BIC provided
→ SurePay enriches the BIC before forwarding the request. - VOP request routed via EDS and BIC provided
→ The supplied BIC is used as-is. - VOP request within SurePay ecosystem
→ No enrichment needed; request proceeds without BIC.
All enrichment actions are logged and available to the PSP for audit purposes.
Frequently asked questions
No. Enrichment is only applied when a BIC is required for routing and not provided in the request.
No. The BIC is used internally for routing purposes and is not included in the response payload.
No. It is an add-on service.