Stripe测试环境下需验证虚拟卡支付遭拒问题排查求助

Hey there, this is a common gotcha with Stripe's test mode and verified card scenarios—let's walk through why this is happening and how to fix it.

Key Reasons for the Decline #

1. Legacy Charge API Doesn’t Handle Strong Customer Authentication (SCA) #

Your current code uses the deprecated stripe.Charge.create method, which doesn’t support modern authentication flows like 3D Secure. Even in test mode, Stripe enforces SCA-compliant steps for "verified" card scenarios, and the old Charge API can’t handle these requirements, leading to declines.

2. Test Card Explicitly Requires Authentication #

Stripe’s test cards mimic real-world behaviors. For example, the test card 4000 0000 0000 3220 is designed to require 3D Secure authentication. If your code doesn’t trigger and handle this auth step, the payment will fail immediately.

3. Missing Decline Context from Stripe #

You’re not capturing the specific decline reason Stripe returns. When a payment fails, Stripe provides detailed errors (like requires_authentication) that directly point to the issue—this is the fastest way to diagnose the problem.

Fixes to Implement #

Step 1: Switch to Payment Intents (Recommended by Stripe) #

Replace your legacy Charge API code with Payment Intents, which natively handle authentication flows. Here’s an updated Django view example:

@csrf_exempt
def create_payment_intent(request):
    if request.method == 'POST':
        try:
            intent = stripe.PaymentIntent.create(
                amount=int(request.POST["am"]),
                currency='usd',
                description=request.POST['desc'],
                payment_method_types=['card'],
            )
            # Return the client secret to your frontend to complete the payment flow
            return JsonResponse({'clientSecret': intent.client_secret})
        except stripe.error.StripeError as e:
            return JsonResponse({'error': str(e)}, status=400)

Step 2: Handle 3D Secure on the Frontend #

You’ll need to use Stripe’s frontend SDK (Stripe.js) to complete the payment flow. When the Payment Intent requires authentication, Stripe will prompt the user to finish 3D Secure, then confirm the payment automatically.

Step 3: Check Stripe Test Dashboard for Decline Details #

Log into your Stripe Test Dashboard, navigate to Payments, and select the failed payment. The "Failure reason" field will tell you exactly why the card was declined (e.g., requires_authentication, incorrect_cvc). This is critical for narrowing down specific issues.

Step 4: Use Test Cards with Known Behaviors #

Stripe provides test cards for different scenarios:

• 4242 4242 4242 4242: Generic test card (no auth required, works with your original code)
• 4000 0000 0000 3220: Requires 3D Secure (will fail without the proper flow)
• 4000 0000 0000 0002: Simulates insufficient funds decline

Quick Note #

Even in test mode, Stripe enforces SCA rules for cards that require verification. Your original code skips the authentication step, which is why verified virtual cards are failing while non-verified ones work.

内容的提问来源于stack exchange，提问作者Marko Maksimovic