Payments-processor migration

The PMS is moving its embedded payments from one processor to another, and every property is a separate legal entity that has to onboard separately: full KYC/KYB verification, decision-maker records, bank details, and signed attestations. The same tedious form, times every entity.

How it works

Each property's verification portal is reached through Mews Commander's onboarding page, which opens a live hosted Adyen session. I drive it with Chrome automation. The agent fills the business fields it is allowed to (legal name, tax ID, address, ownership percentages, owner names and addresses) and navigates the checklist.

• The agent never enters SSNs, dates of birth, bank or routing numbers, or government IDs, and never clicks Submit or Sign.
• I personally sign the PCI and services-agreement attestations in the browser. The agent stays out of the sign screens entirely.

Most properties are fully done. A couple are held up on real-world snags (one on a tax-ID record the processor has to review, two waiting on the vendor to turn the portal on), not on the automation. I do not guess at a legal name or an ID. Where there is ambiguity, it waits for a confirmed answer.

Onboarding a dozen legal entities to a new processor is exactly the repetitive, compliance-heavy grind an operator dreads. The agent absorbs the form-filling. I keep the pen for anything that is an attestation or an identity. That split is what lets one person clear a stack of KYC without cutting a corner.