Registration Key

Purpose:

A registration key is required in all Scripts that are sent to the Elavon Host for processing and will be sent as an HTTP Header Field in the POST request.

Example:

POST /cgi-bin/encompass4.cgi HTTP/1.1<CR><LF>
Content-Length: xxx<CR><LF>
Host: {Host Destination}<CR><LF>
Registration-Key: {Registration Key Value}<CR><LF>
Connection: Keep-Alive<CR><LF>
<CR><LF>
{XML or Value-Pair format}
POST /cgi-bin/encompass4.cgi HTTP/1.1<CR><LF>
Content-Length: xxx<CR><LF>
Host: {Host Destination}<CR><LF>
Registration-Key: {Registration Key Value}<CR><LF>
Connection: Keep-Alive<CR><LF>
<CR><LF>
{XML or Value-Pair format}

Notes:

The Registration Key should be sent as an HTTP Header field.

The NOVA_PORTAL_FAKE_KEY is only used to send transactions to the Elavon development host and cannot be used to send traffic to production hosts. A 20-character Production Registration Key will be assigned by the Certification Department after certification is complete.