diff --git a/docs/topics/payments/credit-transfers/sepa/vop/verification-of-payee.mdx b/docs/topics/payments/credit-transfers/sepa/vop/verification-of-payee.mdx
index c0cd5168051..3f7e9402411 100644
--- a/docs/topics/payments/credit-transfers/sepa/vop/verification-of-payee.mdx
+++ b/docs/topics/payments/credit-transfers/sepa/vop/verification-of-payee.mdx
@@ -64,13 +64,15 @@ sequenceDiagram
     participant EU as End-user
     participant P as Partner
     participant S as Swan
+    participant Bene as Beneficiary's bank
 
     EU->>P: Enters beneficiary details
-    P->>S: VoP Triggers
-    S->>S: Generates VoP result
-    S-->>P: Verification results<br/>(Custom integration)
-    P-->>EU: Displays VoP results/warnings<br/>(Custom integration)
-    S-->>EU: Displays VoP results/warnings<br/>(Default integration)
+    P->>S: VoP triggers
+    S->>+Bene: Sends VoP request (IBAN + name)
+    Bene-->>-S: Returns verification result
+    S-->>P: Relays result<br/>(Custom integration)
+    P-->>EU: Displays VoP result/warnings<br/>(Custom integration)
+    S-->>EU: Displays VoP result/warnings<br/>(Default integration)
 
     Note over EU: Reviews the results
 
@@ -107,6 +109,12 @@ Following the [European Payments Council (EPC)'s recommended matching rules](htt
 
 ### VoP results {#vop-results}
 
+:::caution Swan relays results: it doesn't determine them
+VoP results are determined solely by the **beneficiary's bank** (the creditor's PSP). Swan sends the verification request and displays the result exactly as received. Swan has no influence over the outcome and cannot modify or override it.
+
+If a result seems unexpected, the beneficiary's bank made that determination based on their own matching logic.
+:::
+
 The beneficiary's bank can return one of four verification results. **All results must be displayed to the end-user**. Swan will systematically display the VoP result and warning on the SCA consent screen.
 
 <Tabs>