Checkout authorizations
Assess checkout cases
Label up to 1,000 observed processor requests as recognized, unsupported, or unverified before you build.
POST
Send the processor endpoints your automation observed at your target merchants, without card data or request bodies. Each case comes back labelled, with a weighted share of your traffic the Vault recognizes.
recognized (a known processor request format), unsupported (for example an iframe-bound VGS tokenization or a non-POST), or unverified (a renewal the merchant bills itself, or a format the registry does not know).