Operational Manual to Create New E-Payment Partner.

This manual will describe the process of Stages To create an E-Payment via the B2B engine.

Create a new B2B E-Payment Partner

INSERT INTO gen.gnqb2p (gnqb2bpcode,gnqb2bpname,gnqepayyn) VALUES ('MWEB','MWEB E-Payments','N');

Create a DB procedure to encode the Standard ITS XML output. We suggest you do this in the E-payments package iz1pkg.sql. Remember iz1pkg.sql is only for E-payments. If you want to do something else, then start a new package and create a structure similar to iz1pkg.sql. The package MUST have a procedure called get_xml that will generate the Standard ITS XML output. (Example: iz1pkg.extra_MWEB) This procedure must do any validation or additional changes to the Standard ITS XML output.
Create a transformation style sheet that will take the Standard ITS XML output after it has gone through the extra_XXXX procedure and convert it into the format that the E-payments partner requires. (Example: iz1MWEBo.xsl)
Create a transformation style sheet that will take the Response from the E-payment partner and convert it into the Standard ITS Response XML format. (Example: iz1MWEBi.xsl)
Create a DB procedure to decode the Standard ITS Response XML format. This procedure should be used to i.e. change the bank's response code into an ITS acceptable response code. (Example: iz1pkg.decode_MWEB)

Code Structures involved

E-Payment Partners

See option {STWEBM-21}, Table GNQB2P
There must be one entry per B2B Partner.
Only one of these E-Payment Partners can be active at one stage.

E-Payment Transactions

See option {STWEBM-10}, Table GHXWOP
There must be one entry for each B2B transaction that has been done irrespective of the outcome.

B2B parameters for E-Payments

See Option {GCS2-18}, Table GMKPSS
This is a list of Mandatory codes that must be created for each partner

USEWALLET:

Set this field to 'N' if the partner requests data to be transferred via normal HTTP
Set this field to 'Y' if the partner requests data to be transferred via HTTPS. Note that when you are using SSL to transfer detail, You also need to setup the WALLET in Oracle and update the following SOD parameters :

WF: Wallet File
WP: Wallet Pin

URL:

Set this to the Path that will be supplied to you by the E-Payment Partner. Note: this will have the HTTP or HTTPS preifx and must correlate with what you have supplied with the USEWALLET parameter above.

URLPATH:

Set this to the actual folder and file that must be called within the web site as defined in the URL parameter above. NOTE: The combination of the URL and URLPATH will make out the full name to be called for this process to be started.

This is a list of Optional codes that could be created for each partner

EPROC:

This is the extract procedure for this specific E-Payment Partner.
This is used to add additional logic to the initial request and include things like a control key that must be made up each time a request is made.
This is usually a procedure inside the iz1pkg.sql program and starts with "extract_" and ends in the E-payment partner's code. (Example: iz1pkg.extract_MWEB)
This procedure is kicked off BEFORE the request is translated via the OUT/OUTFC/OUTTC combination codes.

DPROC:

This is the Decode procedure for this specific E-Payment Partner.
This is used to add additional logic or manipulate values that was received from the E-payment partner in their response.
This procedure is kicked off AFTER the response style sheet has been translated via the IN/INFC/INTC codes.
This is usually a procedure inside the iz1pkg.sql program and starts with "decode_" and ends in the E-payment partner's code. (Example: iz1pkg.decode_MWEB)

OUT:

This is used when you want the Standard ITS XML format to be translated into the format as is specified by the Partner. Along with this code you also need to specify the following two codes.

OUTFC:

This is the Format code for the above style sheet. Usually it is set to "XML"

OUTTC:

This is the format type for the above style sheet. Usually it is set to "REP"

This is used when you want the Partner Response style sheet translated back into the Standard ITS XML response format. Along with this code you also need to specify the following two codes.

INFC:

This is the Format code for the above style sheet. Usually it is set to "XML"

INTC:

This is the format type for the above style sheet. Usually it is set to "REP"

HDR:

This is the Header format for the xml to be transferred to the E-payment Partner.
Usually in the format of "text/xml" or "application/x-www-form-urlencoded"

EXTRA:

Any extra detail that needs to be transferred to the E-payment partner but does not exist on the standard ITS XML format.

Installation

When busy with an installation for HTTPS requests (Like MWEB) at a client do the following

Log into the GEN schema and run the following script (Cut from here):

set serveroutput on size 20000
CREATE OR REPLACE PROCEDURE xxolltst IS
v_pieces     SYS.UTL_HTTP.HTML_PIECES;
v_url        VARCHAR2(2000);
v_blob       BLOB;
v_clob       CLOB;
v_wallet_file     VARCHAR2(256) := gen.g54_its_sod('WF', 'BB', 'A'); -- 'file://disk3/itsv13';
v_wallet_password VARCHAR2(256) := gen.g54_its_sod('WP', 'BB', 'A'); -- 'admin123';
v_var XMLTYPE;
v_value VARCHAR2(2000);
BEGIN

--v_url := 'http://www.its.co.za';
--v_url := 'http://www.its.co.za/info/index.php';
v_url := 'https://secure.safeshop.co.za/s2s/myip.asp';

DBMS_LOB.CreateTemporary(v_blob, FALSE);
DBMS_LOB.CreateTemporary(v_clob, FALSE);

   UTL_HTTP.SET_WALLET(v_wallet_file, v_wallet_password);
   UTL_HTTP.set_transfer_timeout(7200);
   v_pieces := UTL_HTTP.request_pieces(v_url, 200000);

   FOR v_i IN 1..v_pieces.count LOOP
      DBMS_LOB.WriteAppend(v_blob,
                           LENGTH(v_pieces(v_i)),
                           UTL_RAW.CAST_TO_RAW(v_pieces(v_i)));
    END LOOP;

gen.g10pkg.blob2clob(v_blob, v_clob);

v_var := XMLTYPE(v_clob);
SELECT EXTRACTVALUE(v_var, '/Safe/RemoteIP')
INTO v_value
FROM DUAL;
DBMS_OUTPUT.PUT_LINE('IP='||v_value);

--DBMS_LOB.freeTemporary(v_clob);
--DBMS_LOB.CreateTemporary(v_clob, FALSE);
--SELECT updateXML(v_var, '/Safe/RemoteIP/text()', '********').EXTRACT('/').getCLobVal()
--INTO v_clob
--FROM gen.gaoins;

DBMS_OUTPUT.PUT_LINE('---------------------------');
DBMS_OUTPUT.PUT_LINE(SUBSTR(v_clob,1,250));
DBMS_OUTPUT.PUT_LINE(SUBSTR(v_clob,251,250));
DBMS_OUTPUT.PUT_LINE(SUBSTR(v_clob,501,250));
DBMS_OUTPUT.PUT_LINE('---------------------------');

DBMS_LOB.freeTemporary(v_clob);
DBMS_LOB.freeTemporary(v_blob);
END xxolltst;
/
show errors

execute xxolltst;

drop procedure xxolltst;

When the output comes back with a 'ORA-29248: an unrecgonized WRL was used to open a wallet' error, it means that the wallet has not been setup. Contact the DBA's
When the output comes back with a 'ORA-28871: certificate chain is incomplete' error, it means that the wallet does not have this security certificate loaded yet. Contact the DBA's and ask them to load the certificate. Remember, to supply them the SSL web address for this site.
When the output still comes back with a 'ORA-28871: certificate chain is incomplete' error, it means that you do not have the full/correct path and need more/correct detail
When the output comes back with a 'ORA-28759: Failed to open file' error, it means that the wallet files Is not yet on the Database Server. Please ensure that DBA's has created a wallet for you or that the following files has been transferred from ITS to the clients DB server (and NOT the App Server). Ensure that they have been chmod 777 ?wallet.*

cwallet.sso
ewallet.der
ewallet.p12

When the output comes back with an XML file similar to the following, it means that the machine you are on and MWEB is able to communicate and when the MWEB account is setup for this machine, MWEB will request an IP number for the account. Supply the one returned.

<?xml version="1.0" ?><Safe><RemoteIP>196.46.143.212</RemoteIP></Safe>

When the the B2B process runs and the output from iz1pkg comes back with something like 'The Store Security Check Failed', it means that this Machine has not been added yet. You probably updated to a new environment. Add this machines IP address to the Store Security at https://secure.safeshop.co.za
Please remember to drop this procedure and DO NOT give this procedure to the client as sensitive detail (Wallet password) could be picked up.

Debugging

Select of transaction code detail for Web Deposit event failed.

Please ask user to create a Transaction type definitions for event number 'WD' using {FCSO-7}

Unable to find Epayment reply detail

Ensure that B2B parameters 'ECODE' and 'DCODE' for the Partner is correct in {GCS2-12} (OR {GCS2-18} in Integrator)

i02pkg failed. Please contact the institution

Please Check i02pkg.i02_ins_iamlog as it might raise an exception. If so just recompiled i02pkg.

Processing Rules
	No special processing rules.