Skip to content

Shopify Dude Fix

Shopify Payments App Rejects a Vaulted Card Without CVV? Handle trusted_vault_origin in 2027-01

Payment apps on API 2027-01 can receive trusted_vault_origin. Learn when a missing CVV is acceptable, what the flag does not prove, and how to test safely.

Quick answer: For a Shopify Payments Apps API credit-card payment or verification request, payment_method.data.trusted_vault_origin === true means the card details came from a vault Shopify trusts. Do not reject that request solely because the CVV is absent. Continue fraud checks, 3-D Secure when applicable, and your normal processing rules.
On this page

Why a previously saved card can be rejected

Shopify announced the trusted vault origin signal on October 30, 2026. Some payments integrations assume every credit-card request must contain a CVV, even when card credentials come from a trusted vault. The new optional flag gives a narrow way to distinguish these requests. It does not mean the transaction is fraud-free, nor does it identify the particular vault.

Read the field at the correct location

The Boolean is in payment_method.data, outside the encrypted card details. It is not the same as vault_status or transaction_reason. Shopify sends it only when the extension uses API 2027-01 or later, Shopify has enabled the feature for the payments app, and Shopify has a value available. The current stable version is 2026-10, so use 2027-01 release-candidate environments for testing, not production upgrades before stability.

// Illustration inside your validated payments request handler.
const card = request.payment_method;
const trusted = card?.type === 'credit_card' &&
  card?.data?.trusted_vault_origin === true;
const hasCvv = Boolean(decryptedCard?.verification_value);
if (!hasCvv && !trusted) {
  // Apply your existing missing-CVV policy for this flow.
  return handleMissingCvvByExistingPolicy();
}
// Continue normal authorization, fraud and authentication checks.
return processPaymentWithExistingControls();

This sketch is not a complete payments handler. Keep decryption and sensitive card handling in the required PCI-compliant environment. If the flag is false or absent, retain your existing CVV policy; neither case introduces a new universal CVV requirement for flows that already accept CVV-less payments.

Common misunderstanding: The flag is not a bypass for all risk controls and is not a statement that every vaulted card is safe. It only changes how to interpret a missing CVV when Shopify explicitly marks the origin trusted.

How to test this

  1. In a 2027-01 test environment with the feature enabled, send a credit-card request with trusted_vault_origin: true and no CVV; confirm it is not rejected solely for the missing code.
  2. Send false and omitted flag cases and confirm existing CVV policy remains unchanged.
  3. Test a true flag with a supplied CVV; confirm normal processing and fraud checks still run.
  4. Confirm older API versions and apps without enablement handle an omitted field without throwing.
  5. Check payment and card-verification request paths separately; do not log decrypted card data or CVV.