Skip to content

DOC-1151/VOP-000: Single-page guide #344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 39 commits into
base: main
Choose a base branch
from

Conversation

max-koro
Copy link
Contributor

No description provided.

Copy link

linear bot commented Jul 11, 2025

Copy link

netlify bot commented Jul 11, 2025

Deploy Preview for incomparable-tiramisu-91a96a ready!

Name Link
🔨 Latest commit 1978b83
🔍 Latest deploy log https://app.netlify.com/projects/incomparable-tiramisu-91a96a/deploys/687ca84ab46b190008f3434d
😎 Deploy Preview https://deploy-preview-344--incomparable-tiramisu-91a96a.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@max-koro max-koro force-pushed the DOC-1151/VoP-000__single-page-guide branch from 9114b34 to 71b7455 Compare July 15, 2025 11:44
:::tip Why verification tokens matter
- **Regulatory compliance**: Demonstrates VoP verification was performed
- **Time-limited**: Check `expiresAt` timestamp to ensure validity
- **Single-use security**: Each token works only once, preventing replay attacks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are "replay attacks"?

Copy link
Contributor Author

@max-koro max-koro Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're attacks where malicious actors intercept & reuse data to trick a system into accepting it as legitimate. It's not essential. If you want me to remove it, lmk 😄

Copy link
Contributor

@racene-swan racene-swan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey! Good job on this - generally good structure and detail. Small formatting issues around sentence case, full stops on bullets, and consistency around the wording.

@@ -4,6 +4,10 @@ title: Initiate a credit transfer

# Initiate a credit transfer

:::warning VoP Integration Required
Starting October 9, 2025, Swan automatically includes [Verification of Payee (VoP)](verification-of-payee) in all SEPA Credit Transfers per the European Union (EU) Instant Payments Regulation. Consider integrating the [`verifySepaBeneficiary` mutation](verification-of-payee#guide-verify) for optimal user experience.
Copy link
Contributor Author

@max-koro max-koro Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re: regulations, they're linked in the VoP article at /payments/credit-transfers/sepa/verification-of-payee. The goal of this callout is to bring people over to the main VoP article mentioned above, where the EU link is. lmk if you want it here as well 😃

re: "per", I feel it's the proper wording for regulatory stuff. It conveys the authoritative nature of the requirement, is shorter and more direct. It's especially appropriate for describing mandatory compliance requirements. lmk if we have to spar on this hill ⚔️

@@ -7,6 +7,10 @@ title: Verify a beneficiary
Verify a beneficiary with the API.
[Verifying beneficiaries](./index.mdx#beneficiary-verification) reduces the risk of errors and potential fraud.

:::danger Migration required
The `beneficiaryVerification` query will be deprecated on October 9, 2025. [Migrate to Verification of Payee (VoP)](verification-of-payee#migration) before the compliance deadline.
Copy link
Contributor Author

@max-koro max-koro Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

links to pages also need to be sentence case.

Which link are you referring to? The one below follows Coley's currently implemented standard (that I agree with) of capitalizing consecrated names. E.g.
image

Also Theo wants all VoP acronyms to be written with the exact capitalization VoP so I figured the full term would follow the same standard


# Verification of Payee

Validate beneficiary details before sending SEPA Credit Transfers to reduce fraud and payment errors.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edited to "Validate" if that works for you

@max-koro max-koro marked this pull request as ready for review July 16, 2025 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants