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.
array
required
1 to 1,000 cases with unique
ids.string
required
Your label for the case.
string
required
The processor URL the checkout page called.
string
Default
POST.string
one_time (default), save_card, subscription_initial, subscription_renewal.number
Relative checkout traffic. Default 1.
boolean
Default false.
string
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).null
Always null. Endpoint recognition is not a purchase test.