Skip to Navigation | Skip to Content

Accessing RAVEN

Credentials

In order to begin working with the RAVEN system you will want to have access to both the RAVEN API (RAPI) and the RAVEN Online (RoL) web application. The API is used to programatically submit payments to RAVEN. With it you can have your server talk to the RAVEN system. RAVEN Online can be used to view payments that have been submitted. You can use it to check if API calls made have worked as expected. If you plan to process batch files you will also need access to the file exchange system. To access the above you will require some or all of  the following:

  • UserName – used when interacting with the RAVEN API and when logging into RAVEN Online.
  • Shared Secret – used to sign API requests.
  • Password or Secure Token for RAVEN Online – used along with your UserName when logging into RAVEN Online.
  • Payment Routing Number (PRN) – controls the routing of payment requests.
  • WebFolder UserName and Password – used to log into the file exchange system if you are batch processing.

There are two RAVEN systems: a demonstration system and the actual production system. The credentials used for each are different.

Demonstration System

The RAVEN demonstration system allows you to explore the API without requiring any configuration in the production system. You can immediately begin using it to develop and test your integration code. To access this system use the following credentials:

  • UserName – ernest
  • Shared Secret (for use with the RAVEN API) – all good men die young
  • Password for RAVEN Online access – yellow (Note: no security token is required)
  • PRN to use when submitting payments – 840033
  • URL for API – https://demo.deepcovelabs.com/realtime/
  • URL for RAVEN Online – https://demo.deepcovelabs.com/online/
  • URL for file exchange system – this is not supported on the demonstration system.

The demonstration 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 demonstration system is linked to the RAVEN Online demonstration system. Any payments submitted via the demonstration API are also visible in the RAVEN Online demonstration site.

Because the demonstration system is a shared system any data submitted will be visible to all users. Therefore, do not submit any private information to the demonstration system. The demonstration system is also refreshed on a regular schedule. Once refreshed, any payments submitted to the demonstration system are erased. If you need to ensure that payments are not deleted, you may use a dedicated test channel in the production system as described below.

To facilitate the move from the demonstration system to the production system, please ensure that when accessing the API you can easily change the UserName, Shared Secret, PRN and URL you are using.

Production System

Once you reach the point in your integration where the demonstration system is no longer suitable, for example, pre-production testing or if you need to test a currency or service not supported by the demonstration system, you will need access to the production system. To access the production system you will require the following credentials which will be provided by client support:

  • UserName – provided by client support
  • SharedSecret for use with the RAVEN API – provided by client support
  • Password and security token for RAVEN Online access – handy to have but not essential
  • PRN – there may be several of these depending on how payments are to flow
  • WebFolder UserName and Password – if you are batch processing.
  • URL for API – https://raven.deepcovelabs.com/realtime/
  • URL for RAVEN OnLine – https://raven.deepcovelabs.com/online/
  • URL for the file exchange system – https://dataexchange.deepcovelabs.com/<UserName>

The PRN may be set up to process requests using test channels or live channels. Initially, you can request that the PRN be set up with test channels. Files and real-time 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 payments on test channels as follows:

  1. Payments are loaded and validated as if they were live payments. Any validation errors will be reported as they would be for live payments.
  2. If the payment passes the validation step, the test is successful.
  3. 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.

Once your integration is complete and you are ready to go live you can request the channels be marked as live.

Raven Integration