Before you expose Payment Services for Adobe Commerce and Magento Open Source to your shoppers, it is a good idea to test in your sandbox environment and in production. Testing and validation help ensure that Payment Services functions work as expected and provide the best payment options for your store and customers.
Testing Payment Services in a sandbox environment is an important validation step, even though it is a simulated environment connected only to the PayPal sandbox, not to real banks and merchants.
Authorize and Capture), refund, or void the just-completed order. You can also simply create an invoice for an order, if your payment action is set to
Authorize and Capture.
When testing and validating your sandbox you must use fake credit card numbers, so that you are not creating real charges to an existing credit card account.
Use PayPal’s Credit Card Generator to generate random credit card information for testing.
PayPal’s sandbox payment processing is sometimes slow and the service can occasionally go down. This situation is not an indication of the speed and efficiency of live product payment processing.
It is highly recommended that you test Payment Services in production, with real credit cards and banks, before exposing this functionality to shoppers. Even though testing Payment Services in sandbox is important, testing in production is the most fool-proof method for ensuring Payment Services works as expected.
You can test Payment Services in production in one of two ways:
Complete your production testing with real credit cards and PayPal accounts, testing the entire lifecycle of a payment, including capture and refund. Completing the entire checkout and payment flow during testing gives you the clearest picture of how your Payment Services functionality will work when live shoppers are using it.
You should also verify the information that appears on the bank statements for the payment methods you use in production testing are correct and expected (including the description of your business).