Card testing

Test your card integration in the sandbox environment by simulating:

• Successful payments for Expanded Checkout integrations using test card numbers.
• Card error scenarios by using rejection triggers.
• 3D Secure authentication scenarios.
• Recommended use cases for Expanded Checkout integration.

Simulate successful payments

To simulate a successful card capture with Expanded Checkout integration in sandbox:

• Ensure the integration is in sandbox mode, with a sandbox client ID, and connected to api-m.sandbox.paypal.com endpoints.
• Use a test card number with a future expiration date and a 3-digit CVV, or a 4-digit CVV for American Express.

Test static card numbers

Test card numbers

Test Expanded Checkout payments and saved payment method use cases with these test card numbers:

Test generated card numbers

Credit card generator

Generate additional credit cards for sandbox testing and PayPal Checkout. You can add generated credit cards to a PayPal sandbox account or use them to test credit card payments.

Simulate card error scenarios

Enter a rejection trigger in the First Name or Name on Card to simulate credit card error scenarios in Expanded Checkout integrations.

Rejection triggers

Rejection test simulations show a response_code that changes based on the test trigger you use. Rejection trigger values are case-sensitive.

Sample response

The response shows that the order is successfully created, but because a refusal was passed, the card payment status is DECLINED:

• Line 18 shows status=DECLINED. The card was refused.
• Line 51 shows avs_code=G. The card is globally unavailable.
• Line 52 shows cvv_code=P. The card wasn't processed.
• Line 53 shows response_code=5400. The card is expired.

{
  "id": "3M049991JF5624929",
  "status": "COMPLETED",
  "payment_source": {
    "card": {
      "last_digits": "6889",
      "brand": "VISA",
      "type": "CREDIT"
    }
  },
  "purchase_units": [
    {
      "reference_id": "default",
      "payments": {
        "captures": [
          {
            "id": "2FB04508RA686960W",
            "status": "DECLINED",
            "amount": {
              "currency_code": "USD",
              "value": "500.00"
            },
            "final_capture": true,
            "disbursement_mode": "INSTANT",
            "seller_protection": { "status": "NOT_ELIGIBLE" },
            "seller_receivable_breakdown": {
              "gross_amount": { "currency_code": "USD", "value": "500.00" },
              "paypal_fee": { "currency_code": "USD", "value": "13.44" },
              "net_amount": { "currency_code": "USD", "value": "486.56" }
            },
            "links": [
              {
                "href": "https://api-m.sandbox.paypal.com/v2/payments/captures/2FB04508RA686960W",
                "rel": "self",
                "method": "GET"
              },
              {
                "href": "https://api-m.sandbox.paypal.com/v2/payments/captures/2FB04508RA686960W/refund",
                "rel": "refund",
                "method": "POST"
              },
              {
                "href": "https://api-m.sandbox.paypal.com/v2/checkout/orders/3M049991JF5624929",
                "rel": "up",
                "method": "GET"
              }
            ],
            "create_time": "2022-08-09T22:20:05Z",
            "update_time": "2022-08-09T22:20:05Z",
            "processor_response": {
              "avs_code": "G",
              "cvv_code": "P",
              "response_code": "5400"
            }
          }
        ]
      }
    }
  ],
  "links": [
    {
      "href": "https://api-m.sandbox.paypal.com/v2/checkout/orders/3M049991JF5624929",
      "rel": "self",
      "method": "GET"
    }
  ]
}

Processor response and error codes

To understand why a card payment was declined, review the Orders v2 processor response object in the Orders API response.

For more information about card payment decline reasons and possible values, see:

• Card decline errors.
• Error responses for CVV and AVS.
• Processor response codes for non-PayPal payment processors.

Simulate 3D Secure card payments

Use 3D Secure to authenticate cardholders through card issuers. When your customer submits their card details on your website for processing, you can trigger 3D Secure. When triggered, customers are prompted by their card-issuing bank to complete an additional verification step to enter a one-time or static password, depending on the issuer's method.

For more information about including 3D Secure authentication in your payment flow, see:

• Learn more about 3D Secure for Expanded Checkout using the Orders API.
• Simulate 3D Secure-supported scenarios using 3D Secure test cards to verify your card integration.

Test integration

Test the recommended use cases for Expanded Checkout integration before you go live.

Accept payment

Decline payment

Authorize payment

See also

• Postman Collection — Test additional positive and 4xx error conditions.
• Simulate negative responses — Use API request headers to trigger negative responses.
• Error messages — Explore error messages supported by the Orders API.