Payment gateway integration directory

Every page is built from data, not written freehand (how pages are verified). Each claim on it (the status, the install route, every capability in its table) carries a link to the document it came from and the date that document was checked. Vendor documentation and changelogs come first. Marketplace listings and plugin repositories come next. Forum threads are used only for gotchas, and only when something stronger backs them up. A capability table says Yes only when a source confirms that capability on that specific integration. When the gateway supports something but nothing confirms the integration exposes it, the table says "Not verified here" instead, and a capability with no source either way is left off rather than guessed.

The gotchas are the part you cannot get from a vendor's feature list: fees a platform charges for using an outside gateway, extensions that changed hands, checkout rewrites that broke older plugins, webhook setups that fail quietly in development. They are drafted from sources and then reviewed by a person before a page is published. Nothing here is generated to fill space: a page that ends with "not supported" still has to earn its place with a sourced reason and somewhere else to look.

The directory is maintained by UAT-Ops, a workbench for integrating with an API and proving the integration works. Where UAT-Ops has completed a sandbox validation, it publishes the redacted evidence of the flow on that gateway's page, and every integration page says whether it was sandbox-tested or checked against documentation only. This directory has no paid placements, and no gateway or platform can pay to change a verdict. If a page links through a referral programme, it will say so on the page itself.

Found something out of date? Every page shows when it was last verified. Corrections go to [email protected].