Testing

1. Which credit card information should you use for testing?

In order to perform test payments, simply use the following credit card numbers. That way nothing can go wrong. Moreover, the system won’t have any difficulty accepting this format. When testing 3-D Secure payments you will get an extra password page. Please read the the 3-D Secure frame carefully and enter the displayed or any custom password in the hints field.

1.a) How do I trigger failing refunds

You cannot trigger a failing refund.

2. How do I debug the PAYMILL bridge?

Simply use your develop extension (Chrome Bug, Firebug, etc.) for customer debugging.

3. How do I test specific error codes?

The following error codes can be returned for specific errors. Please implement an appropriate error handling, so you can deal with these errors.

3.1.) How do I test BRIDGE specific error codes?

3.1.a) The generic error codes, regardless of the means of payment will be returned:

• internal_server_error: Communication with PSP failed
• invalid_public_key: Invalid Public Key
• unknown_error: Unknown Error

3.1.b) The following errors can be returned in the case of credit card payment

• 3ds_cancelled: Password Entry of 3-D Secure password was cancelled by the user
• field_invalid_card_number: Missing or invalid creditcard number
• field_invalid_card_exp_year: Missing or invalid Expiry Year
• field_invalid_card_exp_month: Missing or invalid Expiry Month
• field_invalid_card_exp: Card is no longer valid or not anymore
• field_invalid_card_cvc: Invalid Checking Number
• field_invalid_card_holder: Invalid Cardholder
• field_invalid_amount_int: Invalid or missing amount for 3-D Secure
• field_invalid_amount: Invalid or missing amount for 3-D Secure deprecated, see blog post
• field_invalid_currency: Invalid or missing currency code for 3-D Secure

3.1.c) The following errors can be returned in the case of ELV-payments:

• field_invalid_account_number: Missing or invalid account number
• field_invalid_account_holder: Missing or invalid account holder
• field_invalid_bank_code: Missing or invalid bank code

3.2.) How do I test credit card-specific error codes?

The following error codes are returned by us to live transactions. The tests in the test mode are possible with a special credit card, in which you will get back a different error depending on the input of a specific expiration date.

Expirydate	Errorcode	Responsetext Description
01/2020	50501	RESPONSE_BACKEND_TIMEOUT_ACQUIRER The interface to the acquirer does not respond, so we get no response if the transaction was completed successfully
02/2020	50001	RESPONSE_BACKEND_BLACKLISTED The credit card is on a blacklist
03/2020	50201	RESPONSE_BACKEND_ACCOUNT_BLACKLISTED This customer account is on a black list
04/2020	50101	RESPONSE_DATA_CARD_LIMIT_EXCEEDED The credit card limit was exceeded with this transaction, or has already exceeded
05/2020	50102	RESPONSE_BACKEND_CARD_DENIED This card was rejected without reasons
06/2020	50103	RESPONSE_BACKEND_CARD_MANIPULATION This card was declined due to card manipulations
07/2020	40105	RESPONSE_DATA_CARD_EXPIRY_DATE The credit card expiration date is incorrect
08/2020	40101	RESPONSE_DATA_CARD_CVV The CVV is incorrect
09/2020	40100	RESPONSE_DATA_CARD There are problems with the credit card. Further details can not be passed
10/2020	40104	RESPONSE_DATA_CARD_INVALID The credit card is invalid
11/2020	50000	RESPONSE_BACKEND General problem with backend

You can find the complete list of error codes in the API reference. The CVC and date tests are to be disregarded as long as they have valid values (see example above).

4. How do I test webhooks?

With webhooks we give you the possibility to react automatically to certain events which happen within our system. A webhook can be set in live and testmode and is basically a URL where we send an HTTP POST request to every time one of the events attached to that webhook is triggered. Alternatively you can define an email address where we send the event’s information to. You can manage your webhooks via the API as explained at link to API Reference Weebhooks or within the settings in your merchant cockpit.

5. How do I test subscriptions?

Right now you can test subscriptions in testmode only with live conditions. This means that you have to wait the set timeuntil the subscription time has been processed. Right now we cannot manually trigger the subscription.

6. Which PAYMILL features do I verify regarding integration in live mode?

When integrating PAYMILL, you should be sure to check the following items before switching to live mode:

• Have the test keys been exchanged with the live keys? You will find the keys in your account.
• Are validation errors for the credit card correctly displayed in the ResponseHandler for the createToken function?
• A valid token is transferred to us by your server.
• Confidential credit card details such as number, card validity, and the CVC are not sent to your server in the form.
• All values sent via the payment form are valid.
• Are all API errors correctly intercepted?