Testing
Shared Test System
The shared RAVEN test system allows you to submit payments using the following credentials:
- UserName – ernest
- Shared Secret for use with the RAVEN API – all good men die young
- Password for RAVEN Online access – yellow
- PRN to use when submitting payments – 840033
The test URLs are the same as the production URLs documented in the API except that ‘raven’ is replaced by ‘demo’. For example, the hello service at: https://raven.deepcovelabs.com/realtime/hello is also accessible in the test system at: https://demo.deepcovelabs.com/realtime/hello
The test system supports the following services:
- USD, AUD, CAD, EUR, GBP, JPY and ZAR card payments
- AUD, USD, ZAR, DE-EUR and GBP electronic debits and credits.
- AUD, DE-EUR, GBP and USD cheques issued
The API test system is linked to the RAVEN Online demonstration system. Any payments submitted via the API are also visible in the RAVEN Online demo site.
In the shared test system any data submitted will be visible to all. Therefore, do not submit any private information to the test system. The system is refreshed on a regular schedule. After a refresh, any payments submitted to the test system will be lost. If you need to ensure payments are not deleted, use a dedicated test channel in the production system as described below.
Dedicated Test Channel In the Production System
If the shared test system does not meet your requirements, you may request that a dedicated test channel in the production system be configured. The dedicated test channel can be configured for just those products and currencies you plan to use. This channel is not shared and data submitted there is not visible to anyone but you. This data is also permanent. Test files and real-time test payments do not need to be formatted in a special way and are submitted in the same manner as live payments. A payment is considered to be a test payment if the processing channel has been configured as a test channel. This means you can ensure you are able to submit correctly formatted payments while in test mode and then be switched to live mode without making any changes to your process.
RAVEN processes test payments as follows:
- Payments are loaded and validated in the same way as live payments. Any validation errors will be reported as they would be for live payments.
- If the payment passes the validation step, the test is successful.
- Receipt and Result files are generated as they would be for live payments.
Test payments are only validated, they are not processed. Therefore, the Result and Receipt files will not contain values from the processing step. For example, test card payments will not contain approval codes in the Result file.