SmartVista Webgate Product Documentation installation

Webgate solution documentation SmartVistaWebgate installation and configuration guide Contents 1. Glossary .........................................................................................................6 2. Webgate concepts and architecture ..............................................................7 3. System requirements .....................................................................................8 3.1. Hardware requrements ....................................................................................... 8 3.2. OSrequirements .................................................................................................. 8 3.3. Application server ............................................................................................... 8 3.4. Java ...................................................................................................................... 8 3.5. Database .............................................................................................................. 8 4. Installation .....................................................................................................9 4.1. Environment ........................................................................................................ 9 4.2. 4.1.1. Database installation .............................................................................. 9 4.1.2. Weblogic AS ............................................................................................ 9 Home directory structure .................................................................................. 11 4.3. Configuration files ............................................................................................. 12 5. Modules configuration .................................................................................14 5.1. Module activation ............................................................................................. 14 5.2. Database connection ......................................................................................... 14 5.3. USSD .................................................................................................................. 15 5.4. 1. Connection to SVFE .................................................................................... 15 2. Additional parameters ................................................................................ 16 Payments ........................................................................................................... 16 5.5. 1. Connection to SVFE .................................................................................... 16 2. Payment providers...................................................................................... 16 3. Flexible payment providers. ....................................................................... 18 Internet bank integration .................................................................................. 18 5.6. 1. Connection to SVFE .................................................................................... 18 2. Card validation ............................................................................................ 18 SMS .................................................................................................................... 19 5.7. 1. Connection to SVFE .................................................................................... 19 2. Gateways configuration.............................................................................. 19 EMAIL................................................................................................................. 19 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 2 of 210 5.8. 1. Connection to SVFE .................................................................................... 19 2. EMail Configuration .................................................................................... 20 SMS Banking ...................................................................................................... 20 5.9. 1. Connection to SVFE .................................................................................... 20 2. SMS Bank channel configuration ................................................................ 20 3. SMS commands configuration files ............................................................ 21 External systems................................................................................................ 22 1. Connection to SVFE .................................................................................... 22 2. M-PESA CBS Configuration ......................................................................... 22 5.10. SV REMOTE BANK .............................................................................................. 22 1. Connection to SVFE .................................................................................... 23 2. SV Remote bank service properties............................................................ 23 5.11. SmartVista1 ....................................................................................................... 25 1. Connection to SVCG.................................................................................... 25 2. SV1 service properties ................................................................................ 25 5.12. SmartVista2 ....................................................................................................... 27 1. SV2 service properties ................................................................................ 27 6. Webgate application deployment .................................................................27 7. Web services specifications..........................................................................34 7.1. Field type definitions ......................................................................................... 34 7.2. USSD & Internet bank common ........................................................................ 36 7.3. 1. Complex types ............................................................................................ 36 2. Response codes .......................................................................................... 40 3. Inner response codes.................................................................................. 44 4. SOAP Header............................................................................................... 46 Internet bank integration web service .............................................................. 47 7.4. 1. Cards Service............................................................................................... 47 2. Transaction history ..................................................................................... 81 3. Operations processing ................................................................................ 89 Services ............................................................................................................118 USSD integration web service .........................................................................122 1. 2. 3. 4. 5. 6. 7. 8. RegisterCard ............................................................................................. 122 AccountList ............................................................................................... 124 blockCard ..................................................................................................126 unblockCard .............................................................................................. 128 activateCard .............................................................................................. 129 pinChange .................................................................................................131 makeTopup ............................................................................................... 133 validateUtilityPayment .............................................................................135 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 3 of 210 7.5. 9. makeUtilityPayment .................................................................................139 10. cardToCardTransfer ..................................................................................142 11. cardToAccountTransfer ............................................................................144 12. cardToAccountExternalTransfer ............................................................... 145 13. nonCardAccountToAccountTransfer ........................................................ 147 14. balanceInquiry .......................................................................................... 149 15. miniStatement .......................................................................................... 151 16. cardlessRemmitance.................................................................................154 17. changeCardLimit ....................................................................................... 156 18. chequeBookRequest .................................................................................158 OTP integration web service ...........................................................................160 7.6. 1. generateOtp.............................................................................................. 160 IVR integration web service ............................................................................162 7.7. 1. balanceInquiry .......................................................................................... 162 2. makeTopup ............................................................................................... 164 SMSGate WS Interface ....................................................................................166 7.8. SV WS Interface ............................................................................................... 167 1. Complex types .......................................................................................... 167 2. Instant Issue Service .................................................................................174 3. PIN Change Service ...................................................................................185 8. SMS Bankingdocumentation ...................................................................... 189 a. Main configuration .......................................................................................... 189 b. SMS Commands definition ..............................................................................189 SMS Templates definition ...............................................................................195 Card balance enquiry....................................................................................... 196 c. Card status enquiry ......................................................................................... 196 d. Mini-statement................................................................................................ 197 e. Service activation ............................................................................................ 198 f. Service deactivation ........................................................................................ 199 g. Block card ........................................................................................................200 h. Unblock card....................................................................................................200 i. Create virtual card ........................................................................................... 201 j. Card to card transfer ....................................................................................... 202 k. Payment ..........................................................................................................204 l. Payment by template ......................................................................................205 9. SmartVista2 documentation ...................................................................... 207 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 4 of 210 10. Attachments ......................................................................................... 208 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 5 of 210 1. GLOSSARY Term Definition SV SmartVista SVWG SmartVistaWebgate Application SVFE SmartVista Front End SVBO SmartVista Back Office WGMS Weblogic managed Webgate Application WEBGATE_HOME Webgate Application home directory. Configuration and log files will be located under this directory. usually /home/weblogic/webgate_home (Linux/Unix) WL_HOME Weblogic AS home directory. Usually /home/weblogic/ /Oracle/Middleware/Oracle_Home (Linux/Unix) server dedicated for Weblogic Domain directory. Usually WL_DOMAIN WL_HOME/user_projects/domains/base_domain (Linux/Unix) Table 1. Glossary © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 6 of 210 2. WEBGATE CONCEPTS AND ARCHITECTURE SmartVistaWebgate solution is designed as a universal integrational layer application that connects SmartVista services with third party applications or in case of standalone installation it integrates third party applications between each other. Webgate shares several interfaces (such as Web Services) for third party applications to interact with SmartVista family applications. Webgate is the modular application, below is the list of available modules:  USSD integration (Web services)  Payments (using third party providers: WebServices);  Internet Bank integration (Web services);  SMS module (send/receive SMS messages);  Email module (send/receive Email messages);  SMS Bank (depends on SMS module);  External systems (CBS M-PESA);  SV Remote Bank integration (Web services);  SmartVista2 (Integration via SVIS and SVAP);  OTP integration (Web services);  IVR integration (Web services);  mVisa integration (Web services). Any module can be switched on/off using configuration file. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 7 of 210 3. SYSTEM REQUIREMENTS 3.1. HARDWARE REQUREMENTS Processor : 4 cores RAM : 8 GB HDD : 20 GB 3.2. OSREQUIREMENTS Oracle Enterprise Linux, Red Hat Enterprise Linux 6.7, HP-UX. 3.3. APPLICATION SERVER Weblogic 11g, Weblogic 12c, Weblogic 14 3.4. JAVA JDK 8 3.5. DATABASE Oracle 11g, Oracle 12c © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 8 of 210 4. INSTALLATION 4.1. ENVIRONMENT Webgate installation is available only if all requirements listed in System requirements are met. 4.1.1. Database installation All necessary SQL commands can be found in attachment SVWG DB schema installation: 1. DB user for Webgate should be created by DBA user. Sample SQL script for creating a user and granting necessary privileges can be found in schemauser.sql 2. Run all scripts in the ./install drectory. The script with the correct running order is ./META-INF/ru.bpc.db.install.sql. 3. Run all scripts from ./update directory. 4.1.2. Weblogic AS Weblogic AS installation is out of scope of this document. Please refer to Oracle online documentation. At this point we assume that Weblogic Domain is successfully installed, Administration Console is accessible, separate Weblogic managed server for Webgate application is created. Next JVM arguments are strongly recommended to added to Webgate managed server start arguments in one line. -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+TraceClassUnloading -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:gc.log -XX:+HeapDumpOnOutOfMemoryError © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 9 of 210 -XX:HeapDumpPath=${WEBGATE_HOME}/heapdumps -Xms2048m -Xmx2048m -XX:MaxPermSize=1024m -XX:PermSize=1024m © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 10 of 210 4.2. HOME DIRECTORY STRUCTURE SmartVistaWebgate requires that environment variable with name WEBGATE_HOME has to be configured. It should refer to the directory path on the server where all related data will be stored. For instance, it may look like this: -DWEBGATE_HOME=/home/weblogic/svwg In the directory WEBGATE_HOME the next subdirectories have to be created: Folder name Description conf Contains configuration files of webgate and its‘ all services logs Log files base directory. Webgate automatically rotates log files to logs/archive directory based on time and size policy certs Webgate’s identity and trust keystores(trustStore.jks and identityStore.jks). Example folder Certs with empty jksstoreswith default password can be found in the attachments. Table 2. Home directories © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 11 of 210 4.3. CONFIGURATION FILES All configuration files are properties files where configuration is stored as a set of key-value pairs. The format of record is the next: key=value Configuration files should be placed into <WEBGATE_HOME>/conf directory. Below is the table with configuration file name, its’ sample and a related module name. Module name File name Sample configuration - webgate.properties webgate.properties USSD ussd.properties PAYMENTS payment.properties IB internetBank.properties SMS svfesms.properties EMAIL email.properties SMS_BANKING smsbank.properties CBS_MPESA external.properties ussd.properties payment.properties providers.properties internetBank.properties svfesms.properties gateways.xml email.properties smsbank.properties external.properties © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 12 of 210 SVRB_1_29 svrb.properties SV2 sv2.properties OTP otp.properties IVR ivr.properties MVISA mVisa. properties svrb.properties sv2.properties otp.properties ivr.properties mVisa.properties Table 3. Module configuration files File webgate.properties is mandatory and should present in any configuration If service is enabled then its property file must be placed in the <WEBGATE_HOME>/conf directory otherwise the application will fail to start. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 13 of 210 5. MODULES CONFIGURATION The main configuration file of SVWG is webgate.properties and it allows configuring some core features. 5.1. MODULE ACTIVATION Property ru.bpc.webgate.profile holds the list of comma separated names of active services, it means that if service name appears in this list this service will be enabled and started. Property name Sample value Descriprion ru.bpc.webgate.profile IB,USSD,SMS,PAYMENTS The list of active modules Table 4. Module activation property The configuration from the Table 4 enables Internet Banking, USSD, SMS and Payments modules. All other modules will be disabled. For more information about service names see the Module configuration files. To apply changes on any configuration file in conf directory SVWG application has to be restarted (WGBS restart ot Weblogic Webgate Deployment restart) 5.2. DATABASE CONNECTION There are 3 database connections that are required for SVWG: Connection to SVFE database (properties sv.db-fe.*); Connection to SVBO database (properties sv.db-bo.*); Connection to SVWG own schema (properties sv.db.*, see 4.1.1 Database installation). All of the connections have similar configuration. Below is a sample configuration of connection to SVWG schema. Property name Sample value Descriprion sv.db.jdbc-url jdbc:oracle:thin:@localhost:1 521/webgate JDBC URL, representing the database and schema location sv.db.user webgate user/schema name © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 14 of 210 sv.db.password webgate1 password Table 5. Webgate database connection configuration. 5.3. USSD USSD module configuration is stored in ussd.properties file. 1. Connection to SVFE Property name Sample value Descriprion sv.ussd.comm.host localhost IP address or host domain name of the FrontEnd server sv.ussd.comm.port 51618 Communication port sv.ussd.comm.headerL ength 4 ISO8583 packet size block length sv.ussd.comm.echoInte rval 0 Delay between EPay echo packets in minutes. Set to 0 to disable. sv.ussd.comm.sendTim eout 30000 How much millisecons should we wait for FE reply. default: 30 seconds sv.ussd.terminal.merch antId 001601110218 ISO8583 conversation sv.ussd.terminal.merch antType 8 Merchant type used impersonating as device ISO8583 conversation when during sv.ussd.terminal.termin alId 10000002 Terminal ID used impersonating as device ISO8583 conversation when during Terminal location used impersonating as device when sv.ussd.terminal.termin alLocation Table 6. EPay ISO8583 connection configuration with FrontEnd system. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 15 of 210 2. Additional parameters For inner purposes there is a possibility of changing some USSD service parameters. Property name Sample value Descriprion ussd.serviceType 5 Service Type for transactions from USSD channel ussd.serviceId 500 SVFE Service ID of USSD service ussd.blockStatus 05 SVFE card status is used in blockCard service ussd.serviceCheck true If the parameter is enabled webgate sends separate serviceCheck ISO message to FE system before each operation to check if ussd service is enabled ussd.oneCardToServce true If the parameter is enabled only 1 card can be linked to a phone number(ussd service) Table 7. USSD service transaction parameters. 5.4. PAYMENTS Payments service configuration is stored in payment.properties and providers.properties files where providers.properties is not mandatory. 1. Connection to SVFE Connection configuration to SVFE for payments is the same as for USSD service except that parameters name pattern is sv.payment.*. For more details refer to 5.3 USSD 2. Payment providers Payment service contains a bunch of payment providers and each of them has to be configured individually. If some provider is not used in the project his configuration must be left with default values. It must be noted, that there are 2 types of payment providers access: Direct connection. o In this case SmartVista Webgate has a direct access to payment provider service © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 16 of 210 Connection through an intermediary In this case SmartVista Webgate sends payment request to some third-party service specifying a provider name. The first type of connection is strict and tightly depends on implementation while the second one has common interface to all payment providers and only provider names may differ. SVWG allows configuring the list of providers for the second type of access. The third-party, that gives an access to such provider, is called dispatcher. There are can be many dispatchers and each may support many providers. The format of property record for dispatcher is the next: payment.dispatcher[<index>].name=<dispatcher name> payment.dispatcher[<index>].profile=<profile name> payment.dispatcher[<index>].providers=>:<list of provider name separated by semicolon> where: o <index> - integer value starting with 0; o <dispatcher name> - known for Webgate dispatcher name; o <profile name> - profile common name; o <list of provider name separated by semicolon> - the list of supported provider. It is important that each provider name has to be unique across all dispatchers. o The list of available dispatcher names: o DISP_EGRESS o DISP_TNM o DISP_AIRTEL o DISP_ACCESS o DISP_ESCOM o DISP_MRA o DISP_DSTV o DISP_SMARTVEND o DISP_COLLECTION o DISP_ZAIN Dispatcher’s providers have higher priority than direct connection providers. It means that if there is a direct connection to provider, but this provider also was include in some dispatcher configuration, all request to this provider will go through dispatcher. o Example of dispatcher configuration: payment.dispatcher[0].name=DISP_EGRESS payment.dispatcher[0].profile=EGRESS payment.dispatcher[0].providers=DSTV;COH;CUT;GZU;ZIMRA;MSU;TELONE;BUSE;TO © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 17 of 210 PICS;CIMAS;ZBLIFE;KADOMA;MEIKLES;MASVINGO;CHINHOYI;RUWA;EDGARS;ZETDC;TRUW ORTH;MOBILE payment.dispatcher[1].name=DISP_TNM payment.dispatcher[1].profile=TNM payment.dispatcher[1].providers=TNMPRE 3. Flexible payment providers. A file providers.properties can be used for flexible settings of payment providers. Example of provider configuration for service name “DUMMY_PROVIDER”: service.DUMMY_PROVIDER.providerId=887 service.DUMMY_PROVIDER.phoneNumber.tag=36 service.DUMMY_PROVIDER.phoneNumber.label=Phone Number service.DUMMY_PROVIDER.phoneNumber.value=88002008888 service.DUMMY_PROVIDER.clientName.tag=8 service.DUMMY_PROVIDER.clientName.label=User Name Where service.[service name].providerId is a configured provider ID. Not mandatory parameters to extend sent to FE data: service.[service name].providerId.[additional field].tag is a tag number in DE48 to send additional data to FE during payment process; service.[service name].providerId.[additional field].label is a label of an additional field; service.[service name].providerId.[additional field].value is a default value of an additional field. This parameter can be omitted. 5.5. INTERNET BANK INTEGRATION Internet Banking service configuration is stored in internetBank.properties file. 1. Connection to SVFE Connection configuration to SVFE for internet banking is the same as for USSD service except that parameters name pattern is sv.ib.*. For more details refer to 5.3 USSD 2. Card validation When card validation request comes to internet bank web service it checks card status with valid card statuses. The last one can be configured. Property name Sample value Descriprion ws.validnessCardStatuses 0,4 Comma separated list of valid card statuses Table 8. Valid card status property. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 18 of 210 5.6. SMS SMS service configuration is stored in svfesms.properties file and gateways configuration in gateways.xml. 1. Connection to SVFE Connection configuration to SVFE for sms is the same as for USSD service except that parameters name pattern is sv.sms.*. For more details refer to 5.3 USSD 2. Gateways configuration There are several types of gateways supported by SMS service:  SMPP  GSM modem  HTTP server  Soap web service To see a sample of gateways configuration refer to Module configuration files. Available configuration properties for gateways message exchange in the table below. Property name Sample value Descriprion smscomp.gateConfigLocation file:${WEBGATE_HOME }/conf/gateways.xml The path to the gateways.xml file route.sms.request-deliveryreports false Should be set to true if SMS delivery reports are required. Default: false sms.encoding ascii SVFE sms Default:ascii sv.route.sms.gatewayid=modem1,smpp-gateway modem1,smppgateway A list of gateway id’s that are defined in gateways.xml to be used to send a message. First available will be picked. If empty - default gateway will be used. message encoding. Table 9. SMS module configuration properties for gateways. 5.7. EMAIL Email service configuration is stored in email.properties file. 1. Connection to SVFE Connection configuration to SVFE for email is the same as for USSD service except that parameters name pattern is sv.email.*. For more details refer to 5.3 USSD © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 19 of 210 2. EMail Configuration Email message sending is supported via SMTP, POP3 and IMAP protocols. Property name Sample value Descriprion email.protocol smtp Exchange protocol. Possible values: smtp, imap, pop3. email.user test@localhost User domain name email.port 25 Port number email.password Password1 Password email.content-type text/html Email body content type email.encoding ascii Encoding used to transfer Subject and Message Body. Default: ascii email.auth false Should be set to true if authorization is enabled on the email server. email.fromAddress Your favorite Bank <no- Sender address. “Your favorite Bank” reply@bank.com> will appear in “from” field. Table 10. Email module configuration 5.8. SMS BANKING SMS Banking service configuration is stored in smsbank.properties file. 1. Connection to SVFE Connection configuration to SVFE for sms banking is the same as for USSD service except that parameters name pattern is sv.smsbank.*. For more details refer to 5.3 USSD 2. SMS Bank channel configuration Property name Sample value Descriprion smsbank.enabled true Enables or disables Default: false smsbank.concurrency 2 Number of threads to process SMS messages from mobile operator. Default: 2 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 20 of 210 SMS bank. smsbank.service-id 300 Service Id in SVFE. Default:300 smsbank.default-currency 840 Default currency to be used in requests. Should be set on each environment. If not defined then default currency from general configuration file will be used smsbank.request-deliveryreports true Should delivery reports for outgoing SMS bank messages be requested. Default:true smsbank.preauthpayments true Should validation message be sent before financial Table 11. SMS Banking service properties. 3. SMS commands configuration files please refer to SMS Bank documentation. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 21 of 210 5.9. EXTERNAL SYSTEMS Configuration of external systems (like CBS) is stored in external.properties file. It is supposed, that each project may have some additional connections with third-party systems. In that case such systems have to be configured as external and for each system there are should be distinct service (profile) name. SmartVista Webgate supports the next list of external systems: o M-PESA (CBS-like system in Safaricom) 1. Connection to SVFE Connection configuration to SVFE for external systems is the same as for USSD service except that parameters name pattern is sv.<external system name>.*. For more details refer to 5.3 USSD 2. M-PESA CBS Configuration Property name Sample value Descriprion mpesa.out.address http://localhost:8002/mp esaOut M-PESA address mpesa.in.address /mpesa/resultService Result web service relative path that receives result messages from MPESA mpesa.thirdPartyId FHLK#7623$% Third party ID in M-PESA mpesa.password 12345 Password mpesa.secretKey G(DSj43.km Secret key for encryption mpesa.resultUrl http://10.7.40.171:7001/S VWS/MPESA/Result URL address of Result web service that is sent to M-PESA mpesa.initiator.id 86131000009 Initiator ID mpesa.receiver.id 3214 Primary party ID mpesa.timeout 5000 Timeout in milliseconds of waiting result from M-PESA Table 12. SOAP M-Pesa configuration . 5.10. SV REMOTE BANK © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 22 of 210 Web service url SV Remote bank module provides an integration of SVRB to SmartVista FE, BO and CBS through web service. For each SVRB version the webgate has special profile. For example for SVRB verion 1.24 should be used profile SVRB_1_24. 1. Connection to SVFE Connection configuration to SVFE is the same as for USSD. For details refer to 5.3 USSD 2. SV Remote bank service properties Property name Sample value Descriprion svrb.card-rb-service-id 550 Id of service to be binded to a card when attempting to show it in SV remote bank ws.cbsWs.url http://localhost:20013/cb sWs CBS Web service to get account balances svrb.supported-currencies 840,938 A list (or single) digital currency codes supported for SVRB application. Nullable, default: trans.defaultcurrency from webgate.properties svrb.route.sms.gateway-id smppgateway An id (or list delimited by comma) of SMS gateway IDs (see gateways.xml) used to send Remote Bank SMS messages. If not defined then default gateway will be used svrb.request-deliveryreports true Should be delivery reports be requested for remote bank sms messages. Default: true. NOTE: If there are no SMS gateways supporting delivery reports and the property is set to true it can break sms message sending at all svrb.institute-id 9999 An id of institute which is SVRB forking for. Nullable svrb.cbs-balance true Should card and account balances be fetched from CBS WS svrb.cbs-user SV CBS Web service user © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 23 of 210 svrb.trans-hist.types-show ALL The parameter is used to configure types of transactions according to theirs response codes and types. Possible values: ALL - retrieve all transactions, ONLY_SUCCESSFUL only successful transactions, ALL_EXCEPT_INCOMING_TRANSFERS - all transactions except of declined incoming svrb.showZeroFee false To show fee field in transaction history and info about just executed transaction in case of the value 0(the real fee could be configured in for example in BO system). svrb.enroll.phoneMaskJQu +999 99 999 9?9 99 ery Mobile phone number mask on enroll page. jQuery mask format svrb.enroll.phone.placehol +xxxxxxxxxxxx der Mobile phone placeholder. It shows on the enrolment page. svrb.enroll.cardNumberM askJQuery 9999 9999 9999 9999 Card number mask on enroll page. jQuery mask format svrb.enroll.cardNumber.p attern 111122\\d{10}|111121\\d {10} Card number regular expression pattern for value from enrolment page svrb.enroll.expDate.patter n yyyyMM Expiry date pattern on the enrolment page svrb.messages.cacheseconds 1000 Seconds after that locale properties files will be reloaded. Default -1 : do not reload svrb.bo-transactionhistory.enabled false By default gettransaction history and mini-statement only from FE. With this option it will allow to get transaction from BO2 after fe-depthdays. Default value is FALSE : transaction is from FE only © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 24 of 210 svrb.trans-hist.fe-depthdays 15 Transactions with a period from current date - 'fe-depth-days' till 'sysdate' should be fetched from FE DB. Others should be fetched from SV2 BO system. Default : 30 svrb.cardlessoperation.code-show OTP To show code after generate cardless operation. It depends on business logic of each bank Possible values: OTP - otp, PIN - pin, CVV - cvv, VIRTUAL_HPAN - last 10 digits of HPAN. svrb.excludeVirtualCards false Virtual cards are not considered on restrictions checking during a user login action. Possible values: true, false. Default: false svrb.cardType false Allowed config usageType when create virtual card default value is empty. Possible values: KEY1:VALUE1,KEY2:VALUE2. Default: empty Example: svrb.cardType=SINGLE:40,MULTIPLE:37 Table 13. 5.11. SV Remote bank service properties SMARTVISTA1 SmartVista1 module provides an integration of SmartVista Webgate with SmartVista1 with Instant Issuing and PIN Change services. Current WSDL is in attachments Issuing WSDL 1. Connection to SVCG Connection to SVCG database (properties sv.db-cg.*) is the same as for other datasources (refer to 5.2) 2. SV1 service properties Property name Sample value Descriprion sv.api.issuing.out.address /issuing Uri address of Issuing service © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 25 of 210 sv.fe.scp.host localhost IP address of SVFE server sv.fe.scp.port 22 SCP port on SVFE server sv.fe.scp.destination /home/svfe/input/autoloa d Absolute path to the autoload folder of SVFE sv.fe.scp.username svista Username for SCP connection sv.fe.scp.password Svista1 Password for SCP connection sv.fe.scp.chmod 664 Chmod parameters for uploaded files sv.application.prepaid.limi t.serviceId 1 this service id which limit is set. It is used Customer Limits verification in BO sv.application.prepaid.limi t.scheme 226 limit scheme customer block that we send during the instant issuance for prepaid card generation with BTRT01 Table 14. SV service properties © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 26 of 210 5.12. SMARTVISTA2 SmartVista2 module provides an integration of SmartVista Webgate with SmartVista2 API throw SVIS and SVAP web services. Current WSDL is in attachments SVAP WSDL and SVIS WSDL 1. SV2 service properties Property name Sample value Descriprion sv2.svap.out.address http://localhost:18002/sv ap SV2 BO SVAP service url. sv2.svap.out.operator ADMIN Operator name/login who fills an application sv2.svap.out.app.directory /weblogic/svwg/apps A directory to store applications that were not successfully processed sv2.svap.in.address http://localhost:18002/sv apIn URL of published by webgate SVAP service sv2.svis.out.address http://localhost:18002/svi s SV2 BO SVIS service url. sv2.svis.in.address http://localhost:18002/svi sIn URL of published by webgate SVAP service Table 15. SV2 service properties 6. WEBGATE APPLICATION DEPLOYMENT Below are the steps to install/deploy Webgate applicaton to Weblogic AS 11g Login to Weblogic console. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 27 of 210 Go to deployments Click “Lock & Edit” button (if available) © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 28 of 210 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 29 of 210 Click “Install” Select installation file path Click “Next” © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 30 of 210 Click “Finish” Click “Activate Changes” (if available) After that on the Deployments page Webgate application has to be in the state Active. If there are some active services like Internet Banking or USSD, their interfaces can be opened with url http://<host>:<port>/webgate/SVWS © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 31 of 210 To open Webgate UI go to http://<host>:<port>/webconsole/ui © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 32 of 210 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 33 of 210 7. WEB SERVICES SPECIFICATIONS This section describes web services provided by SVWG. All technical details about field necessity or field data type can be found in their WSDL files.To list all web services are running at the moment please access SVWG by web service list URL. Actual wsdl’s also can be downloaded by clicking on a link to the right ofWSDL label. 7.1. FIELD TYPE DEFINITIONS Note: A “Len” column defines a maximum length of a field. Important: All numeric fields which represented as strings can be negative, zero or positive. The “-” sign is placed before a negative value. There is no any sign before zero or positive numbers. Short name WSDL type Information L long Min:-67000 9223372036854775808 5500 Max: 9223372036854775807 0 I int Min: -2147483648 Max: 2147483647 0 5000 S string Type represents character strings. Length is unlimited if length is not defined explicitly Cardholder Name D date Date without time 2014-12-12 DT dateTime Date with time 2014-04-26T21:32:52 B boolean Boolean value (true/false) true decimal The decimal separator is always a point (.), and no separation at the thousand mark may be added. There is no support for scientific notation. 123.456, +1234.456, 1234.456, -456 DEC Example © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 34 of 210 DUR LS duration list Table 16. The duration data type is used to specify a time interval. P5Y (period of 5 years), PT15H (a period of 15 hours) a list of strings 100 34 56 -23 1567 AB here 100, 34, 56,-23, 1567, AB are items of the list Field types © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 35 of 210 7.2. USSD & INTERNET BANK COMMON This article describes common parts for USSD and Internet Bank web services. Each web service contains operations (methods) which will be described below. All query operations have errorCode and errorDescription fields in their responses. These fields will be filled if the request is not succeeded. All data manage operations have status, code, descr fields in their responses. 1. Complex types Argument M/O Type Description amount M L Amount in the minimum fractions for the currency currencyCode M S ISO currency code AmountDTO Table 17. Argument M/O Type Description id M S Channel id description O S Channel description Amount O AmountDTO Price per month ChannelDTO Table 18. Argument M/O Type Description accountNumber M S actualBalance AmountDTO Actual account’s balance M Account number Table 19. AccountDTO Argument M/O Type Description userId M S User ID in Third-party system channelId M AmountDTO System ID reason O S Reason of changing Table 20. AuditDTO © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 36 of 210 Argument M/O Type Description accountNumber M S Account Number instId S Institution ID M Table 21. AccountDetailsDTO Argument M/O Type Description cashLimit O S Total Cash Withdrawal limit purchaseLimit O S Total Purchase limit transferLimit O S Total Transfer limit avalilableCashLimit O S Total Cash Withdrawal avalilablePurchaseLimit O S Total Cash Withdrawal limit avalilableTransferLimit O S Total Transfer limit countryLimit O S Country level limit terminalLimit O S Terminal level limit Table 22. CardLimitsFeDTO Argument M/O Type Description limitType 7 M S limitValue 12 M L dateFrom - O D dateTo - O D actionType 6 M S Table 23. LimitEditDTO © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 37 of 210 Argument M/O Type Description limitType 7 M S limitValue 12 O L dateFrom - O D dateTo - O D tdy 12 O L LimitInfoDTO Table 24. Argument M/O Type Description amount - M Number currency - M L TransactionAmountDTO Table 25. Argument M/O Type Description transmissionDateTime - O D Trace - O L dateTimeLocalTransaction - M D referenceNumber - O S authidresp - O S IdentificationDataDTO Table 26. Argument M/O Type Description cardDataInputMode - S: M - MANUAL, - MAGNETIC_STRIPE_READ © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 38 of 210 cardholderAuthenticationMethod - M S: - NOT_AUTHENTICATION - PIN - SIGNATURE_BASED PointServiceDataCodeDTO Table 27. Argument M/O Type Description hpanMask - O S cardholderId - O S - ValidateCardAdditionalDataDTO Table 28. Argument M/O Type Description phoneNumber - M S serviceType - M S cardholderIdInfo - M S serviceId - M S serviceObjectType - M S: Table 29. CARD - ACCOUNT ServiceActionAdditionalDataDT Argument M/O Type Description serviceType - S O - © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 39 of 210 cardStatus - M S: hpanMask - O S cardholderId - O S Table 30. - CALL_ISSUER - WARM_CARD - DO_NOT_HONOR - HONOR_WITH_ID - NOT_PERMITTED - LOST_CARD - STOLEN_CARD - CALL_SECURITY - INVALID_CARD - PICK_UP_CARD - CALL_ACQUIRER_SECURITY - CARD_IS_NOT_ACTIVATED - PIN_ATTEMPTS_EXCEEDED - FORCED_PIN_CHANGE - CREDIT_DEBTS - PIN_ACTIVATION - INSTANT_CARD_PERSONIFICATION_WAITING - FRAUD_PREVENTION - TEMPRORY_BLOCKED_BY_CLIENT - PERMANENT_BLOCKED_BY_CLIENT BlockCardAdditionalDataDTO 2. Response codes Code Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 40 of 210 WSA001 Wrong card WSA002 Wrong card status WSA003 Negative response from FE WSA004 Unknown bill payment WSA005 Utility company not mapped WSA006 Mobile operator not mapped WSA008 Negative amount WSA009 Record to edit is not found WSA010 Invalid mobile WSA011 Duplicated card WSA012 Duplicated mobile WSA013 Duplicated record WSA014 Card expired WSA015 Expiry required WSA016 Wrong expiry WSA017 Wrong date WSA018 Wrong amount WSA019 Referenced mobile not registered WSA020 Mobile referenced by payment WSA022 Wrong currency WSA023 Wrong pinblock WSA024 Wrong customer number WSA025 Wrong amount or currency WSA026 Payment executed but not approved by Provider WSA027 Payment not processed due to error © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 41 of 210 WSA028 Remote system rejection WSA029 Missing mandatory field WSA030 Card is not exist WSA031 Merchant is not exist WSA032 Merchant is not valid WSA033 Service is not registered WSA034 Service has been linked before WSA035 Service has not been linked before WSA036 Wrong source system WSA037 MemNO is required WSA038 Wrong restriction field format WSA039 Wrong phone number format WSA040 Wrong account number WSA041 Card number or Account number field must be passed in the request WSR000 Authorization error WSR001 Query error WSR002 Unknown error WSR003 FE request sending error WSR004 Processed with error WSR005 Cardless Remittance failure WSR006 Virtual card failure WSR007 Credit push failure WSR008 Balance inquire failure WSR009 Mini statement failure WSR010 Card activation failure © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 42 of 210 WSR024 Query timeout WSU001 Query error WSU002 Unknown error WSU003 FE request sending error WSU004 Card Registration error WSU005 Mobile phone is not registered yet WSU006 Mobile topup failure WSU007 Utility payment verification failure WSU008 Utility payment failure WSU009 Card2Card failure WSU010 Card2Account failure WSU011 Balance inquire failure WSU012 Mini statement failure WSU013 Cardless Remittance failure WSU014 Card block failure WSU015 PIN Change failure WSU016 Account list failure WSU017 Card2Account External failure WSU018 Phone number is not registered WSU019 Card activation failure WSU020 Card unblock failure WSU021 Change card limit failure WSU022 Cheque book request WSU023 Card personification failure WSU024 Non-card transfer failure © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 43 of 210 WSI000 Balance inquire failure WSI001 Mobile topup failure WSI002 Wrong one time passcode WSI003 Passcode has expired WSI004 No more attempts WSI005 Wrong one time passcode ID WSO000 Generating one time passcode failure WSR016 P2P transfer failure WSR017 Validate card failure WSR018 Service action failure WSR019 Block card failure Table 31. Response codes 3. Inner response codes Code Description 00 Successful transaction 01 Call issuer 03 Invalid Merchant ID 04 Invalid card, capture 05 Do not honor transaction 08 Approve with identification 12 Invalid transaction 13 Cannot process amount. 14 Invalid account 15 The card is already active 30 The message isn't within standards © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 44 of 210 31 Issuer inoperative 33 Card expired, capture card 36 Account restricted, capture card 37 Call Security - Capture 41 Lost Card - Capture 43 Stolen Card - Capture 51 Insufficient funds 55 Incorrect PIN, foreign. 57 Not permitted 61 Negative auth cycle limit exceeded 61 Card's or Acc's cycle limit exceeded 62 Bad card (on_us) 65 Limit reached for count of tx in cycle 68 Timer time out 75 Excessive pin failures 76 Wrong Pin, Excessive pin failures 77 The card has NOT ANY accounts 78 Original transaction could not be found 90 Response status unknown 91 Service not available 92 Invalid Payment Parameter 93 Service blocked 94 Duplicate transmission 95 amount being reversed greater than orig 96 Cannot process transaction © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 45 of 210 97 Service not allowed for client 98 Invalid insurance number A1 Service is already binded A2 Service is not binded A3 Invalid service data A4 MAC error A5 Debts absence. A6 Invalid payment data A7 Additional information required A8 No such object in system A9 Object is not created in system AA Object is already created in system AB Invalid CVV2 Table 32. Inner response codes 4. SOAP Header For authentication of incoming messages every SOAP request has to have SOAP header with corresponding credentials. Bellow there is an example of such header: <soapenv:Header> <sec:credentials xmlns:sec="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </sec:credentials> </soapenv:Header> Credentials will be provided by bank. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 46 of 210 7.3. INTERNET BANK INTEGRATION WEB SERVICE 1. Cards Service This Web service designed for query card details. For more technical details see ICard.wsdl in attachments. 1.1. GetCardList Get the card list by customerId. Argument Len M/O Type Description customerId 20 M S Customer’s identification number Table 33. GetCardList request Argument Len M/O Type Description CardNumber 24 M S Card number ExpiryDate 10 M D Card expiry date EmbossedName 26 M S Embossed name of the cardholder ContractId 6 M S Contract id ContractDescr 64 M S Contract description Virtual 1 M S 1-Virtual, 0-Not virtual CardType 2 M S Card type code CardTypeName 200 M S Card type description CardCategory 10 M S Debit/Credit/Prepaid CardPS 4 M S Card payment system – Visa, MC, CUP, AMEX, JCB CardStatus 8 M S SVBO Card status code CardStatusName 256 M S SVBO Card status description CardCurrency 3 M S Applicable only for Credit/Prepaid cards – card’s linked account currency. Alphabetic 3 letter code PrimaryIndicator 1 M S 0-Supplementary, 1- Primary card © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 47 of 210 MemNo 1 M Table 34. I The ordinal number of plastic for card GetCardList response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getCardList> <customerId> <customerId>754452</customerId> </customerId> </ws:getCardList> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getCardListResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <cardList> <card> <cardNumber>5890888877776666</cardNumber> <expiryDate>2021-09-30</expiryDate> <embossedName>MR CARDHOLDER NAME</embossedName> <contractId>001</contractId> <contractDescr>CASH24</contractDescr> <virtual>0</virtual> <cardType>18</cardType> <cardTypeName>Cash24 Local Debit card</cardTypeName> <cardCategory>Debit</cardCategory> <cardPS>MC</cardPS> <cardStatus>CHST0</cardStatus> <cardStatusName>VALID CARD</cardStatusName> <cardCurrency>USD</cardCurrency> <primaryIndicator>1</primaryIndicator> <memNo>1</memNo> </card> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 48 of 210 <card> <cardNumber>5890888877776667</cardNumber> <expiryDate>2021-09-30</expiryDate> <embossedName>MR CARDHOLDER NAME2</embossedName> <contractId>001</contractId> <contractDescr>CASH24</contractDescr> <virtual>0</virtual> <cardType>18</cardType> <cardTypeName>Cash24 Local Debit card</cardTypeName> <cardCategory>Debit</cardCategory> <cardPS>MC</cardPS> <cardStatus>CHST0</cardStatus> <cardStatusName>VALID CARD</cardStatusName> <cardCurrency>USD</cardCurrency> <primaryIndicator>1</primaryIndicator> <memNo>1</memNo> </card> </cardList> </reply> </ns2:getCardListResponse> </soap:Body> </soap:Envelope> 1.2. GetCardOverview All Data will be fetched from SVBO DB or SVFE DB. Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which the details to be provided memNo 2 O S SVFE card’s memNo value Source 2 O S Source System name, from where to fetch the data. Possible values: FE, BO. Default value: BO. GetCardOverview request. Table 35. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 49 of 210 ContractId 6 M S Contract id ContractDescr 64 M S Contract description Virtual 1 M S 1-Virtual, 2-Not virtual CardType 2 M S Card Type CardCategory 7 M S Debit/Credit/Prepaid CardPS 4 M S Card payment system – Visa, MC, CUP, AMEX, JCB CardStatus 8 M S SVBO Card Status CardCurrency 3 M S Applicable only for Credit/Prepaid cards – card’s linked account currency. PrimaryIndicator 1 M S 0-Supplementary, 1- Primary card CustomerNumber 20 O S SVBO PersonId of the Cardholder, as part of Release-2 it will become equal to LCIF number in the CBS CBSAccountNumber 32 O S For a Debit card it is a CBS account number used for online ISO transaction processing with CBS (in case of more than one CBS account linked then it will be a sequence of this fields). For a credit card it is a CBS account number used for recovery of credit card dues AssociatedAccountNumber 32 M S Internal SV Account number (in case of more than one account number linked with the card sequence of the fields will be returned) CardholderName 150 M S Cardholder name as stored in SV person table PrimaryCardHolderName 150 O S To be returned only for Supplementary cards. Cardholder name as stored in SV person table for the corresponding cardholder of the primary card. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 50 of 210 PrimaryCardNumber 24 O S Filled only for supplementary cards EmbossingName 26 M S Embossing name as it is on the card plastic MobileNumber 20 O S Cardholder mobile number OfficeNumber 20 O S Cardholder office number EmailAddress 100 O S Cardholder email address IssueDate 19 M S Card’s Issue date Activation Date 19 O S Card’s Activation date ExpiryDate 19 M S Card’s Expiry date Repayment Plan 16 O S The numeric configuration for the Credit card to be returned, which defines the percentage of the Outstanding credit balance to be paid-off from CBS account BranchID 12 M S The Agent_Id in SVBO which issued the card. It will identify the SBM Branch. SBM India will be configured as separate Agent in SV for Release-2. AddressLine1 64 O S Cardholder’s statement address line 1 AddressLine2 40 O S Cardholder’s statement address line 2 AddressLine3 40 O S Cardholder’s statement address line 3 AddressLine4 40 O S Cardholder’s statement address line 4 lastTransactionAmount O S Last transaction amount in a minimum transaction currency units lastTransactionDate O S Last transaction date and time in format: yyyy-MM-dd'T'HH:mm:ss pinOffset 4 O S PIN offset pinCount 1 O S Count of consecutive invalid PIN denials ErrorCode 10 O S Error numeric code in case of request was not succeeded © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 51 of 210 internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 36. GetCardOverview response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getCardOverview> <cardNumber>1234123412341234</cardNumber> </ws:getCardOverview> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getCardOverviewResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <contractId>1123</contractId> <contractDescr>Some description</ contractDescr > <virtual>0</ virtual > <cardType>213</cardType> <cardCategory>Credit</cardCategory> <cardPS>VISA</cardPS> <cardStatus>2</cardStatus> <cardCurrency>480</cardCurrency> <primaryIndicator>0</primaryIndicator> <customerNumber>1702</customerNumber> <cbsAccountNumber>ACC123456</cbsAccountNumber> <cbsAccountNumber>ACC123457</cbsAccountNumber> <associatedAccountNumber>C23324235</ associatedAccountNumber> <cardholderName>Mister Cardholder</cardholderName> <primaryCardHolderName>Mister Primary Cardholder</primaryCardHolderName> <primaryCardNumber>1234123412341234</primaryCardNumber> <embossingName>MR CARDHOLDER</embossingName> <mobileNumber>23051231234</mobileNumber> <officeNumber>23051231234</officeNumber> <emailAddress>cardholder@mydomain.mu</emailAddress> <issueDate>15/12/2014</issueDate> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 52 of 210 <activationDate>12/12/2013</activationDate> <expiryDate>15/12/2018</expiryDate> <repaymentPlan>07</repaymentPlan> <branchId>1001</branchId> <addressLine1>Address line 1 value</addressLine1> <addressLine4>Address line 4 value</addressLine4> </reply> </ns2:getCardOverviewResponse> </soap:Body> </soap:Envelope> 1.3. GetCardDetailsBO All the data will be fetched from SVBO DB. This Web Service is designated to be called for Credit and Prepaid cards only, which balances are handled by SV. All amounts to be returned in Card account billing currency: Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which the details to be provided Table 37. GetCardDetailsBO request. Argument Len M/O Type Description CardCreditLimit 16 O S Credit Limit configured for the card Available Balance 16 M S Available card balance AvailableCreditBalance 16 M S Available credit balance CardCashLimit 16 M S Daily Cash Limit configured for the card Available Cash Balance 16 M S Available card cash balance OutstandingBalance 16 M S Current Outstanding balance (Total amount of funds owed to bank: Billed+Unbilled) OutstandingCashBalance 16 M S The same as above but pertaining only to Cash funds © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 53 of 210 UnbilledAmount 16 M S Current Unbilled amount – sum of cleared transactions, which will be billed on the next statement date LastBilledAmount 16 M S Last Statement billing amount MinimumPaymentDue 16 M S Last Statement Minimum Payment amount BillingDate 19 O S Last Statement Billing date DueDate 19 O S Last Statement Duedate PastDueFlag 1 O S 0/1 flag, which indicates if the Customer has paid its Minimum Payment amount before DueDate PastDueAmount 16 M S The total amount (billed in previous statement cycle), which was not paid before duedate PaymentsSinceLastStatement 16 M S Total sum of payment transactions performed since last statement ApprovedTransactionsTotal 10 M S Count of approved cleared transactions since last statement Purchases 16 M S Sum of cleared Purchases performed in current billing cycle CashAdvances 16 M S Sum of cleared Cash Advances performed in current billing cycle PaymentsCredit 16 M S Sum of cleared Payments and Credits performed in current billing cycle LPF 16 M S The amount of Late Payment Fee charged in the current billing cycle if exists AnnualFee 16 M S The amount of Annual Fee charged in the current billing cycle if exists © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 54 of 210 OverlimitFee 16 M S The amount of Overlimit Fee charged in the current billing cycle if exists Interest 16 M S The amount of Interest charged in the latest billing cycle if exists OutstandingAuthorizationAmo unt 16 M S Sum of amounts of authorizations which not cleared yet(Total Hold Amount) NumberofOutstandingAuthoriz 10 ations M S Number of authorizations which not cleared yet RewardOpenBalance 16 M S Number of reward points cardholder have at the beginning of billing cycle RewardEarned 16 M S Number of reward points earned in the current billing cycle RewardRedeemed 16 M S Number of reward points redeemed in the latest billing cycle RewardCloseBalance 16 M S Number of Reward points as of now – RewardOpenBalance+RewardEarne d CardCurrency 3 M S Default account currency FaceValue 16 O S Face Value of Prepaid card ErrorCode 10 O S Error numeric code in case of request was not succeeded ErrorDescription 50 O S Error text description in case of request was not succeeded Table 38. GetCardDetailsBO response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 55 of 210 <soapenv:Header/> <soapenv:Body> <ws:getCardDetailsBO> <cardNumber>1234123412341234</cardNumber> </ws:getCardDetailsBO> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getCardDetailsBOResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <cardCreditLimit>5000000</cardCreditLimit> <availableBalance>3412000</availableBalance> <availableCreditBalance>3412000</availableCreditBalance> <cardCashLimit>530000</cardCashLimit> <availableCashBalance>3242324554</availableCashBalance> <outstandingBalance>54123400</outstandingBalance> <outstandingCashBalance>3423124455</outstandingCashBalance> <unbilledAmount>50000</unbilledAmount> <lastBilledAmount>4222444</lastBilledAmount> <minimumPaymentDue>34500</minimumPaymentDue> <billingDate>2014-01-01</billingDate> <dueDate>2014-01-01</dueDate> <pastDueFlag>0</pastDueFlag> <pastDueAmount>2342354</pastDueAmount> <paymentsSinceLastStatement>534262346</paymentsSinceLastStatement> <approvedTransactionsTotal>8003450070</approvedTransactionsTotal> <purchases>234234</purchases> <cashAdvances>324234324234</cashAdvances> <paymentsCredit>435323</paymentsCredit> <lpf>2344</lpf> <annualFee>5404560</annualFee> <overlimitFee>23344</overlimitFee> <interest>50</interest> <numberofOutstandingAuthorizations>10</numberofOutstandingAuthorizations> <rewardOpenBalance>23</rewardOpenBalance> <rewardEarned>23</rewardEarned> <rewardRedeemed>32</rewardRedeemed> <rewardCloseBalance>12</rewardCloseBalance> <cardCurrency>480</ cardCurrency > <faceValue>200000</ faceValue> </reply> </ns2:getCardDetailsBOResponse> </soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 56 of 210 </soap:Envelope> 1.4. GetCardDetailsFE All the data will be fetched from SVFE DB. This Web Service is designated to be called for Credit and Prepaid cards only, which balances are handled by SV. All amounts to be returned in Card account billing currency. Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which the details to be provided memNo 2 O S SVFE card’s memNo value GetCardDetailsFE request. Table 39. Argument Len M/O Type Description AvailableBalance 12 M S Available card balance AvailableCashBalance 12 M S Available card cash balance OutstandingBalance 12 M S Outstanding balance, which will be CreditLimit + CreditLimitIncrease – AvailableBalance CardStatus 2 M S Card Hot status CurPaymentAmount 12 M S Summ of payments authorized by SVFE but not passed to SVBO in posting file yet limits - O CardLimitsFeDTO Card limits ErrorCode 10 O S Error numeric code in case of request was not succeeded ErrorDescription 50 O S Error text description in case of request was not succeeded Table 40. GetCardDetailsFE response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 57 of 210 <soapenv:Header/> <soapenv:Body> <ws:getCardDetailsFE> <cardNumber>1234123412341234</cardNumber> </ws:getCardDetailsFE> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getCardDetailsFEResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <availableBalance>23124455</availableBalance> <availableCashBalance>23412124</availableCashBalance> <outstandingBalance>234234</outstandingBalance> <cardStatus>2</cardStatus> <curPaymentAmount>324234</curPaymentAmount> </reply> </ns2:getCardDetailsFEResponse> </soap:Body> </soap:Envelope> 1.5. ChangeCardStatus This WebService is designated to perform Card status change immediately in SVFE system: Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which the details to be provided CardId 24 M S Card UID in clear text for which the details to be provided CardStatusCode 2 M S Hot Card Status code to be changed on UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR Reason 256 O S Description of the reason of card status change Table 41. ChangeCardStatus request. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 58 of 210 Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 42. ChangeCardStatus response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:changeCardStatus> <request> <cardNumber>1234123412341234</cardNumber> <cardStatusCode>4</cardStatusCode> <userId>admin</userId> <channelId>CRM</channelId> <reason>Reason</reason> </request> </ws:changeCardStatus> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardStatusResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:changeCardStatusResponse> </soap:Body> </soap:Envelope> 1.6. GetSuppCards The data will be fetched from SVBO DB. This WebService is designated to return the list of the card numbers, which are Supplementary cards for the Primary card with passed Card Number. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 59 of 210 Argument Len M/O Type Description CardNumber 24 M S Table 43. Card Number in clear text for which the details to be provided GetSuppCard request. Argument Len M/O Type Description Card 24 O S Sequence of card numbers for all cards which Supplementary for the card with corresponding passed CardNumber Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref. 2.4) ErrorDescription O S Error text description in case of request was not succeeded 50 Table 44. GetSuppCard response. Request Sample: <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ws=”http://ws.webgate.bpc.ru/”> <soapenv:Header/> <soapenv:Body> <ws:getSuppCards> <cardNumber>1234123412341234</cardNumber> </ws:getSuppCards> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”> <soap:Body> <ns2:getSuppCardsResponse xmlns:ns2=”http://ws.webgate.bpc.ru/”> <reply> <cardList> <card>1234123412341234</card> <card>43214321432143321</card> </cardList> </reply> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 60 of 210 </ns2:getSuppCardsResponse> </soap:Body> </soap:Envelope> 1.7. ChangeCardLimit This WebService is designated to set\update card limits in SVFE system. Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which ATM cash withdrawal limit needs to be changed NewLimit 12 M L New value of ATM cash withdrawal limit DateFrom - O D The date when new limit should begin to affect( leave empty in case of new limit is permanent) DateTo - O D The date when new limit will be expired( leave empty in case of new limit is permanent) UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR Reason 256 O S Description of the reason of card limit change Table 45. ChangeCardLimit request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error numeric code in case of request was not succeeded ErrorDescription 50 O S Error text description in case of request was not succeeded Table 46. ChangeCardLimit response. Request Sample: <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ws=”http://ws.webgate.bpc.ru/”> <soapenv:Header/> <soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 61 of 210 <ws:changeCardLimit> <request> <cardNumber>1234123412341234</cardNumber> <newLimit>5000000</newLimit> <dateFrom>2014-01-01</dateFrom> <dateTo>2014-12-31</dateTo> <userId>admin</userId> <channelId>CRM</channelId> <reason>Reason</reason> </request> </ws:changeCardLimit > </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/”> <soap:Body> <ns2:changeCardLimitResponse xmlns:ns2=”http://ws.webgate.bpc.ru/”> <reply> <status>1</status> </reply> </ns2: changeCardLimitResponse > </soap:Body> </soap:Envelope> 1.8. BalanceInquiry This WebService is designated to authorized card by CVV2 and get actual card balance. Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which ATM cash withdrawal limit needs to be changed CVV2 3 O L CVV2 of the card (for authorization) Table 47. balanceInquiry request. Argument Len M/O Type balance 12 O AmountDTO Actual card balance ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 48. Description balanceInquiry response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 62 of 210 Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:balanceInquiry> <balanceInquiry> <cardNumber>5423390007411264</cardNumber> <cvv2>301</cvv2> </balanceInquiry> </ws:balanceInquiry> </soapenv:Body> </soapenv:Envelope> Response Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soap:Body> <ns2:balanceInquiryResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <balance> <amount>4663283.0</amount> <currencyCode>840</currency> </balance> </reply> </ns2:balanceInquiryResponse> </soap:Body> </soapenv:Envelope> 1.9. getStatement This WebService is designated to get ministatement for the card (up to 5 last transactions). Argument Len M/O Type Description CardNumber 24 M S Card Number in clear text for which ATM cash withdrawal limit needs to be changed CVV2 3 O L CVV2 of the card (for authorization) Table 49. Argument Len M/O Type balance 12 O getStatement request. Description TransactionDTO Actual card balance © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 63 of 210 ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 50. getStatement response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getStatement> <getStatement> <cardNumber>5423390007411264</cardNumber> <cvv2>301</cvv2> </getStatement> </ws:getStatement> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getStatementResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <transactions> <transaction> <transactionDate>2015-03-30T00:00:00</transactionDate> <transactionAmount>20000.0</transactionAmount> <transactionCurrency>0</transactionCurrency> </transaction> <transaction> <transactionDate>2015-03-30T00:00:00</transactionDate> <transactionAmount>4683283.0</transactionAmount> <transactionCurrency>0</transactionCurrency> </transactions> </reply> </ns2:getStatementResponse> 1.10. ValidatePinblock The service is designed for pinblock validation. SVWG supports only 2 variants of PINBlock format: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 64 of 210 - 01: ISO 9564-I & ANSI X9.8 format 0; 03: Diebold & IBM ATM format. Argument Len M/O Type Description CardNumber 24 M S Card number in clear text Pinblock 16 M S Alphabetic and Numeric chars. Table 51. ValidatePinblock request. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 52. ValidatePinblock response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:validatePinblock> <request> <cardNumber>5423390007411264</cardNumber> <pinblock>5CE0D60F30985842</pinblock> </request> </ws:validatePinblock> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:validatePinblockResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:validatePinblockResponse> </soap:Body> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 65 of 210 1.11. ActivateCard The service is designed to activate and personalized issued card with cardholder data according his/here mobile phone number. Argument Len M/O Type Description cardNumber 24 M S Card number in clear text cellPhone 16 M S Cardholder mobile phone number expiryDate - M date Card expire date (day part may always be 01, example 2019-04-01) Table 53. ActivateCard request. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, request fails cardNumber - O S Card number processingCode - O S Processing code identificationData - O identificationDataDTO Identification data responseCode O S - Table 54. 00 - success ActivateCard response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:activateCard> <activateCard> <cardNumber>4891910012100016</cardNumber> <cellPhone>88002008888</cellPhone> <expiryDate>2019-06-01</expiryDate> </activateCard> </ws:activateCard> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 66 of 210 filled when </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:activateCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardNumber>5210972000000138</cardNumber> <processingCode>910000</processingCode> <identificationData> <transmissionDateTime>1970-09-11T19:04:17+03:00</transmissionDateTime> <trace>180825</trace> <dateTimeLocalTransaction>2019-0911T15:55:00+03:00</dateTimeLocalTransaction> </identificationData> <responseCode>00</responseCode> </reply> </ns2:activateCardResponse> </soap:Body> </soap:Envelope> 1.12. SetPin The service is designed to activate and personalized issued card with cardholder data according his/here mobile phone number. Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which thenew pin will be set CardId 24 M S Card UID in clear text for which the new pin will be set Pinblock 16 M S Pinblock in ISO-1 format UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR Table 55. SetPin request. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 67 of 210 ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails O S Internal error code internalErrorCode 2 Table 56. SetPin response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:setPin> <request> <cardId>5423390007411264</cardId> <pinblock>5CE0D60F30985842</pinblock> <userId>admin</userId> <channelId>WSO2</channelId> </request> </ws:setPin> </soapenv:Body> </soapenv:Envelope> Response Sample: soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:setPinResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:setPinResponse> </soap:Body> </soap:Envelope> 1.13. PinCountReset The service is designed to receive a request for reset of PIN Retry counter to 0 from Enterprise Integration Service. Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which thenew pin will be set © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 68 of 210 CardId 24 M S Card UID in clear text for which the new pin will be set Table 57. PinCountReset request. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails O S Internal error code internalErrorCode 2 Table 58. PinCountReset response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:pinCountReset> <request> <cardId>5423390007411264</cardId> </request> </ws:pinCountReset> </soapenv:Body> </soapenv:Envelope> Response Sample: soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:pinCountResetResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:pinCountResetResponse> </soap:Body> </soap:Envelope> 1.14. CardLink The service is designed to link a card from issued cards pool with a cardholder. The method supports following link types: 1)a new card for a new customer(account is not exist in SV). List of fields: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 69 of 210 ApplType = LKTPNECT, ExistCardNumber and ExistCardId fields are not needed in a request message. 2) a new card for an existing customer(account is exist in SV) when an old card is expired or in inactive status by any reason. List of fields: ApplType = LKTPEXCT, ExistCardNumber and ExistCardId fields are not needed in a request message. 3) a new main card for an existing customer(account is exist in SV) with old card blocking. List of fields: ApplType = LKTPEXOB, ExistCardNumber or ExistCardId field is required in a request message. 4) a supplementary card for an existing card and existing customer account. List of fields: ApplType = LKTPEXSC, ExistCardNumber or ExistCardId field is required in a request message. The service is developed only for SVFE KEF version. Argument Len M/O Type Description ApplType 8 M S Link operation type. Possible values: LKTPNECT - card for new customer LKTPEXCT - card for exist customer when the old card inactive LKTPEXOB - card for exist customer with the old card blocking LKTPEXSC - supplementary card for exist card and account CustomerNumber 200 M S Customer number(CBS) ProductId M S Product. Possible values: 8 Eg: 50000005 CardNumber 24 O S Linked Card Number CardId 24 M S Linked Card UID AccountNumber 32 M S Account number AccountCurrency 3 M S ISO currency code of the account Surname 200 M S Cardholder’s surname © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 70 of 210 FirstName 200 M S Cardholder’s first name IdNumber 200 M S Cardholder’s ID number(passport number) CellPhone 16 M S Cardholder’s mobile phone number EmailAddress 100 O S Cardholder’s email address ExistCardNumber 24 O S Existing Card number ExistCardId 24 O S Existing Card UID InstantFlag 1 M B If ‘true’ special Instant Payment EMV application will be used UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR Table 59. CardLink request. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails O S Internal error code internalErrorCode 2 Table 60. CardLink response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:cardLink> <cardLink> <applType>LKTPNECT</applType> <customerNumber>0000123456789</customerNumber> <productId>50000005</productId> <cardId>50076554372</cardId> <accountNumber>9911864516727</accountNumber> <surname>Wayne</surname> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 71 of 210 <firstName>Bruce</firstName> <cellPhone>88002008888</cellPhone> <existCardId>4891910012100015</existCardId> <instantFlag>true</instantFlag> <userId>admin</userId> <channelId>IOBUS</channelId> </cardLink> </ws:cardLink> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardLinkResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:cardLinkResponse> </soap:Body> </soap:Envelope> </soap:Envelope> 1.15. ChangeCardRestrictions The service is designed to apply issuer transaction restrictions for a card. The service is developed only for SVFE KEF version. Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which the limits will be set CardId 24 M S Card UID in clear text for which the limits will be set RestrictionsBit 16 M S Binary field where each position represents some restriction. 0 means restriction is of. 1 means restriction is on. Current masks: 0000000000000001 - internet on 0000000000000010 - international on 0000000000000100 - domestic on InternationalDateFrom - O D If date is presented the international restriction will take action starting this date © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 72 of 210 InternationalDateTo - O D If date is presented the international restriction will take action till this date UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR ChangeCardRestriction request. Table 61. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 62. ChangeCardRestriction response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:changeCardRestrictions> <changeCardRestrictions> <cardId>4891910012100016</cardId> <userId>admin</userId> <restrictionsBit>0000000000000101</restrictionsBit> <internationalDateFrom> 2017-01-01T08:00:00 </internationalDateFrom> <internationalDateTo> 2017-01-31T08:00:00 </internationalDateTo> <channelId>IOBUS</channelId> </changeCardRestrictions> </ws:changeCardRestrictions> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardRestrictionsResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 73 of 210 <reply> <status>1</status> </reply> </ns2:changeCardRestrictionsResponse> </soap:Body> 1.16. ChangeCardLimits The service is designed to apply card limits in FE system. The service is developed only for SVFE KEF version. Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which the limits will be set CardId 24 M S Card UID in clear text for which the limits will be set Limits 0..n M LimitEditDTO List of limits UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR ChangeCardLimits request. Table 63. Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 64. ChangeCardLimits response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:changeCardLimits> <changeCardLimits> <cardId>4891910012100016</cardId> <limits> <limitEdit> <limitType>LMTTC19</limitType> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 74 of 210 <limitValue>0</limitValue> <actionType>SET</actionType> <limitEdit> <limitEdit> <limitType>LMTTC20</limitType> <limitValue>0</limitValue> <actionType>REMOVE</actionType> <limitEdit> <limitEdit> <limitType>LMTTC21</limitType> <limitValue>0</limitValue> <actionType>SET</actionType> <dateFrom>2017-01-01T08:00:00</dateFrom> <dateTo>2017-01-31T08:00:00</dateTo> <limitEdit> </limits> <userId>admin</userId> <channelId>IOBUS</channelId> </changeCardLimits> </ws:changeCardLimits> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeLimitsResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:changeLimitsResponse> </soap:Body> </soap:Envelope> 1.17. GetCardData Get card data by card number or CardId(Card UID). The service is developed only for SVFE KEF version. Argument Len M/O Type Description CardId 24 M S Table 65. Argument Card UID in clear text for which the details to be provided GetCardData request. Len M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 75 of 210 Status 1 M S 0 - Fail, 1 - Success CardId 24 M S Card UID CardNumberMask 24 M S Card Number(PAN) mask in format BIN(6 number) + ****** + 4 last number CardStatus 2 M S FE Card Hot status value CardStatusName 100 M S FE Card Hot status name StatusChangeDate - M D Date of the last card status change ExpiryDate 10 M D Card expiry date RestrictionsBit 16 M S Binary field where each position represents some restriction. 0 means restriction is of. 1 means restriction is on. Current masks: 0000000000000001 - internet on 0000000000000010 - international on 0000000000000100 - domestic on InternationalDateFrom - O D If date is presented the international restriction will take action starting this date InternationalDateTo - O D If date is presented the international restriction will take action till this date Limits 0..n O LimitInfoDTO List of limits Table 66. GetCardData response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getCardData> <getCardData> <cardId>4891910012100016</cardId> </getCardData> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 76 of 210 </ws:getCardData> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getCardDataResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardId>4891910012100016</cardId> <cardNumberMask>923400******3434</cardNumberMask> <cardStatus>9</cardStatus> <cardStatusName>INVALID CARD, CAPTURE</cardStatusName> <statusChangeDate>2017-01-01T08:50:20</statusChangeDate> <expiryDate>15/12/2018</expiryDate> <restrictionsBit>0000000000000101</restrictionsBit> <internationalDateFrom> 2017-01-01T08:00:00 </internationalDateFrom> <internationalDateTo> 2017-01-31T08:00:00 </internationalDateTo> <limits> <limitInfo> <limitType>LMTTC19</limitType> <limitValue>0</limitValue> <tdy>0<tdy> <limitInfo> <limitInfo> <limitType>LMTTC20</limitType> <limitValue>0</limitValue> <tdy>0<tdy> <limitInfo> </limits> </reply> </ns2:getCardDataResponse> </soap:Body> </soap:Envelope> 1.18. Block card Make a block card transaction Argument M/O Type Description cardNumber O Card number S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 77 of 210 expiryDate O Date Card expired date cardSeqNo O S Card sequence No track2 O S Card track 2 identificationData M IdentificationDataDTO Identification data pointServiceData O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED additionalData M BlockCardAdditionalDataDTO Service additional data pinData O S PIN data Block card request Table 67. Argument Len M/O Type Description Status 1 S 0-Fail, 1- Success channels 0..n O ChannelDTO List of channels ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded cardNumber - O S Card number expiryDate - O Date Expired date card M © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 78 of 210 cardSeqNo - O S Card sequence No track2 - O S Card track 2 processingCode - M S Processing code identificationData - M IdentificationDataDTO Identification data pointServiceData - O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED responseCode - M S Response code accountId - O S Account ID Table 68. Block card response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:blockCard xmlns:ns2="http://ws.webgate.bpc.ru/"> <blockCard> <cardNumber>555555555555</cardNumber> <expiryDate>2020-09-01</expiryDate> <identificationData> <transmissionDateTime>2019-0808T11:36:53.724+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0808T11:36:53.724+07:00</dateTimeLocalTransaction> <referenceNumber>1234</referenceNumber> </identificationData> <pointServiceData> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 79 of 210 <cardDataInputMode>MAGNETIC_STRIPE_READ</cardDataInputMode> <cardholderAuthenticationMethod>NOT_AUTHENTICATION</cardholderAuthent icationMethod> </pointServiceData> <additionalData> <serviceType>3</serviceType> <cardStatus>LOST_CARD</cardStatus> <hpanMask>HpanMask</hpanMask> <cardholderId>cardHolderId</cardholderId> </additionalData> <pinData>pinData</pinData> </blockCard> </ns2:blockCard> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:blockCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardNumber>555555555555</cardNumber> <expiryDate>2020-09-01</expiryDate> <processingCode>910000</processingCode> <identificationData> <transmissionDateTime>1970-0808T11:36:53+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0808T11:36:53+07:00</dateTimeLocalTransaction> </identificationData> <responseCode>00</responseCode> </reply> </ns2:blockCardResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 80 of 210 <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:blockCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR018</errorCode> <errorDescription> Block card failure </ errorDescription> </reply> </ns2:blockCardResponse > </soap:Body> </soap:Envelope> 1.19. Set Default Account To set default account for a card Argument M/O Type Description cardNumber M S Card number cardId M S Card UID in clear text for which the new pin will be set expiryDate O Date Card expired date account M S Default account which is used to set for a card Set default account request Table 69. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded processingCode - M S Processing code © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 81 of 210 identificationData - M Table 70. IdentificationDataDTO Identification data Set default account response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser1</user> <pass>wspassword1</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:setDefaultAccount xmlns:ns2="http://ws.webgate.bpc.ru/"> <setDefaultAccount> <cardNumber>3434343434343434</cardNumber> <cardId>34343434</cardId> <account>555555555555555</account> </setDefaultAccount> </ns2:setDefaultAccount> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser1</user> <pass>wspassword1</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:setDefaultAccountResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:setDefaultAccountResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 82 of 210 <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2: setDefaultAccountResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSA003</errorCode> <errorDescription> Negative response from FE </ errorDescription> </reply> </ns2: setDefaultAccountResponse> </soap:Body> </soap:Envelope> 2. Transaction history This Web service designed for query FE and BO transactions. For more technical details see ITransaction.wsdl in attachments. 2.1. GetAuthHistoryFE All the data will be fetched from SVFE DB. This WebService is designated to be called for Credit and Prepaid cards only. WebService will return the list of transactions after applying the filters passed in Request arguments. It is highly recommended to specify any filter (e.g. TransactionDateFrom and TransactionDateTo) to provide query execution performance. Number of returning rows will be restricted by application’s sv.db.transaction.defaultmaxrows parameter, but it won’t be greater than number defined in the sv.db.querymaxRows parameter. A result set is ordered by TransactionDate desc. Only financial transactions will be fetched. Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which the details to be provided TransactionDateFrom - O DT Filter on the From date of the transaction was perfomed to be applied during search TransactionDateTo - O DT Filter on the To date of the transaction was performed to be applied during search BillingAmountFrom 12 O L Filter on the From Billing amount of the transaction to be applied during search BillingAmountTo 12 O L Filter on the To Billing amount of the transaction to be applied during search © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 83 of 210 TrxnAmountFrom 12 O L Filter on the From Original amount of the transaction to be applied during search TrxnAmountTo 12 O L Filter on the To Original amount of the transaction to be applied during search TrxnCurrency 3 O S Filter on the Original currency of the transaction to be applied during search, which will be passed in numeric ISO format BillingCurrency 3 O S Filter on the converted currency of the transaction to be applied during search, which will be passed in numeric ISO format NumberOfTransaction - O L Filter on the count of the latest transactions Declined O B If it equals true then only declined transactions will return; else if the field equals false, then only authorized will return; else if it not appears then all transactions will return; - GetAuthHistoryFE request. Table 71. Argument Len M/O Type Description TransactionID 9 M S Unique Id of transaction from SVFE TransactionDate - M DT The date when transaction was performed PostDate - O D The date when transaction was posted on the SVBO account for further accounting BillingAmount 12 M S Transaction amount in billing currency BillingCurrency 3 M S Billing currency ISO code TrxnAmount 12 M S Transaction amount in transaction currency TrxnCurrency 3 M S Original transaction currency TrxnType 4 M S SVBO transaction type TrxnDescription 100 O S Description of the transaction as it will appear in the Statement CardNumber 24 M S Card number © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 84 of 210 MCC 4 M S Merchant Category Code of the merchant where the transaction was originated MerchantName 40 M S Merchant name of the merchant where the transaction was originated DeclineReason 128 O S SVFE decline reason code to be returned Country 3 O S ISO country code ErrorCode 10 O S Error numeric code in case of request was not succeeded ErrorDescription 50 O S Error text description in case of request was not succeeded Table 72. GetAuthHistoryFE response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getAuthHistoryFE> <filter> <cardNumber>1234123412341234</cardNumber> <transactionDateFrom>2013-01-01T17:34:01</transactionDateFrom> <transactionDateTo>2013-01-31T01:56:57</transactionDateTo> <billingAmountFrom>500</billingAmountFrom> <billingAmountTo>50000</billingAmountTo> <transactionAmountFrom>500</transactionAmountFrom> <transactionAmountTo>500000</transactionAmountTo> <transactionCurrency>480</transactionCurrency> <numberOfTransaction>5</numberOfTransaction> <declined>true</declined> </filter> </ws:getAuthHistoryFE> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getAuthHistoryFEResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 85 of 210 <reply> <transactions> <transaction> <transactionId>22341255</transactionId> <transactionDate>2013-12-31T14:08:12</transactionDate> <postDate>2014-01-01 T14:08:12</postDate> <billingAmount>50000</billingAmount> <billingCurrency>480</ billingCurrency > <transactionAmount>500000</transactionAmount> <transactionCurrency>480</transactionCurrency> <transactionType>205</transactionType> <transactionDescription>Space Shuttle Mission</transactionDescription> <mcc>233</mcc> <merchantName>NASA</merchantName> <declineReason>insufficient funds</declineReason> </transaction> <transaction> <transactionId>22341255</transactionId> <transactionDate>2013-12-31</transactionDate> <postDate>2014-01-01</postDate> <billingAmount>100000</billingAmount> <transactionAmount>50000</transactionAmount> <transactionCurrency>480</transactionCurrency> <transactionType>205</transactionType> <transactionDescription>Souz-2 launch</transactionDescription> <mcc>233</mcc> <merchantName>ROSCOSMOS</merchantName> <declineReason>insufficient funds</declineReason> </transaction> </transactions> </reply> </ns2:getAuthHistoryFEResponse> </soap:Body> </soap:Envelope> 2.2. GetTransactionHistoryBO All the data will be fetched from SVBO DB. This Web service is designated to be called for Credit and Prepaid cards only. The service will return the list of transaction after applying the filters passed in Request arguments. It is highly recommended to specify any filter (e.g. TransactionDateFrom and TransactionDateTo) to provide query execution performance. Number of returning rows will be restricted by application’s sv.db.transaction.defaultmaxrows parameter, but it won’t be greater than number defined in the sv.db.querymaxRows parameter. A result set is ordered by TransactionDate desc. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 86 of 210 Argument Len M/O Type Description CardNumber 24 O S Card Number in clear text for which the details to be provided TransactionDateFrom - O DT Filter on the From date of the transaction was perfomed to be applied during search TransactionDateTo - O DT Filter on the To date of the transaction was performed to be applied during search BillingAmountFrom 16 O L Filter on the From Billing amount of the transaction to be applied during search BillingAmountTo 16 O L Filter on the To Billing amount of the transaction to be applied during search TrxnAmountFrom 16 O L Filter on the From Original amount of the transaction to be applied during search TrxnAmountTo 16 O L Filter on the To Original amount of the transaction to be applied during search TrxnCurrency 3 O S Filter on the Original currency of the transaction to be applied during search, which will be passed in numeric ISO format BillingCurrency 3 O S Filter on the converted currency of the transaction to be applied during search, which will be passed in numeric ISO format NumberOfTransaction - O L Filter on the count of the latest transactions Unbilled O B If it equals true then only unbilled transactions will return; else if the field equals false, then only billed will return; else if it not appears then all transactions will return; - GetTransactionHistoryBO request. Table 73. Argument Len M/O Type Description TransactionID 12 M S Unique Id of transaction from SVBO TransactionDate - M DT The date when transaction was performed © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 87 of 210 PostDate - O D The date when transaction was posted on the SVBO account for further accounting. If the transaction is not cleared yet, this field will be returned with no data BillingAmount 16 M S Transaction amount in billing currency BillingCurrency 3 M S Card account’s ISO digital currency code TrxnAmount 16 M S Transaction amount in transaction currency TrxnCurrency 3 M S Original transaction currency TrxnType 4 M S SVBO transaction type TrxnDescription 150 O S Description of the transaction as it will appear in the Statement CardNumber 24 M S Card number ErrorCode 10 O S Error numeric code in case of request was not succeeded ErrorDescription 50 O S Error text description in case of request was not succeeded Table 74. GetTransactionHistoryBO response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://svc.svws.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:getTransactionHistoryBO> <filter> <cardNumber>1234123412341234</cardNumber> <transactionDateFrom>2013-01-01T00:00:00</transactionDateFrom> <transactionDateTo>2013-01-31T05:00:00</transactionDateTo> <billingAmountFrom>500</billingAmountFrom> <billingAmountTo>50000</billingAmountTo> <transactionAmountFrom>500</transactionAmountFrom> <transactionAmountTo>500000</transactionAmountTo> <transactionCurrency>480</transactionCurrency> <numberOfTransaction>50</ numberOfTransaction > <unbilled>false</unbilled> </filter> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 88 of 210 </ws:getTransactionHistoryBO> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getTransactionHistoryBOResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <transactions> <transaction> <transactionId>22341255</transactionId> <transactionDate>2013-12-31T15:12:48</transactionDate> <postDate>2014-01-01</postDate> <billingAmount>50000</billingAmount> <transactionAmount>500000</transactionAmount> <transactionCurrency>480</transactionCurrency> <transactionType>205</transactionType> <transactionDescription>Space Shuttle Mission</transactionDescription> </transaction> <transaction> <transactionId>22341255</transactionId> <transactionDate>2013-12-31T00:13:67 </transactionDate> <postDate>2014-01-01</postDate> <billingAmount>100000</billingAmount> <transactionAmount>50000</transactionAmount> <transactionCurrency>480</transactionCurrency> <transactionType>205</transactionType> <transactionDescription>Souz-2 launch</transactionDescription> </transaction> </transactions> </reply> </ns2:getTransactionHistoryBOResponse> </soap:Body> </soap:Envelope> 3. Operations processing For more technical details see IVirtualIssuing.wsdl in attachments. 3.1. CardlessRemittance This service is designated to create card reference number with expire date, PIN code and initial sum. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 89 of 210 Argument Len M/O Type Description cardNumber 16 O S Card number. If this is not available, the senderAccountNumber mast be filled. cvv2 3 O N CVV2 of a source card withdrawalDueDate - M D Expiry date of a virtual card amount 1 M AmountDTO Remittance amount senderAccountNumber 32 S S Sender card account number. If this is not available, the cardNumber mast be filled. destCellPhone 16 O S Beneficiary mobile phone number instId 4 O S Institution ID virtCardProductType 2 O S Virtual card product type Cardless remittance request. Table 75. Argument Len M/O Type amount 1 O AmountDTO Remittance amount account 32 O S Sender card account number txnNum 11 O S Transaction reference number remittanceReferenceNumber 16 O S Masked virtual card number cvv2 3 O L CVV2 of generated virtual card pin 10 O S PIN value otp 99 O S One Time Password (OTP) withdrawalDueDate - O D Expiry date of a virtual card ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 76. Description Cardless remittance response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 90 of 210 Request Sample: <soapenv:Header/> <soapenv:Body> <ws:cardlessRemittance> <cardlessRemittance> <cardNumber>5423390007411264</cardNumber> <cvv2>999</cvv2> <withdrawalDueDate>2017-12-01</withdrawalDueDate> <amount> <amount>2000</amount> <currencyCode>840</currencyCode> </amount> <senderAccountNumber>1000000001</senderAccountNumber> </cardlessRemittance> </ws:cardlessRemittance> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardlessRemittanceResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <amount> <amount>2000</amount> <currencyCode>840</currencyCode> </amount> <account>1000000001</account> <txnNum>769771</txnNum> <remittanceReferenceNumber>******</remittanceReferenceNumber> <cvv2>0</cvv2> <pin>8301</pin> <otp>842341</otp> <withdrawalDueDate>2017-12-01</withdrawalDueDate> </reply> </ns2:cardlessRemittanceResponse> </soap:Body> </soap:Envelope> 3.2. ZIPIT Credit Push This message is used to transfer funds in real time to banked individuals at another bank. Argument Len M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 91 of 210 senderAccount 32 M S Sender account number amount 1 M AmountDTO Remittance amount receiverAccount 32 M S Receiver account number receiverBin 6 M L Receiver BIN externalTransactionType 3 O S External transaction type and possible values below: 2B -> Person to business BB -> Business to business B2 -> Business to person PP -> Person to person MB -> Money to bank transactionPurpose 20 O S Transaction purpose and possible values: CNT -> Construction EDU -> Education ENT -> Entertainment FES -> Funeral Expenses GFT -> Gift GRC -> Groceries HTR -> Holiday Travel INS -> Insurance Premium INV -> Investment MED -> Medical OTR -> Other RNT -> Rent SOWF -> Alimony and Maintenance UTB -> Utility Bills reference 99 O Table 77. L Customer reference number ZIPIT Credit Push request. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 92 of 210 Argument Len M/O Type Description ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 78. ZIPIT Credit Push response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:creditPush> <creditPush> <senderAccount>1000000001</senderAccount> <amount> <amount>3000</amount> <currencyCode>840</currencyCode> </amount> <receiverAccount>1000000002</receiverAccount> <receiverBin>5423391</receiverBin> <externalTransactionType>2B</externalTransactionType> <transactionPurpose>GFT</transactionPurpose> <reference>534634636</reference> </creditPush> </ws:creditPush> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:creditPushResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply/> </ns2:creditPushResponse> </soap:Body> </soap:Envelope> 3.3. Virtual card generation This message is used to generate virtual card. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 93 of 210 Argument Len M/O Type Description account 32 M S Card account number cellPhone 20 M S Cell phone number expiryDate - M D Card expiry date limitValue 12 M L Card limit amount in the minimum fractions for the account’s currency Generation of a virtual card request. Table 79. Argument Len M/O Type Description cardNumber 16 O S Card number expiryDate - O D Card expiry date limitValue 12 O L Card limit amount in the minimum fractions for the account’s currency cvv2 3 O L CVV2 of generated virtual card pin 10 O S PIN value ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 80. Generation of a virtual card response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:createVirtualCard> <createVirtualCard> <account>1000000001</account> <cellPhone>12345678</cellPhone> <expiryDate>2017-12-01</expiryDate> <limitValue>1000</limitValue> </createVirtualCard> </ws:createVirtualCard> </soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 94 of 210 </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:createVirtualCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <cardNumber>******</cardNumber> <expiryDate>2017-12-01</expiryDate> <limitValue>1000</limitValue> <pin>5634</pin> </reply> </ns2:createVirtualCardResponse> </soap:Body> </soap:Envelope> 3.4. Non-card transfer This message is used for non-card transfer between different institutions. Argument Len M/O Type Description sourceAccount - M AccountDetailsDTO Source account details destAccount - M AccountDetailsDTO Destination account details amount - M AmountDTO Transaction amount requestId - O S Unique message ID Non-card transfer request. Table 81. Argument Len M/O Type Description status 1 M L 0-Fail, 1- Success transactionId 12 O L Unique transaction ID requestId - O S Message ID(requestId) from a request message ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 82. Non-card transfer response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 95 of 210 Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:nonCardTransfer xmlns:ns2="http://ws.webgate.bpc.ru/"> <nonCardTransfer> <sourceAccount> <instId>0001</instId> <accountNumber>41075123456</accountNumber> </sourceAccount> <destAccount> <instId>0002</instId> <accountNumber>521234234234</accountNumber> </destAccount> <amount> <amount>10000</amount> <currency>840</currency> </amount> <requestId>0000001</requestId> </nonCardTransfer> </ns2:nonCardTransfer> </soap:Body> </soap:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:nonCardTransferResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>555777</transactionId> <requestId>0000001</requestId> </reply> </ns2:nonCardTransferResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 96 of 210 </soap:Body> </soap:Envelope> 3.5. Debit account presentment This message is used for debit account presentment. Argument Len M /O Type Description accountType - O AccountType Account Type accountId 1-99 M S Account number amount - M SvAmountDTO Transaction amount transmissionDateTime - O D Transmission date referenceNumber - O S Reference number Debit account presentment request. Table 83. Argument Len M/ O Type Description status 1 M L 0-Fail, 1- Success referenceNumber 12 O L Reference number accountType 1-99 M S Account Type ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 84. Debit account presentment response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 97 of 210 <soapenv:Body> <ws:debitAccountPresentment> <debitAccountPresentment> <accountType>DEFAULT</accountType> <amount> <amount>1000</amount> <currencyCode>840</currencyCode> </amount> <accountId>65874657879</accountId> <referenceNumber>1234567890</referenceNumber> </debitAccountPresentment> </ws:debitAccountPresentment> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:debitAccountPresentmentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <accountType>DEFAULT</accountType> <referenceNumber>1234567890</referenceNumber> </reply> </ns2:debitAccountPresentmentResponse> </soap:Body> </soap:Envelope> 3.6. Credit account presentment This message is used for credit account presentment. Argument Len M /O Type Description accountType - O AccountType Account Type accountId 1-99 M S Account number amount - M SvAmountDTO Transaction amount © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 98 of 210 transmissionDateTime - O D Transmission date referenceNumber - O S Reference number Credit account presentment request. Table 85. Argument Len M/ O Type Description status 1 M L 0-Fail, 1- Success referenceNumber 12 O L Reference number accountType 1-99 M S Account Type ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 86. Credit account presentment response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soapenv:Body> <ws:creditAccountPresentment> <creditAccountPresentment> <accountType>DEFAULT</accountType> <amount> <amount>1000</amount> <currencyCode>840</currencyCode> </amount> <accountId>65874657879</accountId> <referenceNumber>1234567890</referenceNumber> </creditAccountPresentment> </ws:creditAccountPresentment> </soapenv:Body> </soapenv:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 99 of 210 Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:creditAccountPresentmentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <accountType>DEFAULT</accountType> <referenceNumber>1234567890</referenceNumber> </reply> </ns2:creditAccountPresentmentResponse> </soap:Body> </soap:Envelope> 3.7. validateUtilityPayment Verify customer data. This message has to be called before makeUtilityPayment. Argument M/O Type Description cardNumber M S Card number cvv2 O L CVV2 of the card (for authorization) sourceAccountNumber O S Source account number utilityAccountNumber M S Utility account number amount O AmountDTO Transaction amount provider M S Provider name. Examples: ESCOM – Escom DSTV – DSTV MRA – MRA ValidateUtilityPayment request Table 87. Argument Len M/O Type Description Status 1 M 0-Fail, 1- Success S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 100 of 210 transactionId 12 O S Transaction ID utilityAccountNumber 20 O S Verified utility account number that has to be used into makeUtilityPayment message channels 0..n O ChannelDTO List of channels ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 88. ValidateUtilityPayment response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateUtilityPayment xmlns:ns2="http://ws.webgate.bpc.ru/"> <validateUtilityPayment> <cardNumber>3434343434343434</cardNumber> <cvv2>999</cvv2> <utilityAccountNumber>1000100010001</utilityAccountNumber> <amount> <amount>1000</amount> <currency>454</currency> </amount> <provider>MRA</provider> </validateUtilityPayment> </ns2:validateUtilityPayment> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 101 of 210 </auth:credentials> </soap:Header> <soap:Body> <ns2:validateUtilityPaymentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>75432294</transactionId> <utilityAccountNumber>1000100010001</utilityAccountNumber> </reply> </ns2:validateUtilityPaymentResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateUtilityPaymentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR011</errorCode> <errorDescription>Utility payment verification failure</ errorDescription> </reply> </ns2:validateUtilityPaymentResponse> </soap:Body> </soap:Envelope> 3.8. makeUtilityPayment Make an utility payment transaction Argument M/O Type Description cardNumber M S Card number cvv2 O L CVV2 of the card (for authorization) sourceAccountNumber O S Source account number utilityAccountNumber M S Utility account number amount O AmountDTO Transaction amount © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 102 of 210 provider M S Provider name. Examples: ESCOM – Escom DSTV – DSTV MRA – MRA channels O ChannelDTO List of channels. Only one channel is possible. Available only for MultiChoice provider period O S Table 89. Period parameter. Available only for MultiChoice provider MakeUtilityPayment request Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID utilityAccountNumber 20 O S Verified utility account number that has to be used into makeUtilityPayment message channels 0..n O ChannelDTO List of channels ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 90. MakeUtilityPayment response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 103 of 210 <soap:Body> <ns2:makeUtilityPayment xmlns:ns2="http://ws.webgate.bpc.ru/"> <makeUtilityPayment> <cardNumber>3434343434343434</cardNumber> <cvv2>999</cvv2> <utilityAccountNumber>1000100010001</utilityAccountNumber> <amount> <amount>1000</amount> <currency>454</currency> </amount> <provider>MRA</provider> <period>1</period> </makeUtilityPayment> </ns2:makeUtilityPayment> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:makeUtilityPaymentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>75432294</transactionId> </reply> </ns2:makeUtilityPaymentResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateUtilityPaymentResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR012</errorCode> <errorDescription>Utility payment failure</ errorDescription> </reply> </ns2:validateUtilityPaymentResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 104 of 210 </soap:Body> </soap:Envelope> 3.9. P2PTransfer Make a P2P transfer transaction Argument M/O Type Description cardNumber M S Source card number expiryDateCard O Date Expired date source card amountData M TransactionAmountDTO Transfer amount identificationData M IdentificationDataDTO Identification data merchant O Int Merchant ID pointServiceData O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED secondCardNumber M expiryDateSecondCard O S Destination card number Date Expired date second card P2PTransfer request Table 91. Argument Len M/O Type Description Status 1 S 0-Fail, 1- Success channels 0..n O ChannelDTO List of channels ErrorCode 10 S Error numeric code in case of request was not succeeded M O © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 105 of 210 internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded cardNumber - M S Source card number expiryDateCard - O Date Expired date source card processingCode - M S Processing code amountData - M TransactionAmountDTO Transaction amount identificationData - M IdentificationDataDTO Identification data Merchant - O Int Merchant ID pointServiceData - O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED responseCode - M S Response code expiryDateSecondCard - O Date Expired date second card Table 92. P2P transfer response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <user>wsuser</user> <pass>wspassword</pass> </soap:Header> <soap:Body> <ns2:p2pTransfer xmlns:ns2="http://ws.webgate.bpc.ru/"> <cardNumber>555555555555</cardNumber> <expiryDateCard>2020-09-01</expiryDateCard> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 106 of 210 <amountData> <amount>1000</amount> <currency>302</currency> </amountData> <identificationData> <transmissionDateTime>2019-0806T13:36:35.661+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T13:36:35.661+07:00</dateTimeLocalTransaction> <referenceNumber>1234</referenceNumber> </identificationData> <secondCardNumber>666666666666</secondCardNumber> </ns2:p2pTransfer> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:p2pTransferResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardNumber>555555555555</cardNumber> <processingCode>490000</processingCode> <amountData> <amount>1000</amount> <currency>302</currency> </amountData> <identificationData> <transmissionDateTime>1970-08-06T13:36:35+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T13:36:35+07:00</dateTimeLocalTransaction> <referenceNumber>1234</referenceNumber> </identificationData> <responseCode>00</responseCode> </reply> </ns2:p2pTransferResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 107 of 210 <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:p2pTransferResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR016</errorCode> <errorDescription> P2P transfer failure </ errorDescription> </reply> </ns2:p2pTransferResponse > </soap:Body> </soap:Envelope> 3.10. Validate card Make a validate card transaction Argument M/O Type Description cardNumber O S Card number expiryDate O Date Card expired date cardSeqNo O S Card sequence No track2 O S Card track 2 identificationData M IdentificationDataDTO Identification data pointServiceData PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: O MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED additionalData M ValidateCardAdditionalDataDTO Card additional data pinData O S PIN data Table 93. Validate card request Argument Len M/O Type Description Status 1 0-Fail, 1- Success M S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 108 of 210 channels 0..n O ChannelDTO List of channels ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded cardNumber - M S Card number expiryDate - O Date Expired date card cardSeqNo - O S Card sequence No track2 - O S Card track 2 processingCode - M S Processing code identificationData - M IdentificationDataDTO Identification data pointServiceData - O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED responseCode - M S additionalData - O ValidateCardAdditionalDataDTO Card additional data Table 94. Response code ValidateCard response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 109 of 210 <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateCard xmlns:ns2="http://ws.webgate.bpc.ru/"> <validateCard> <cardNumber>555555555555</cardNumber> <expiryDate>2020-09-01</expiryDate> <identificationData> <transmissionDateTime>2019-0806T14:08:23.117+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T14:08:23.117+07:00</dateTimeLocalTransaction> <referenceNumber>1234</referenceNumber> </identificationData> <additionalData> <hpanMask>hpanMark</hpanMask> <cardholderId>cardHolderId</cardholderId> </additionalData> </validateCard> </ns2:validateCard> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardNumber>555555555555</cardNumber> <processingCode>890000</processingCode> <identificationData> <transmissionDateTime>1970-08-06T14:08:23+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T14:08:23+07:00</dateTimeLocalTransaction> </identificationData> <responseCode>00</responseCode> <additionalData> <hpanMask>hpanMark</hpanMask> <cardholderId>cardHolderId</cardholderId> </additionalData> </reply> </ns2:validateCardResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 110 of 210 </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:validateCardResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR017</errorCode> <errorDescription> Validate card failure </ errorDescription> </reply> </ns2:validateCardResponse > </soap:Body> </soap:Envelope> 3.11. Card link The service is designed to link a certain card from a pool of cards with a cardholder at SVBO a certain card to the CBS account. The method supports following link types: The method supports following link types: 1)a new card for a new customer(account is not exist in SV). List of fields: ApplType = LKTPNECT, ExistCardNumber and ExistCardId fields are not needed in a request message. 2) a new card for an existing customer(account is exist in SV) when an old card is expired or in inactive status by any reason. List of fields: ApplType = LKTPEXCT, ExistCardNumber and ExistCardId fields are not needed in a request message. 3) a new main card for an existing customer(account is exist in SV) with old card blocking. List of fields: ApplType = LKTPEXOB, ExistCardNumber or ExistCardId field is required in a request message. 4) a supplementary card for an existing card and existing customer account. List of fields: ApplType = LKTPEXSC, ExistCardNumber or ExistCardId field is required in a request message. The service is developed only for SVFE KEF version. Argument Len M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 111 of 210 ApplType 8 M S Link operation type. Possible values: LKTPNECT - card for new customer LKTPEXCT - card for exist customer when the old card inactive LKTPEXOB - card for exist customer with the old card blocking LKTPEXSC - supplementary card for exist card and account CustomerNumber 200 M S Customer number(CBS) ProductId M S Product. Possible values: 8 Eg: 50000005 CardNumber 24 O S Linked Card Number CardId 24 M S Linked Card UID AccountNumber 32 M S Account number AccountCurrency 3 M S ISO currency code of the account Surname 200 M S Cardholder’s surname FirstName 200 M S Cardholder’s first name IdNumber 200 M S Cardholder’s ID number(passport number) CellPhone 16 M S Cardholder’s mobile phone number EmailAddress 100 O S Cardholder’s email address ExistCardNumber 24 O S Existing Card number ExistCardId 24 O S Existing Card UID InstantFlag 1 M B If ‘true’ special Instant Payment EMV application will be used UserId 50 M S UserId who initiated the request ChannelID 50 M S System name through which the request was originated: IB, CRM, IVR Table 95. CardLink request. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 112 of 210 Argument Len M/O Type Description Status 1 M S 0 - Fail, 1 - Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails O S Internal error code internalErrorCode 2 Table 96. CardLink response. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws.webgate.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <ws:cardLink> <cardLink> <applType>LKTPNECT</applType> <customerNumber>0000123456789</customerNumber> <productId>50000005</productId> <cardId>50076554372</cardId> <accountNumber>9911864516727</accountNumber> <surname>Wayne</surname> <firstName>Bruce</firstName> <cellPhone>88002008888</cellPhone> <existCardId>4891910012100015</existCardId> <instantFlag>true</instantFlag> <userId>admin</userId> <channelId>IOBUS</channelId> </cardLink> </ws:cardLink> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardLinkResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:cardLinkResponse> </soap:Body> </soap:Envelope> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 113 of 210 3.12. Service action Make a service action transaction Argument M/O Type Description cardNumber M S Card number expiryDate O Date Card expired date cardSeqNo O S Card sequence No track2 O S Card track 2 identificationData M IdentificationDataDTO Identification data pointServiceData PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: O MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED additionalData M ServiceActionAdditionalDataDTO Service additional data pinData O S PIN data actionCode M S Action: 1- Add service 2- Change service 3- Delete service accountId O S Account ID Service action request Table 97. Argument Len M/O Type Description Status 1 S 0-Fail, 1- Success channels 0..n O ChannelDTO List of channels M © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 114 of 210 ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded cardNumber - O S Card number expiryDate - O Date Expired date card cardSeqNo - O S Card sequence No track2 - O S Card track 2 processingCode - M S Processing code identificationData - M IdentificationDataDTO Identification data pointServiceData - O PointServiceDataCodeDTO Provider card mode, Authentication method. Examples: MANUAL, MAGNETIC_STRIPE_READ NOT_AUTHENTICATION, PIN, SIGNATURE_BASED responseCode - M S Response code accountId - O S Account ID Table 98. Service action response Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 115 of 210 <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:serviceAction xmlns:ns2="http://ws.webgate.bpc.ru/"> <serviceAction> <cardNumber>555555555555</cardNumber> <expiryDate>2020-09-01</expiryDate> <identificationData> <transmissionDateTime>2019-0806T14:39:33.457+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T14:39:33.457+07:00</dateTimeLocalTransaction> <referenceNumber>1234</referenceNumber> </identificationData> <additionalData> <phoneNumber>849887654</phoneNumber> <serviceType>3</serviceType> <cardholderIdInfo>cardHolderId</cardholderIdInfo> <serviceId>1</serviceId> <serviceObjectType>CARD</serviceObjectType> </additionalData> <pinData>pinData</pinData> <actionCode>1</actionCode> <accountId>1</accountId> </serviceAction> </ns2:serviceAction> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:serviceActionResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <cardNumber>555555555555</cardNumber> <expiryDate>2020-09-01</expiryDate> <processingCode>970000</processingCode> <identificationData> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 116 of 210 <transmissionDateTime>1970-0806T14:39:33+07:00</transmissionDateTime> <trace>1234</trace> <dateTimeLocalTransaction>2019-0806T14:39:33+07:00</dateTimeLocalTransaction> <referenceNumber>1234 </referenceNumber> </identificationData> <responseCode>00</responseCode> <accountId>[B@5c66d090</accountId> </reply> </ns2:serviceActionResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:serviceActionResponse xmlns:ns2="http://ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSR017</errorCode> <errorDescription> Validate card failure </ errorDescription> </reply> </ns2:serviceActionResponse > </soap:Body> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 117 of 210 Services This Web service designed for different service operation with SV entities. For more technical details see IService.wsdl in attachments. 3.13. EnrollCardCashbackPoint This WebService is designated to perform enrolling Card into CashBackPoint program in SVBO system. Argument Len M/O Type Description CardNumber 24 M S Card number Token 100 M S Token EnrollCardCashbackPoint request Table 99. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 100. EnrollCardCashbackPoint response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:svc="http://svc.svws.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <svc: enrollCardCashbackPoint> <request> <cardNumber>1234123412341234</cardNumber> <token>1111</token> </request> </svc: enrollCardCashbackPoint> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:enrollCardCashbackPoinResponse xmlns:ns2="http://svc.svws.bpc.ru/"> <reply> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 118 of 210 <status>1</status> </reply> </ns2: enrollCardCashbackPoinResponse> </soap:Body> </soap:Envelope> 3.14. UnlinkCardCashbackPoint This WebService is designated to perform unlink Card into CashBackPoint program in SVBO system. Argument Len M/O Type Description CardNumber 24 M S Card number Token 100 M S Token Unlink CardCashbackPoint request Table 101. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 102. UnlinkCardCashbackPoint response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:svc="http://svc.svws.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <svc: unlinkCardCashbackPoint> <request> <cardNumber>1234123412341234</cardNumber> <token>1111</token> </request> </svc: unlinkCardCashbackPoint> </soapenv:Body> </soapenv:Envelope> Response Sample: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 119 of 210 <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:unlinkCardCashbackPoinResponse xmlns:ns2="http://svc.svws.bpc.ru/"> <reply> <status>1</status> </reply> </ns2: unlinkCardCashbackPoinResponse> </soap:Body> </soap:Envelope> 3.15. EnrollMerchantCashbackPoint This WebService is designated to perform enrolling Merchant into CashBackPoint program in SVBO system. Argument Len M/O Type Description MerchantId 15 M S Table 103. Merchant Id EnrollMerchantCashbackPoint request Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 104. EnrollMerchantCashbackPoint response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:svc="http://svc.svws.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <svc: enrollMerchantCashbackPoint> <merchantId>000000000000007</merchantId> </svc: enrollMerchantCashbackPoint> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 120 of 210 <soap:Body> <ns2:enrollMerchantCashbackPoinResponse xmlns:ns2="http://svc.svws.bpc.ru/"> <reply> <status>1</status> </reply> </ns2: enrollMerchantCashbackPoinResponse> </soap:Body> </soap:Envelope> 3.16. UnlinkMerchantCashbackPoint This WebService is designated to perform unlink Merchant into CashBackPoint program in SVBO system. Argument Len M/O Type Description MerchantId 15 M S Merchant Id UnlinkMerchantCashbackPoint request Table 105. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error code, filled when request fails ErrorDescription 50 O S Error description, filled when request fails Table 106. UnlinkMerchantCashbackPoint response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:svc="http://svc.svws.bpc.ru/"> <soapenv:Header/> <soapenv:Body> <svc: unlinkMerchantCashbackPoint> <merchantId>000000000000007</merchantId> </svc: unlinkMerchantCashbackPoint> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 121 of 210 <ns2:unlinkMerchantCashbackPoinResponse xmlns:ns2="http://svc.svws.bpc.ru/"> <reply> <status>1</status> </reply> </ns2: unlinkMerchantCashbackPoinResponse> </soap:Body> </soap:Envelope> 7.4. USSD INTEGRATION WEB SERVICE This web service is designed to integrate SV with USSD applications, but that doesn’t restrict SVWG clients from using this web service with another applications. For more technical details see IUSSDGateway.wsdl in attachments. 1. RegisterCard Attach USSD service to card. The mobile phone number should be already assigned for this card into SVFE. Argument M/O Type Description cardNumber M S Card Number in clear text for which USSD service will be registered cellPhone M S Cell phone number expiryDate M date Card expire date (day part may always be 01, example 2019-04-01) Imsi M S International mobile subscriber identity RegisterCard request. Table 107. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 122 of 210 internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 108. RegisterCard response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:registerCardxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <registerCard> <cardNumber>4891910012100016</cardNumber> <cellPhone>88002008888</cellPhone> <expiryDate>2019-06-01</expiryDate> <imsi>4</imsi> </registerCard> </ussd:registerCard> </soapenv:Body> </soapenv:Envelope> Response sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:registerCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000159937</transactionId> </reply> </ns2:registerCardResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:registerCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 123 of 210 <reply> <status>0</status> <errorCode>WSU004</errorCode> <errorDescription>FE Card Registration error</errorDescription> </reply> </ns2:registerCardResponse> </soap:Body> </soap:Envelope> 2. AccountList Get the list of card account by USSD phone number. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone AccountList request. Table 109. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success accountList 0..n O AccountDTO List of accounts ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 110. AccountList response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 124 of 210 <soapenv:Body> <ussd:accountListxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <accountList> <cellPhone>0888892087</cellPhone> <imsi>1</imsi> </accountList> </ussd:accountList> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:accountListResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <accountList> <accountNumber>0101494004</accountNumber> <actualBalance> <amount>1.68567743E8</amount> <currency>454</currency> </actualBalance> </accountList> <accountList> <accountNumber>0127529992</accountNumber> <actualBalance> <amount>294236.0</amount> <currency>454</currency> </actualBalance> </accountList> <accountList> <accountNumber>5100288888</accountNumber> <actualBalance> <amount>-100000.0</amount> <currency>454</currency> </actualBalance> </accountList> </reply> </ns2:accountListResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 125 of 210 <ns2:accountListResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU016</errorCode> <errorDescription>USSD: Account list failure</errorDescription> </reply> </ns2: accountListResponse> </soap:Body> </soap:Envelope> 3. blockCard This message is used for blocking card. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) BlockCard request. Table 111. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 112. BlockCard response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 126 of 210 Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:blockCardxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <blockCard> <cellPhone>0888892087</cellPhone> <imsi>1</imsi>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  <cvv2>000</cvv2> </blockCard> </ussd:blockCard> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:blockCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000167528</transactionId> </reply> </ns2:blockCardResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:blockCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU014</errorCode> <errorDescription>USSD: Card block failure</errorDescription> </reply> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 127 of 210 </ns2:blockCardResponse> </soap:Body> </soap:Envelope> 4. unblockCard This message is used for unblocking card. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) UnblockCard request. Table 113. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 114. UnblockCard response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth=«http://ws.webgate.bpc.ru/»> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 128 of 210 <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:unblockCardxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <unblockCard> <cellPhone>0888892087</cellPhone> <imsi>1</imsi>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  <cvv2>000</cvv2> </unblockCard> </ussd:unblockCard> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:unblockCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000167528</transactionId> </reply> </ns2:unblockCardResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:unblockCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU020</errorCode> <errorDescription>USSD: Card unblock failure</errorDescription> </reply> </ns2:unblockCardResponse> </soap:Body> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 129 of 210 5. activateCard This message is used for activate card. Argument M/O Type Description cardNumber M S Card Number in clear text for which USSD service will be registered cellPhone M S Cell phone number expiryDate M date Card expire date (day part may always be 01, example 2019-04-01) Imsi M S International mobile subscriber identity ActivateCard request. Table 115. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 116. ActivateCard response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:activateCardxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <activateCard> <cardNumber>4891910012100016</cardNumber> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 130 of 210 <cellPhone>88002008888</cellPhone> <expiryDate>2019-06-01</expiryDate> <imsi>4</imsi> </activateCard> </ussd:activateCard> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:activateCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000167528</transactionId> </reply> </ns2:activateCardResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:activateCardResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU014</errorCode> <errorDescription>USSD: Card activation failure</errorDescription> </reply> </ns2:activateCardResponse> </soap:Body> </soap:Envelope> 6. pinChange PIN change message. SVFE supports only 2 variants of PINBlock format: - 01: ISO 9564-I & ANSI X9.8 format 0; - 03: Diebold & IBM ATM format. Argument M/O Type Description cellPhone M S Cell phone number © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 131 of 210 imsi M S International mobile subscriber identity of the source cell phone oldPinBlock M S PINBlock of old PIN value newPinBlock M S PINBlock of new PIN value PinChange request. Table 117. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 118. PinChange response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:pinChangexmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <pinChange> <cellPhone>0888892087</cellPhone> <imsi>1</imsi> <oldPinBlock>B6389499946CDD69</oldPinBlock> <newPinBlock>5CE0D60F30985842</newPinBlock> </pinChange> </ussd:pinChange> </soapenv:Body> </soapenv:Envelope> Response Sample: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 132 of 210 Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:pinChangeResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000164937</transactionId> </reply> </ns2:pinChangeResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:pinChangeResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU015</errorCode> <errorDescription>USSD: PIN Change failure</errorDescription> </reply> </ns2:pinChangeResponse> </soap:Body> </soap:Envelope> 7. makeTopup Make a mobile top-up transaction. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number destCellPhone M S Destination account number amount M AmountDTO Transaction amount © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 133 of 210 provider M S Provider name. Possible values: TNM – TNM TNM_POSTPAID – TNM Postpaid AIRTEL – Airtel AIRTEL_POSTPAID – AIRTEL Postpaid maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) MakeTopup request. Table 119. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 120. MakeTopup response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:makeTopupxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <makeTopup> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 134 of 210 <cellPhone>88002008888</cellPhone> <imsi>4</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <destCellPhone>1234567890</destCellPhone> <amount> <amount>1000</amount> <currency>840</currency> </amount> <provider>TNM</provider>  <sourceAccountNumber>5830072226</sourceAccountNumber>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  <cvv2>000</cvv2> </makeTopup> </ussd:makeTopup> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeTopupResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000164937</transactionId> </reply> </ns2:makeTopupResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeTopupResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU006</errorCode> <errorDescription>USSD: Mobile topup failure</errorDescription> </reply> </ns2:makeTopupResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 135 of 210 </soap:Body> </soap:Envelope> 8. validateUtilityPayment Verify customer data. This message has to be called before makeUtilityPayment for GOTV and DSTV provider. For other providers this message can be skipped. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone utilityAccountNumber M S Utility account number amount O AmountDTO Transaction amount provider M S Provider name. Possible values: /** Online **/ ESCOM – Escom DSTV – DSTV GOTV – GOTV /** Offline **/ BWB - Blantyre Water Board LCA - Lilongwe City Assembly NRWB - Northern Region Water Board SRWB - Southern Region Water Board ESCOM_POSTPAID - Escom Postpaid MTL – MTL MASM – MASM MRA – MRA BCA - BT && LL City Assembly Table 121. ValidateUtilityPayment request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 136 of 210 utilityAccountNumber 20 O S channels 0..n O ChannelDTO List of channels (for DSTV and GOTV only) ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 122. Verified utility account number that has to be used into makeUtilityPayment message ValidateUtilityPayment response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:validateUtilityPaymentxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <validateUtilityPayment> <cellPhone>88002008888</cellPhone> <imsi>4</imsi> <utilityAccountNumber>Utility12345</utilityAccountNumber> <amount> <amount>2000</amount> <currency>840</currency> </amount> <provider>ESCOM</provider> </validateUtilityPayment> </ussd:validateUtilityPayment> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 137 of 210 <soap:Body> <ns2:validateUtilityPaymentResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000203529</transactionId> <utilityAccountNumber>42842557</utilityAccountNumber> <channels> <id>ACSSKU</id> <description>DStv Access E</description> <amount> <amount>11.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>ADD2SEC</id> <description>Add2 Secondary Product</description> <amount> <amount>11.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>ASIA2PK</id> <description>DStv Indian South Premium Add E</description> <amount> <amount>20.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>ASIA3PK</id> <description>DStv Indian Combined Premium Add E</description> <amount> <amount>34.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>ASIAKU</id> <description>DStv Indian North E</description> <amount> <amount>35.0</amount> <currency>840</currency> </amount> </channels> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 138 of 210 <channels> <id>ASIAPK</id> <description>DStv Indian North Premium Add E</description> <amount> <amount>20.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>COFAMKU</id> <description>DStv Family Bouquet E</description> <amount> <amount>21.0</amount> <currency>840</currency> </amount> </channels> <channels> <id>COMPLKU</id> <description>DStv Compact Plus E</description> <amount> <amount>53.0</amount> <currency>840</currency> </amount> </channels> </reply> </ns2:validateUtilityPaymentResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:validateUtilityPaymentResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU007</errorCode> <errorDescription>USSD: Utility payment verification failure</errorDescription> </reply> </ns2:validateUtilityPaymentResponse> </soap:Body> </soap:Envelope> 9. makeUtilityPayment © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 139 of 210 Make an utility payment transaction. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number utilityAccountNumber M S Utility account number amount M AmountDTO Transaction amount provider M S Provider name. Possible values: /** Online **/ ESCOM – Escom DSTV – DSTV /** Offline **/ BWB - Blantyre Water Board LCA - Lilongwe City Assembly NRWB - Northern Region Water Board SRWB - Southern Region Water Board ESCOM_POSTPAID - Escom Postpaid MTL – MTL MASM – MASM MRA – MRA BCA - BT && LL City Assembly channels O ChannelDTO List of channels. Only one channel is possible. Mandatory for DSTV and GOTV providers. Table 123. MakeUtilityPayment request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 140 of 210 internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 124. MakeUtilityPayment response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:makeUtilityPaymentxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <makeUtilityPayment> <cellPhone>88002008888</cellPhone> <imsi>4</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <utilityAccountNumber>Utility12345</utilityAccountNumber> <amount> <amount>2000</amount> <currency>840</currency> </amount> <provider>ESCOM</provider> </makeUtilityPayment> </ussd:makeUtilityPayment> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeUtilityPaymentResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000166984</transactionId> </reply> </ns2:makeUtilityPaymentResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 141 of 210 </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeUtilityPaymentResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU007</errorCode> <errorDescription>USSD: Utility payment verification failure</errorDescription> </reply> </ns2:makeUtilityPaymentResponse> </soap:Body> </soap:Envelope> 10. cardToCardTransfer Card to card transfer. Source card will be found by phone number. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number receiverCardNumber M S Receiver card number amount M AmountDTO Transaction amount Table 125. CardToCardTransfer request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 142 of 210 internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 126. CardToCardTransfer response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:cardToCardTransferxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <cardToCardTransfer> <cellPhone>88002008888</cellPhone> <imsi>4</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <receiverCardNumber>5029440010103244</receiverCardNumber> <amount> <amount>5000</amount> <currency>840</currency> </amount> </cardToCardTransfer> </ussd:cardToCardTransfer> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardToCardTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000166923</transactionId> </reply> </ns2: cardToCardTransferResponse> </soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 143 of 210 </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardToCardTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU009</errorCode> <errorDescription>USSD: Card2Card failure</errorDescription> </reply> </ns2:cardToCardTransferResponse> </soap:Body> </soap:Envelope> 11. cardToAccountTransfer Card to account transfer. Source card will be found by phone number. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number receiverAccountNumber M S Receiver account number amount AmountDTO Transaction amount M Table 127. CardToAccountTransfer request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 144 of 210 ErrorDescription 50 Table 128. O S Error text description in case of request was not succeeded CardToAccountTransfer response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:cardToAccountTransferxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <cardToAccountTransfer> <cellPhone>88002008888</cellPhone> <imsi>4</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <receiverAccountNumber>0001102011111</receiverAccountNumber> <amount> <amount>3000</amount> <currency>840</currency> </amount> </cardToAccountTransfer> </ussd:cardToAccountTransfer> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardToAccountTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000167049</transactionId> </reply> </ns2:cardToAccountTransferResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 145 of 210 <soap:Body> <ns2:cardToAccountTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU010</errorCode> <errorDescription>USSD: Card2Account failure</errorDescription> </reply> </ns2:cardToAccountTransferResponse> </soap:Body> </soap:Envelope> 12. cardToAccountExternalTransfer Card to external account transfer. Source card will be found by phone number. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number externalAccountNumber M S Receiver external account number amount M AmountDTO Transaction amount Table 129. CardToAccountExternalTransfer request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 130. CardToAccountExternalTransfer response. Request Sample: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 146 of 210 <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:cardToAccountExternalTransferxmlns:ussd="http://ussd.ws.webgate.bpc .ru/"> <cardToAccountExternalTransfer> <cellPhone>88002008888</cellPhone> <imsi>4</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <externalAccountNumber>1234567890</externalAccountNumber> <amount> <amount>3000</amount> <currency>840</currency> </amount> </cardToAccountExternalTransfer> </ussd:cardToAccountExternalTransfer> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardToAccountExternalTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000167049</transactionId> </reply> </ns2:cardToAccountExternalTransferResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardToAccountExternalTransferResponsexmlns:ns2="http://ussd.ws.webga te.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU017</errorCode> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 147 of 210 <errorDescription>USSD: Card2Account External failure</errorDescription> </reply> </ns2:cardToAccountExternalTransferResponse> </soap:Body> </soap:Envelope> 13. nonCardAccountToAccountTransfer Non-card transfer request between accounts of different institutions within a single switch network. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccount M AccountDetailsDTO Source account details destAccount M AccountDetailsDTO Destination account details amount M AmountDTO Transaction amount NonCardAccountToAccountTransfer request. Table 131. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 132. NonCardAccountToAccountTransfer response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 148 of 210 <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:nonCardAccountToAccountTransfer xmlns:ns2="http://ussd.ws.webgate.bpc.ru/" xmlns:ns3="http://ws.webgate.bpc.ru/"> <nonCardAccountToAccountTransfer> <cellPhone>123456789</cellPhone> <imsi>1234</imsi> <sourceAccount> <instId>0001</instId> <accountNumber>41075123456</accountNumber> </sourceAccount> <destAccount> <instId>0002</instId> <accountNumber>521234234234</accountNumber> </destAccount> <amount> <amount>10000</amount> <currency>840</currency> </amount> </nonCardAccountToAccountTransfer> </ns2:nonCardAccountToAccountTransfer> </soap:Body> </soap:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>wsuser</user> <pass>wspassword</pass> </auth:credentials> </soap:Header> <soap:Body> <ns2:nonCardAccountToAccountTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/" xmlns:ns3="http://ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>555777</transactionId> </reply> </ns2:nonCardAccountToAccountTransferResponse> </soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 149 of 210 </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:nonCardAccountToAccountTransferResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU024</errorCode> <errorDescription>USSD: Non-card transfer failure</errorDescription> </reply> </ns2:nonCardAccountToAccountTransferResponse> </soap:Body> </soapenv:Envelope> 14. balanceInquiry Inquiry card balance according to phone number. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) BalanceInquiry request. Table 133. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success balance 12 O AmountDTO Actual card balance © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 150 of 210 ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 134. BalanceInquiry response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:balanceInquiryxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <balanceInquiry> <cellPhone>0882714310</cellPhone> <imsi>1234</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  <cvv2>000</cvv2> </balanceInquiry> </ussd:balanceInquiry> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:balanceInquiryResponsexmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <balance> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 151 of 210 <amount>23600.0</amount> <currency>454</currency> </balance> </reply> </ns2:balanceInquiryResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:balanceInquiryResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU011</errorCode> <errorDescription>USSD: Balance inquire failure</errorDescription> </reply> </ns2:balanceInquiryResponse> </soap:Body> </soap:Envelope> 15. miniStatement Inquiry card ministatement (up to 5 last transactions). Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) Table 135. Argument Len MiniStatement request. M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 152 of 210 Status 1 M S 0-Fail, 1- Success date 12 O DT Transaction date description 100 O S Transaction description amount 16 O L Transaction amount currency 3 O L ISO Currency Code desc 256 O S Transaction type description ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 136. MiniStatement response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:miniStatementxmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <miniStatement> <cellPhone>0882714310</cellPhone> <imsi>1234</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber>  <sourceAccountNumber>5830072226</sourceAccountNumber>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 153 of 210 <cvv2>000</cvv2> </miniStatement> </ussd:miniStatement> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:miniStatementResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactions> <date>2015-07-17T00:00:00</date> <description>- 000000</description> <amount>-6000</amount> <currency>454</currency> <desc>Cash withdrawal/advance</desc> </transactions> <transactions> <date>2015-07-16T00:00:00</date> <description>- 000000</description> <amount>-6000</amount> <currency>454</currency> <desc>Transfer To Foreign Account</desc> </transactions> </reply> </ns2:miniStatementResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:miniStatementResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU012</errorCode> <errorDescription>USSD: Mini statement failure</errorDescription> </reply> </ns2:miniStatementResponse> </soap:Body> </soap:Envelope> 16. cardlessRemmitance © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 154 of 210 Remittance of virtual card. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number withdrawalDueDate O date Withdrawal due date of virtual card amount M AmountDTO Transaction amount destCellPhone O S Destination mobile phone number that will receive the result of this transaction on success CardlessRemittance request. Table 137. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success amount - O AmountDTO Transaction amount transactionId 12 O S Transaction ID remittanceReferenceNumber 16 O S Remittance reference number withdrawalDueDate - O date Withdrawal due date of virtual card ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 138. CardlessRemittance response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 155 of 210 <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>ussd.user</user> <pass>ussd.pass1</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:cardlessRemittancexmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <cardlessRemittance> <cellPhone>0882714310</cellPhone> <imsi>1234</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <withdrawalDueDate>2019-06-01</withdrawalDueDate> <amount> <amount>1000</amount> <currency>454</currency> </amount> </cardlessRemittance> </ussd:cardlessRemittance> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardlessRemittanceResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <amount> <amount>1000.0</amount> <currency>454</currency> </amount> <transactionId>000002196685</transactionId> <remittanceReferenceNumber>109</remittanceReferenceNumber> <withdrawalDueDate>2019-06-01</withdrawalDueDate> </reply> </ns2:cardlessRemittanceResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 156 of 210 <ns2:cardlessRemittanceResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU013</errorCode> <errorDescription>USSD: Cardless Remittance failure</errorDescription> </reply> </ns2:cardlessRemittanceResponse> </soap:Body> </soapenv:Envelope> 17. changeCardLimit Changing card flexibale limit. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone newLimit M L Amount in the minimum fractions for the currency dateFrom O date Starting date of the limit. Should be after current time. dateTo O date End date of the limit audit O AuditDTO Optional field for audit purposes ChangeCardLimit request. Table 139. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 140. ChangeCardLimit response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 157 of 210 Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ussd="http://ussd.ws.webgate.bpc.ru/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ussd:changeCardLimit> <limit> <cellPhone>0882714310</cellPhone> <imsi>1234</imsi> <newLimit>100000</newLimit>  <dateFrom>2015-09-01</dateFrom>  <dateTo>2016-08-31</dateTo> </limit> </ussd:changeCardLimit> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardLimitResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> </reply> </ns2:changeCardLimitResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardLimitResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU021</errorCode> <errorDescription>USSD: Change card limit failure </errorDescription> </reply> </ns2:changeCardLimitResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 158 of 210 </soap:Body> </soapenv:Envelope> 18. chequeBookRequest Cheque book request. Argument M/O Type Description cellPhone M S Cell phone number imsi M S International mobile subscriber identity of the source cell phone sourceAccountNumber O S Source account number pages M I The amount of pages in Cheque book. Available values: 25, 50, 100. ChangeCardLimit request. Table 141. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 142. ChangeCardLimit response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 159 of 210 <ussd:changeCardLimit> <limit> <cellPhone>0882714310</cellPhone> <imsi>1234</imsi>  <sourceAccountNumber>5830072226</sourceAccountNumber> <pages>50</pages> </cardlessRemittance> </ussd:changeCardLimit> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardLimitResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000002196685</transactionId> </reply> </ns2:changeCardLimitResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:changeCardLimitResponse xmlns:ns2="http://ussd.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSU022</errorCode> <errorDescription>USSD: Cheque book request failure </errorDescription> </reply> </ns2:changeCardLimitResponse> </soap:Body> </soapenv:Envelope> 7.5. OTP INTEGRATION WEB SERVICE This Web service designed for generating an OTP and sending to customer. For more technical details see IOtpGateway.wsdl in attachments. 1. generateOtp Generate one time passcode (OTP) and sends to customer. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 160 of 210 Argument M/O Type Description cellPhone M S Cell phone number clientLocale O localeType Customer device locale Table 1. GenerateOtp request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success otpId - M L Actual one time passcode ID attemptsNumber - M I Actual number of OTP inputting attempts (unlimited if value is -1) ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 2. GenerateOtp response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <otp:generateOtpxmlns:otp="http://otp.ws.webgate.bpc.ru/"> <generateOtp> <cellPhone>0882714310</cellPhone> <clientLocale> <language>en</language> <country>gb</country> </clientLocale> </generateOtp> </otp:generateOtp> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 161 of 210 </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:generateOtpxmlns:ns2="http://otp.ws.webgate.bpc.ru/"> <reply> <status>1</status> <otpId>356</otpId> <attemptsNumber>3</attemptsNumber> </reply> </ns2:generateOtp> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:generateOtp xmlns:ns2="http://otp.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSO000</errorCode> <errorDescription> OTP: Generating one time passcode failure </errorDescription> </reply> </ns2:generateOtp> </soap:Body> </soap:Envelope> 7.6. IVR INTEGRATION WEB SERVICE This Web service designed for using IVR channel. For more technical details see IIvrGateway.wsdl in attachments. 1. balanceInquiry Inquiry card balance according to phone number. Argument M/O Type Description cellPhone M Cell phone number S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 162 of 210 maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) Table 3. BalanceInquiry request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success balance 12 O AmountDTO Actual card balance ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 4. BalanceInquiry response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <ivr:balanceInquiryxmlns:ivr="http://ivr.ws.webgate.bpc.ru/"> <balanceInquiry> <cellPhone>0882714310</cellPhone>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 163 of 210 <cvv2>000</cvv2> </balanceInquiry> </ivr:balanceInquiry> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:balanceInquiryResponsexmlns:ns2="http://ivr.ws.webgate.bpc.ru/"> <reply> <status>1</status> <balance> <amount>23600.0</amount> <currency>454</currency> </balance> </reply> </ns2:balanceInquiryResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:balanceInquiryResponse xmlns:ns2="http://ivr.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSI000</errorCode> <errorDescription>IVR: Balance inquire failure</errorDescription> </reply> </ns2:balanceInquiryResponse> </soap:Body> </soap:Envelope> 2. makeTopup Make a mobile top-up transaction. Argument M/O Type Description cellPhone M S Cell phone number destCellPhone M S Destination account number © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 164 of 210 amount M AmountDTO Transaction amount provider M S Provider name otpId O L One time passcode ID (If OTP service enabled) otpValue O S One time passcode value (If OTP service enabled) maskedCardNum O S Masked card number. Format is BIN (6 digits) + % + last 4 digits of card number, example 555555%1234 expiryDate O date Card expire date (day part may always be 01, example 2019-04-01) CVV2 O L CVV2 of the card (for authorization) Table 5. MakeTopup request. Argument Len M/O Type Description Status 1 M S 0-Fail, 1- Success transactionId 12 O S Transaction ID ErrorCode 10 O S Error numeric code in case of request was not succeeded internalErrorCode 2 O S Internal error code (ref Ошибка! Источник ссылки не найден.) ErrorDescription 50 O S Error text description in case of request was not succeeded Table 6. MakeTopup response. Request Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>username</user> <pass>password</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 165 of 210 <ivr:makeTopupxmlns:ivr="http://ivr.ws.webgate.bpc.ru/"> <makeTopup> <cellPhone>88002008888</cellPhone> <destCellPhone>88002008888</destCellPhone> <amount> <amount>1000</amount> <currency>840</currency> </amount> <provider>TNM</provider>  <otpId>10</otpId> <otpValue>qwerty</otpValue>  <maskedCardNum>555555%1234</maskedCardNum>  <expiryDate>2020-01-01</expiryDate>  <cvv2>000</cvv2> </makeTopup> </ivr:makeTopup> </soapenv:Body> </soapenv:Envelope> Response Sample: Success: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeTopupResponse xmlns:ns2="http://ivr.ws.webgate.bpc.ru/"> <reply> <status>1</status> <transactionId>000000164937</transactionId> </reply> </ns2:makeTopupResponse> </soap:Body> </soap:Envelope> Failure: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:makeTopupResponse xmlns:ns2="http://ivr.ws.webgate.bpc.ru/"> <reply> <status>0</status> <errorCode>WSI002</errorCode> <errorDescription>IVR: Wrong one time passcode</errorDescription> </reply> </ns2:makeTopupResponse> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 166 of 210 </soap:Body> </soap:Envelope> 7.7. SMSGATE WS INTERFACE SVWG provides a SOAP web service interface to send SMS messages using configured SMS gateways defined in SMS module section. In that case it acts as an adapter accepting SOAP message and transforming it to send to SMS service provider using different gateways: SMPP, GSM Modem, HTTP server, Web service. Send Sms request message Argument M/O Type Description phone M S Mobile phone number text M S Message text externalId O S External SMS id to trace in the system Table 7. Send SMS request Send Sms response message Argument M/O Type Description success M Result: true or false. Note: that is not delivery indication. True means a message has been accepted and queued for sending B Table 8. Send SMS response Request sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sms="http://www.bpc.ru/ufd/SMSGate/"> <soapenv:Header/> <soapenv:Body> <sms:sendSmsMessage> <message> <phone>1234567890</phone> <text>You one-time password: 123456</text> <externalId>1001</externalId> </message> </sms:sendSmsMessage> </soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 167 of 210 </soapenv:Envelope> 7.8. SV WS INTERFACE 1. Complex types Argument M/O Type Description contractId M L SVBO Contract ID, defines fees, commissions, etc. officerId M S SVBO Operator name who filled up application applicationId O S Application ID uniquely identifies card issuance process on all stages Table 9. MainBlock Argument M/O Type Description customerId M L ID for new or existing customer. If not specified will be generated automatically Document O DocumentBlock The list of customer’s documents Table 10. CustomerBlock Argument M/O Type Description docType M L Document type IDTP0=No ID IDTP1=Passport IDTP2=Driving license IDTP3=Social security IDTP4=Citizen ID IDTP5=VAT certificate of registration number M S Document number series O S Document series if exists authority O S Document authority if exists issDate O date Issuance date expDate O date Expiry date Table 11. DocumentBlock © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 168 of 210 Argument M/O Type Description firstName M L Person’s First Name surname M S Person’s Surname secondName O S Person’s Second name birthday O S Person’s birth day sex O date SEXT1=Male SEXT2=Female SEXT3=Transsexual © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 169 of 210 personStyle O personId O date STLE0=Mr. STLE1=Mrs. STLE2=Ms. STLE3=Sir STLE4=Lord STLE5=Right Honourable STLE6=Baron STLE7=Count STLE8=Miss STLE9=HE MR. STLE10=MESSERS STLE11=H.EX. STLE12=DR. STLE13=ENGINEER STLE14=JUDGE STLE15=SHEIKH STLE16=HER HIGHNESS STLE17=HIS HIGHNESS STLE18=HER R. HIGHNESS STLE19=HIS R. HIGHNESS STLE20=INHERITANCE STLE21=CHILD STLE22=HIS MAJESTY STLE23=LAWYER STLE24=MINOR STLE25=MR/S STLE26=ROYAL HIGHNESS STLE27=PROF.DR. STLE28=HER MAJESTY STLE29=AL-SHEIKHA STLE30=HIS EXCELLENCY ID for new or existing person. If not specified will be generated automatically Table 12. Argument PersonBlock M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 170 of 210 type M L Address type ADDR0=Company ADDR1=Private ADDR2=Government ADDR3=Delivery Address ADDR4=Statement Address ADDR5=Billing Address ADDR6=Address of registration ADDR7=Alternate ADDR8=Office ADDR9=PIN Delivery Address addrLine1 M S Address addrLine2 O S Address 2 addrLine3 O S Address 3 addrLine4 O S Address 4 country O L 3 digits ISO country code zipCode O S primaryPhone O S secondaryPhone O S mobilePhone O S email O S Valid email Table 13. AddressBlock Argument M/O Type Description cardType M S Type for new card cardNumber O S Will be generated automatically. Table 14. Argument M/O Type Description embossedName M S CardInitBlock Type for new card © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 171 of 210 companyName O S Will be generated automatically. expiryDate O date If not exists will be set automatically. Mandatory in response CardDataBlock Table 15. Argument M/O Type Description type M S Account type, if two digits is not set, like “ACCTD” then two digits will be generated automatically ACCTC=Generic Credit ACCTD=Generic Checking ACCTF=Generic Fee ACCTL=Generic Loan ACCTO=Generic Others ACCTS=Generic Savings ACCTW=Offline Wallet ACCTY=Generic Loyalty currency M L 3-digit ISO currency code number O S If set to “0”, then account number will be generated automatically Table 16. AccountInitBlock Argument M/O Type Description serviceId M S Attached service ID serviceLinkLevel M S Copied from the original request startDate M Date Copied from the original request endDate O Date Copied from the original request serviceActionFlag O S Copied from the original request serviceInstanceNumber O S Copied from the original request Table 17. ServiceDataBlock Argument M/O Type Description mobilePhone M S Table 18. Copied from the original request. Format: international number format without “+” SmsServiceBlock © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 172 of 210 Argument M/O Type Description src M L Card block ID in the request (starting from 0) target M L Account block ID in the request (starting from 0) Table 19. CardAccRefsBlock Argument M/O Type Description person O PersonBlock Person data adress O AddressBlock Address data Table 20. Argument M/O Type CardholderBlock Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 173 of 210 reissueCommand M S CRNW01=Name change replacement CRNW02=Damaged card replacement CRNW09=Automatic reissue CRNW11=Card Renewal request (old number,new expire date) CRNW12=Plastic Reissue - Cardholder request (old number,old expire date) CRNW13=Card Replacement - Cardholder request (new number, new/old expire date) CRNW14=Card Renewal request with old PIN CRNW15=Card Replacement - Card Lost or Stolen (new number,new expire date) CRNW16=Plastic Reissue without fee (old number,new expire date) CRNW17=Plastic Reissue without fee (old number,old expire date) CRNW18=Plastic Reissue without fee request (new number, new/old expire date) CRNW19=PIN Reissue CRNW20=Card Renewal request with old PIN without fee CRNW21=Card renewal blocking CRNW22=Card blocking by cardholder request CRNW23=PIN Reissue ( without fee ) CRNW24=Card Replacement - Card Lost (new number,new expire date) CRNW25=Card Replacement - Card Stolen (new number,new expire date) CRNW26=Lost/stolen card (new number,new expire date) without fee CRNW30=Specific Card Replacement CRNW31=Card chip unblocking (old number, old expire date, old pin) maskedCardNumber O S Masked card number of new card. cardType O S Card type of new card. expiryDate O Date Expiration date of new card. embossedName O S Embossed name of new card. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 174 of 210 CardReissueDataBlock Table 21. Argument M/O Type Description cardInit M CardInitBlock cardData M CardDataBlock CardBlock Table 22. Argument M/O Type Description cardInit M CardInitBlock cardData M CardDataBlock cardReissueData M CardReissueDataBlock CardReissueBlock Table 23. Argument M/O Type account M Description AccountInitBlock AccountBlock Table 24. Argument M/O Type serviceData O Description ServiceDataBlock AddServicesBlock Table 25. Argument M/O Type cardAccRefs O Description CardAccRefsBlock CardAccRefsBlock Table 26. 2. Instant Issue Service This Web service designed for instant issue processing in SV1. For more technical details see Issuing WSDLin attachments. 1. validateApplication The request to issue a new card. Argument Len M/O Type Description instId 4 Institution ID M S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 175 of 210 agent 4 M S Agent ID customerProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting cardholderProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting main - M MainBlock customer - O CustomerBlock cardholder - M CardholderBlock card - M CardBlock account - M AccountBlock addServices - O AddServicesBlock cardAccRefs - O CardAccRefs validateApplication request Table 27. Argument Len M/O Type Description instId 4 M S Institution ID agent 4 M S Agent ID customerProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 176 of 210 cardholderProcessingMode - M S main - M MainBlock customer - O CustomerBlock cardholder - M CardholderBlock card - M CardBlock account - M AccountBlock addServices - O AddServicesBlock cardAccRefs - O CardAccRefs Table 28. Create new customer or try use existing customer. Possible values: CreateNew UseExisting validateApplication response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>oeIoUEZGz4#</user> <pass>$3mhGuOk2DB</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <iss:validateApplicationReq> <instId>1101</instId> <agent>10</agent> <customerProcessingMode>CreateNew</customerProcessingMode> <cardholderProcessingMode>CreateNew</cardholderProcessingMode> <main> <contractId>10</contractId> <officerId>VISTA_JKB_SIT</officerId> </main> <cardholder> <person> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 177 of 210 <firstName>GAG</firstName> <surname>GAG</surname> </person> <adress> <type>ADDR1</type> <addrLine1>Gag Gag</addrLine1> </adress> </cardholder> <card> <cardInit> <cardType>M1</cardType> </cardInit> <cardData> <embossedName>GAGGAG</embossedName> </cardData> </card> <account> <acctInit> <type>ACCTD</type> <currency>840</currency> </acctInit> </account> </iss:validateApplicationReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:validateApplicationResp xmlns:ns2="http://www.bpc.ru/issuer"> <instId>1101</instId> <agent>10</agent> <customerProcessingMode>CreateNew</customerProcessingMode> <cardholderProcessingMode>CreateNew</cardholderProcessingMode> <main> <contractId>10</contractId> <officerId>VISTA_JKB_SIT</officerId> <applicationId>592628</applicationId> </main> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 178 of 210 <customer> <customerId>10038221</customerId> </customer> <cardholder> <person> <personId>10407839</personId> <firstName>GAG</firstName> <surname>GAG</surname> </person> <adress> <addressId>11114849</addressId> <type>ADDR1</type> <addrLine1>Gag Gag</addrLine1> </adress> </cardholder> <card> <cardInit> <cardType>M1</cardType> <maskedCardNumber>5513471110038769</maskedCardNumber> </cardInit> <cardData> <embossedName>GAGGAG</embossedName> <expiryDate>2020-01-01+03:00</expiryDate> </cardData> </card> <account> <acctInit> <type>ACCTD01</type> <currency>840</currency> <number>10038221201</number> </acctInit> </account> <cardAccRefs> <src>0</src> <target>0</target> </cardAccRefs> </ns2:validateApplicationResp> </soap:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 179 of 210 </soap:Envelope> 2. validateApplicationReissue Create BTRT20 application to reissue a card. Argument Len M/O Type Description instId 4 M S Institution ID agent 4 M S Agent ID customerProcessingMode - M S Possible values: UseExisting cardholderProcessingMode - M S Possible values: UseExisting main - M MainBlock customer - M CustomerBlock Person - O PersonBlock card - O CardReissueBlock Table 29. validateApplicationReissue request Argument Len M/O Type Description instId 4 M S Institution ID agent 4 M S Agent ID customerProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting cardholderProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting main M MainBlock - © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 180 of 210 customer - M CustomerBlock Person - O PersonBlock card - O CardReissueBlock Table 30. validateApplicationReissue response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>oeIoUEZGz4#</user> <pass>$3mhGuOk2DB</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <iss:validateApplicationReissueReq> <instId>1101</instId> <agent>10</agent> <customerProcessingMode>UseExisting</customerProcessingMode> <cardholderProcessingMode>UseExisting</cardholderProcessingMode> <main> <contractId>1</contractId> <officerId>VISTA_JKB_SIT</officerId> </main> <customer> <customerId>0290418</customerId> </customer> <person> <personId>0290418</personId> </person> <card> <cardInit> <cardType>V1</cardType> <maskedCardNumber>4790673029041803</maskedCardNumber> </cardInit> <cardReissueData> <reissueCommand>CRNW19</reissueCommand> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 181 of 210   <cardType>V1</cardType>  <embossedName>DUMMY2</embossedName> </cardReissueData> </card> </iss:validateApplicationReissueReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:validateApplicationReissueResp xmlns:ns2="http://www.bpc.ru/issuer"> <instId>1101</instId> <agent>10</agent> <customerProcessingMode>UseExisting</customerProcessingMode> <cardholderProcessingMode>UseExisting</cardholderProcessingMode> <main> <contractId>1</contractId> <officerId>VISTA_JKB_SIT</officerId> <applicationId>592636</applicationId> </main> <customer> <customerId>0290418</customerId> </customer> <person> <personId>0290418</personId> </person> <card> <cardInit> <cardType>V1</cardType> <maskedCardNumber>4790673029041803</maskedCardNumber> </cardInit> <cardReissueData> <reissueCommand>CRNW19</reissueCommand> <cardType>V1</cardType> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 182 of 210 <embossedName>DUMMY2</embossedName> </cardReissueData> </card> </ns2:validateApplicationReissueResp> </soap:Body> </soap:Envelope> 3. exportApplicationToPersoBureau Send card application data to SVCG system. Argument Len M/O Type Description applId 20 Application ID M S exportApplicationToPersoBureau request Table 31. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:exportApplicationToPersoBureauReq> <applId>592628</applId> </iss:exportApplicationToPersoBureauReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:exportApplicationToPersoBureauResp /> </soapenv:Body> </soapenv:Envelope> 4. prepareForIssue Prepare card issue in SVCG system. Argument Len M/O Type Description applId 20 Application ID M S © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 183 of 210 PrepareForIssue request Table 32. Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:prepareForIssueReq> <applId>592628</applId> </iss:prepareForIssueReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:prepareForIssueResp /> </soapenv:Body> </soapenv:Envelope> 5. cardWizard Provide an access to issued card data. Argument Len M/O Type Description applId 20 Application ID M Table 33. S CardWizard request Argument Len M/O Type Description applId 20 M S Apllication ID cardNum 20 M S Card number status 10 M S track1 50 M S Preparation status. “OK” for successfully prepared card Track1 Data track2 50 M S Track2 Data embossedData 30 M S Embossed String Data © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 184 of 210 chipData 50 O S Chip Data pinBlock 20 M S Pin Block Data contractId 8 M L Contract ID, defines fees, commissions, etc. corporateName 30 M S expDate - O date Table 34. Expiry date CardWizard response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:cardWizardReq> <applId>592628</applId> </iss:cardWizardReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:cardWizardResp xmlns:ns2="http://www.bpc.ru/issuer"> <applId>592661</applId> <card> <cardNum>5361220000474987</cardNum> <status>OK</status> <track1>%B5361220000474987^NAME/EMBOSS^1802226134818920000000000000000?</tr ack1> <track2>;5361220000474987=18022261348189200000?</track2> <embossedData>EMBOSS NAME</embossedData> <contractId>223</contractId> <corporateName/> <expDate>2018-02-28+03:00</expDate> </card> </ns2:cardWizardResp> </soap:Body> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 185 of 210 6. importCardToProcessingCenter Load issued card data from SVBO to SVFE systems. Argument Len M/O Type Description applId 20 M S Application ID pvv 4 O S Pin Verification Value pinOffset 12 O S Table 35. importCardToProcessingCenter request Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:importCardToProcessingCenterReq> <applId>592628</applId> </iss:importCardToProcessingCenterReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header/> <soapenv:Body> <iss:importCardToProcessingCenterResp /> </soapenv:Body> </soapenv:Envelope> 3. PIN Change Service This Web service designed for PIN change processing in SV1. For more technical details see PIN Change WSDLin attachments. 1. checkCardStatus Check card status in SmartVista and return it in response. Argument Len M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 186 of 210 cardNumber 20 M S Card Number expiryDate - M date Card Expiry Date checkCardStatus request Table 36. Argument Len M/O Type Description cardStatus 6 Card Status. Example: CSTS0 Table 37. O S checkCardStatus response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>oeIoUEZGz4#</user> <pass>$3mhGuOk2DB</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> <iss:checkCardStatusReq> <cardNumber>1234123412341234</cardNumber> <expiryDate>2020-11-04</expiryDate> </iss:checkCardStatusReq> </soapenv:Body> </soapenv:Envelope> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:checkCardStatusResp xmlns:ns2=http://www.bpc.ru/issuer> <cardStatus>CSTS0</cardStatus> </ns2:checkCardStatusResp> </soap:Body> </soap:Envelope> 2. updatePvv Update PIN value in SmartVista. Argument Len M/O Type Description © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 187 of 210 cardNumber 20 M S Card Number expiryDate - M date Card Expiry Date pvv - M S PVV/PIN Offset value Table 38. updatePvv request Argument Len M/O Type Description instId 4 M S Institution ID agent 4 M S Agent ID customerProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting cardholderProcessingMode - M S Create new customer or try use existing customer. Possible values: CreateNew UseExisting main - M MainBlock customer - M CustomerBlock Person - O PersonBlock card - O CardReissueBlock Table 39. updatePvv response Request Sample: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:iss="http://www.bpc.ru/issuer"> <soapenv:Header> <auth:credentials xmlns:auth="http://ws.webgate.bpc.ru/"> <user>oeIoUEZGz4#</user> <pass>$3mhGuOk2DB</pass> </auth:credentials> </soapenv:Header> <soapenv:Body> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 188 of 210 <iss:updatePvvReq> <cardNumber>1234123412341234</cardNumber> <expiryDate>2020-11-04</expiryDate> <pvv>BASD023lDLS312J</pvv> </iss:updatePvvReq> </soapenv:Body> Response Sample: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:updatePvvResp xmlns:ns2=http://www.bpc.ru/issuer /> </soap:Body> </soap:Envelope> © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 189 of 210 8. SMS BANKINGDOCUMENTATION Sms bank module is a multi-languagesolution for receiving SMS messages (text commands) using SMPP, GSM Modem, Web service channels, translating them to SV internal messages and execute several operations. Command templates are configured using text file. To use multi-language mode requirements below should be met:  Incoming SMS channel should support UTF-8 encoding messages transporting  JVM should be switched to UTF-8 file encoding. (-Dfile.encoding=utf-8 VM parameter see 4.1.2) The module provides a capability to setting up incoming command messages formats, success replies, failure replies, unknown failure replies in different languages. It is also possibleto set up different templates for the same command. A. MAIN CONFIGURATION SVWG has own configuration file bundled with the application. Default values are described in the table. Default configuration might be overridden by customizing files: ${WEBGATE_HOME}/conf/smsbank/smscommands.properties ${WEBGATE_HOME}/conf/smsbank/smstemplates.properties SMS Commands definition Properties starting with “placeholders.” define special aliases to parse client’s text command parts. These placeholders are used in command template strings that are matched with a client’s SMS command message. A list of placeholders is not fixed and new items might be added if required and then used in command templates. For instance “placeholders.card-number” property might be then used as expression %CARD:card-number% That means that the application will seek masked card number by “placeholders.cardnumber” property value expression, validate it and assign to CARD property. For more information about command templates please refer SMS templates Properties starting with “replacer.” introduce placeholders to be used by the application itself while creating response text to a client. List is also not fixed. For instance %DATE:date-timestamp% means that DATE variable (it might be a transactions date, or expiry date and etc. It depends on command’s context) will be formatted using © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 190 of 210 “replacer.date-timestamp” property timestamp%” string by result value value expression and replace Properties starting with “commands.”introduce reply smstemplates.properties) in case of different processing errors. “%DATE:date- message keys (in template key Properties starting with “txtcommand.”introduce available text commands. The template to define a new command is: txtcommand.<command name>.type=<command type> txtcommand.<command name>.template=<command template key> txtcommand.<command name>.reply=<successful reply template key> txtcommand.<command with a reason> name>.reply-error-reason=<failure reply txtcommand.<command name>.reply-error-noreason=<failure reply template key without any reason> Note command types are fixed and might be one of Please refer to SMS templatesfor commands details. All available commands are enabled by default. See commands declaration below: txtcommand.balance.type=CARD_BALANCE_INQUIRY txtcommand.balance.template=txtcommand.balance_inquiry txtcommand.balance.reply=txtcommand.balance_inquiry_reply txtcommand.balance.reply-errorreason=txtcommand.balance_inquiry_reply_error_reason txtcommand.balance.reply-errornoreason=txtcommand.balance_inquiry_reply_error_noreason txtcommand.status.type=CARD_STATUS_INQUIRY txtcommand.status.template=txtcommand.status_inquiry txtcommand.status.reply=txtcommand.status_inquiry_reply txtcommand.status.reply-errorreason=txtcommand.status_inquiry_reply_error_reason txtcommand.status.reply-errornoreason=txtcommand.status_inquiry_reply_error_noreason txtcommand.mini_statement.type=CARD_MINI_STATEMENT txtcommand.mini_statement.template=txtcommand.mini-statement txtcommand.mini_statement.reply=txtcommand.mini-statement_reply © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 191 of 210 txtcommand.mini_statement.reply-error-reason=txtcommand.ministatement_reply_error_reason txtcommand.mini_statement.reply-error-noreason=txtcommand.ministatement_reply_error_noreason txtcommand.activate_service.type=SMS_SERVICE_ACTIVATION txtcommand.activate_service.template=txtcommand.service-activation txtcommand.activate_service.reply=txtcommand.service-activation_reply txtcommand.activate_service.reply-error-reason=txtcommand.serviceactivation_reply_error_reason txtcommand.activate_service.reply-error-noreason=txtcommand.serviceactivation_reply_error_noreason txtcommand.deactivate_service.type=SMS_SERVICE_DEACTIVATION txtcommand.deactivate_service.template=txtcommand.service-deactivation txtcommand.deactivate_service.reply=txtcommand.service-deactivation_reply txtcommand.deactivate_service.reply-error-reason=txtcommand.servicedeactivation_reply_error_reason txtcommand.deactivate_service.reply-error-noreason=txtcommand.servicedeactivation_reply_error_noreason txtcommand.block_card.type=CARD_BLOCK txtcommand.block_card.template=txtcommand.card_block txtcommand.block_card.reply=txtcommand.card_block_reply txtcommand.block_card.reply-errorreason=txtcommand.card_block_reply_error_reason txtcommand.block_card.reply-errornoreason=txtcommand.card_block_reply_error_noreason txtcommand.unblock_card.type=CARD_UNBLOCK txtcommand.unblock_card.template=txtcommand.card_unblock txtcommand.unblock_card.reply=txtcommand.card_unblock_reply txtcommand.unblock_card.reply-errorreason=txtcommand.card_unblock_reply_error_reason txtcommand.unblock_card.reply-errornoreason=txtcommand.card_unblock_reply_error_noreason txtcommand.issue_virtual_card.type=CARDLESS_REMITTANCE txtcommand.issue_virtual_card.template=txtcommand.issue_virtual_card txtcommand.issue_virtual_card.reply=txtcommand.issue_virtual_card_reply txtcommand.issue_virtual_card.reply-errorreason=txtcommand.issue_virtual_card_reply_error_reason © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 192 of 210 txtcommand.issue_virtual_card.reply-errornoreason=txtcommand.issue_virtual_card_reply_error_noreason txtcommand.card_to_card_transfer.type=CARD_TO_CARD_TRANSFER txtcommand.card_to_card_transfer.template=txtcommand.card_to_card_transfer txtcommand.card_to_card_transfer.reply=txtcommand.card_to_card_transfer_rep ly txtcommand.card_to_card_transfer.reply-errorreason=txtcommand.card_to_card_transfer_reply_error_reason txtcommand.card_to_card_transfer.reply-errornoreason=txtcommand.card_to_card_transfer_reply_error_noreason txtcommand.payment.type=PAYMENT txtcommand.payment.template=txtcommand.payment txtcommand.payment.reply=txtcommand.payment_reply txtcommand.payment.reply-error-reason=txtcommand.payment_reply_error_reason txtcommand.payment.reply-errornoreason=txtcommand.payment_reply_error_noreason txtcommand.payment_saved.type=SAVED_PAYMENT txtcommand.payment_saved.template=txtcommand.saved_payment txtcommand.payment_saved.reply=txtcommand.saved_payment_reply txtcommand.payment_saved.reply-errorreason=txtcommand.saved_payment_reply_error_reason txtcommand.payment_saved.reply-errornoreason=txtcommand.saved_payment_reply_error_noreason smscommands.properties default values Property name Default value Descriprion supported-locales en ISO-639 language code to be used while parsing text commands placeholder.amount (\\\\d+(?:\\\\.\\\\d{1,3})?) Amount regexp, allows records like 100, 100.1, 100.01, 100.101 placeholder.amount-opt (\\\\d+(?:\\\\.\\\\d{1,3})?) ? optional amount regexp placeholder.amount-nodecimal (\\\\d+) Amount without fractions © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 193 of 210 placeholder.mobilenumber (\\\\+\\\\d{11}) mobile number in international forma, i.e. +10912121128 placeholder.mobilenumber-short (\\\\d{8}) Short mobile number i.e. local phone numbers: 9268967900 placeholder.card-numbermasked (\\\\d{4}\\\\*\\\\d{4}) masked card number i.e. 1234*6789 placeholder. card-number (\\\\d{16,19}) full card number with length of 16-19 examples 1234567890123456, 1234567890123456789 placeholder.currencysymbolic ([a-zA-Z]{3}) iso-4217 3 character code i.e. USD placeholder.currencysymbolic-opt ([a-zA-Z]{3})? optional iso-4217 3 character code i.e. USD or empty placeholder.date ([0123]?\\\\d{1}\\\\[01]?\\\\d{1}\\\\-\\\\d{4}) Date in format dd-MM-yyyy placeholder.expire-date ([01]{1}\\\\d{1}\\\\d{2}) Card expiry date in format MMyy i.e. 1216 placeholder.service-id (\\\\w+) Service id (payments) any word. i.e. 508 or MOBILE and etc. placeholder.paymentparameters ([\\\\w\\\\\\\\+,\\\\|\\\\=\\\\!@%\\ \\*\\\\<\\\\>;/]+)? Optional flexible payment parameters as one string delimited by semiocolon i.e. payer=JohnDoe;period=January placeholder.payment-id (\\\\w+) payment id (when payment template is registered in SV system) any word i.e. 105 or MyPaymentId placeholder.SPACE (?:\\\\s+) technical placeholder. Used to control spaces in commands: one or more spaces or new line characters i.e. 24.08.2016 © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 194 of 210 placeholder.SPACE-OPT (?:\\\\s*) technical placeholder. Used to control optional spaces in commands: zero, one or more spaces or new lines characters replacer.date-day-seconds dd.MM HH:mm date format i.e. 24.08 15:31 (24 August 3:31 pm) replacer.date-timestamp dd.MM.yyyy HH:mm:ss date format i.e. 24.08.2016 15:31:55 (24 August 2016 3:31:55 pm) replacer.date dd.MM.yyyy date format i.e. 24.08.2016 (24 August 2016) commands.wrong_comma txtcommand.wrong_com nd_reply mand_reply Reply message key to be sent if user command is not recognized commands.wrong_field_f ormat_reply txtcommand.wrong_field_ format_reply Reply message key to be sent if user provided incorrect data in a field commands.unknown_erro r txtcommand.unknown_er ror Reply message key to be sent if unrecognized error has occurred while processing a command commands.success_but_r esponse commands.success_but_r esponse Reply message key to be sent if command had been successfully processed (payment executed) but an error occurred while creating response message Table 40. SMS commands properties © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 195 of 210 SMS Templates definition SVWG matches commands templates in Case-Insensitive mode. All incoming/outgoing (request/reply) message templates are smstemplates.properties. This localization file contains English templates. defined in To add a new localization file with templates in other language add new file smstemplates_<lang>.properties file to the same directory where <lang> is ISO-639 2 character language code (French - smstemplates_fr.properties, Arabic smstemplates_ar.properties) and add a locale name to “supported-locales” property described in table (i.e. supported-locales=en,fr,ar).Note that SVWG application restart is required. In case when multiple language support is enabled SMS Bank module will attempt to match a client’s message to command templates in each language. Reply message language is the same as matched command language. Translations for all message keys should be provided in each existing localization file. Common messages: txtcommand.wrong_command_reply = Command is not correct. Please check allowed command list The reply message in case when user command is not recognized txtcommand.wrong_field_format_reply = {0} does not match allowed format {1} Reply message in case when some field didn’t match it’s format (date,card number, mobile number and etc). Here {0} will be replaced with field name and {1} with field format. txtcommand.unknown_error = Command failure. Please contact administrators or try later Reply on unknown processing error txtcommand.success_but_response = Command successful, but response not created Reply message in case when a command was successfully processed, but an error has occurred while creating the response. © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 196 of 210 B. CARD BALANCE ENQUIRY Command returns card’s balance. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.balance_inquiry = Balance|SPACE|%CARD_MASK:card-number-masked% txtcommand.balance_inquiry_reply = Card: %CARD_MASK:%, %DATE:datetimestamp% Balance: %AMT:% %CURR:% txtcommand.balance_inquiry_reply_error_reason = Card: %CARD_MASK:%, %DATE:date-timestamp% Balance Error: %ERROR:% txtcommand.balance_inquiry_reply_error_noreason = Card: %CARD_MASK:%, %DATE:date-timestamp% Balance Failure Description: Text command structure:  “Balance” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number- %CARD_MASK:card-number-masked% (see cardnumber-masked placeholder) Request sample: Balance 5381*1234 Success reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Balance: 15812.00 USD Failure reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Balance Error: Wrong card Unknown error reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Balance Failure C. CARD STATUS ENQUIRY Command returns card status. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.status_inquiry = Status|SPACE|%CARD_MASK:card-number-masked% txtcommand.status_inquiry_reply = Card: %CARD_MASK:%, %DATE:date-timestamp% Balance: %AMT:% %CURR:%, Status: %PARAMS:% © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 197 of 210 txtcommand.status_inquiry_reply_error_reason = Card: %CARD_MASK:%, %DATE:date-timestamp% Status Error: %ERROR:% txtcommand.status_inquiry_reply_error_noreason = Card: %CARD_MASK:%, %DATE:date-timestamp% Status Failure Description: Text command structure:  “Status” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (see cardnumber-masked placeholder) Request sample: Status 5381*1234 Success reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Balance: 15812.00 USD, Status: Active Failure reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Status Error: Wrong card Unknown error reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Status Failure D. MINI-STATEMENT Command returns a list of latest transactions short descriptions. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.mini-statement = Statement|SPACE|%CARD_MASK:card-number-masked% txtcommand.mini-statement_reply = Card: %CARD_MASK:%, %DATE:date-timestamp% Transactions:%REPEAT:<|NEWLINE|%DATE:date-day-seconds% %SIGN:% %AMT:% %CURR:% %AUTH_ID:% %PLACE:%>% txtcommand.mini-statement_reply_error_reason = Card: %CARD_MASK:%, %DATE:date-timestamp% Ministatement Error: %ERROR:% txtcommand.mini-statement_reply_error_noreason = Card: %CARD_MASK:%, %DATE:date-timestamp% Ministatement Failure Description: Text command structure:  “Statement” word © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 198 of 210  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (see cardnumber-masked placeholder) Request sample: Statement 5381*1234 Success reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Transactions: 12.08 15:31 - 1.50 USD 274124 Coffee House 12.08 15:35 - 25.87 USD 274138 Auchan Moll Failure reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Ministatement Error: Wrong card Unknown error reply sample: Card: 5381*1234, 24.08.2016 18:21:15 Ministatement Failure E. SERVICE ACTIVATION Activates SMS service for a card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.service-activation = Activate|SPACE|SMS|SPACE|%CARD_MASK:cardnumber-masked% txtcommand.service-activation_reply = Card %CARD_MASK:% %DATE:datetimestamp% SMS service Activated txtcommand.service-activation_reply_error_reason = Card %CARD_MASK:% %DATE:date-timestamp% SMS Activation Error: %ERROR:% txtcommand.service-activation_reply_error_noreason = Card %CARD_MASK:% %DATE:date-timestamp% SMS Activation Failure Description: Text command structure:  “Activate” word  Space character - |SPACE| (see SPACE placeholder definition)  “SMS” word  Space character - |SPACE| (see SPACE placeholder definition) © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 199 of 210  client masked card number number-masked placeholder) - %CARD_MASK:card-number-masked% (see card- Request sample: Activate SMS 5381*1234 Success reply sample: Card5381*1234 24.08.2016 18:21:15 SMS Service Activated Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 SMS Activation Error: Wrong card Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 SMS ActivationFailure F. SERVICE DEACTIVATION Deactivates SMS service for a card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.service-deactivation = Deactivate|SPACE|SMS|SPACE|%CARD_MASK:card-number-masked% txtcommand.service-deactivation_reply = Card %CARD_MASK:% %DATE:datetimestamp% SMS Service Deactivated txtcommand.service-deactivation_reply_error_reason = Card %CARD_MASK:% %DATE:date-timestamp% SMS Deactivation Error: %ERROR:% txtcommand.service-deactivation_reply_error_noreason = Card %CARD_MASK:% %DATE:date-timestamp% SMS Deactivation Failure Description: Text command structure:  “Deactivate” word  Space character - |SPACE| (see SPACE placeholder definition)  “SMS” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number number-masked placeholder) - %CARD_MASK:card-number-masked% (see card- Request sample: Deactivate SMS 5381*1234 Success reply sample: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 200 of 210 Card5381*1234 24.08.2016 18:21:15 SMS Service Deactivated Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 SMS Deactivation Error: Wrong card Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 SMS Deactivation Failure G. BLOCK CARD Blocks a card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.card_block = Block|SPACE|%CARD_MASK:card-number-masked% txtcommand.card_block_reply successfully blocked = Card %CARD_MASK:% txtcommand.card_block_reply_error_reason timestamp% Block Error: %ERROR:% = Card %DATE:date-timestamp% %CARD_MASK:% %DATE:date- txtcommand.card_block_reply_error_noreason = Card %CARD_MASK:% %DATE:datetimestamp% Block Failure Description: Text command structure:  “Block” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (see cardnumber-masked placeholder) Request sample: Block 5381*1234 Success reply sample: Card5381*1234 24.08.2016 18:21:15 successfully blocked Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Block Error: Wrong card Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Block Failure H. UNBLOCK CARD © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 201 of 210 Blocks a card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.card_block = Unblock|SPACE|%CARD_MASK:card-number-masked% txtcommand.card_block_reply successfully unblocked = Card %CARD_MASK:% txtcommand.card_block_reply_error_reason timestamp% Unblock Error: %ERROR:% = Card %DATE:date-timestamp% %CARD_MASK:% %DATE:date- txtcommand.card_block_reply_error_noreason = Card %CARD_MASK:% %DATE:datetimestamp% Unblock Failure Description: Text command structure:  “Unblock” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (see cardnumber-masked placeholder) Request sample: Unblock 5381*1234 Success reply sample: Card5381*1234 24.08.2016 18:21:15 successfully unblocked Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Unblock Error: Wrong card Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Unblock Failure I. CREATE VIRTUAL CARD Create a new virtual card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.issue_virtual_card = Virtual|SPACE|%CARD_MASK:card-numbermasked%|SPACE|%AMT:amount%|SPACE-OPT|%CURR:currency-symbolicopt%|SPACE|%EXPIRY:expire-date% txtcommand.issue_virtual_card_reply = Card %CARD_MASK:% %DATE:datetimestamp% Virtual remittance %AMT:% %CURR:% Exp. %EXPIRY:expire-date% successful © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 202 of 210 txtcommand.issue_virtual_card_reply_error_reason = Card %CARD_MASK:% %DATE:date-timestamp% Virtual Card Error: %ERROR:% txtcommand.issue_virtual_card_reply_error_noreason = Card %CARD_MASK:% %DATE:date-timestamp% Virtual Failure Description: Text command structure:  “Virtual” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (source card number) (see card-number-masked placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  amount - balance of new virtual card - %AMT:amount% (seeamount placeholder)  Optional space character (exist when currency is provided) - |SPACE-OPT| (see SPACE-OPT placeholder definition)  Optional currency of new virtual card - %CURR:currency-symbolic-opt% (see currency-symbolic-optplaceholder). If currency is not provided then source card’s currency will be chosen.  Space character - |SPACE| (see SPACE placeholder definition)  New virtual card expiration - %EXPIRY:expire-date% (see expire-date placeholder) Request sample: Virtual 5381*1234 1000.50 USD 1216 Success reply sample: Card5381*1234 24.08.2016 18:21:15 Virtual remittance 1000.50 USD Exp. 1216 successful Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Virtual Card Error: Insufficient funds Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Virtual Failure J. CARD TO CARD TRANSFER Perform card to card transfer. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 203 of 210 txtcommand.card_to_card_transfer = Transfer|SPACE|%CARD_MASK:card-numbermasked%|SPACE|%CARD:card-number%|SPACE|%EXPIRY:expiredate%|SPACE|%AMT:amount%|SPACE-OPT|%CURR:currency-symbolic-opt% txtcommand.card_to_card_transfer_reply = Card %CARD_MASK:% %DATE:datetimestamp% Transfer %AMT:% %CURR:% to %CARD:% successful txtcommand.card_to_card_transfer_reply_error_reason = Card %CARD_MASK:% %DATE:date-timestamp% Transfer Error: %ERROR:% txtcommand.card_to_card_transfer_reply_error_noreason = Card %CARD_MASK:% %DATE:date-timestamp% Transfer Failure Description: Text command structure:  “Transfer” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (source card number see card-number-masked placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  credited card full number - %CARD:card-number% (see card-numberplaceholder)  Space character - |SPACE| (see SPACE placeholder definition)  Source card expiration date (for identification purposes)- %EXPIRY:expire-date% (see expire-date placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  transfer amount- %AMT:amount% (seeamount placeholder)  Optional space character (exist when currency is provided) - |SPACE-OPT| (see SPACE-OPT placeholder definition)  Optional currency of transfer - %CURR:currency-symbolic-opt% (see currencysymbolic-opt placeholder). If currency is not provided then source card’s currency will be chosen. Request sample: Transfer 5381*12345381234567891234 1216 1000.50 USD Success reply sample: Card5381*1234 24.08.2016 18:21:15 Transfer 1000.50 USD to 5381234567891234 successful Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Transfer Error: Insufficient funds Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Transfer Failure © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 204 of 210 K. PAYMENT Perform a payment from a card. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.payment = Payment|SPACE|%CARD_MASK:card-numbermasked%|SPACE|%SERVICE:service-id%|SPACE|%AMT:amount%|SPACEOPT|%CURR:currency-symbolic-opt%|SPACE-OPT|%PARAMS:payment-parameters% txtcommand.payment_reply = Card %CARD_MASK:% %DATE:date-timestamp% Payment %AMT:% %CURR:% with service %SERVICE:% and parameters: %PARAMS:% successful txtcommand.payment_reply_error_reason = Card %CARD_MASK:% %DATE:datetimestamp% Payment Error: %ERROR:% txtcommand.payment_reply_error_noreason = Card %CARD_MASK:% %DATE:datetimestamp% Payment Failure Description: Text command structure:  “Payment” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (source card number see card-number-masked placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  payment service id - %SERVICE:service-id% (see service-id placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  payment amount- %AMT:amount% (seeamount placeholder)  Optional space character (exist when currency is provided) - |SPACE-OPT| (see SPACE-OPT placeholder definition)  Optional payment currency - %CURR:currency-symbolic-opt% (see currencysymbolic-opt placeholder). If currency is not provided then source card’s currency will be chosen.  Optional space character (exist when additional parameters are provided) - |SPACEOPT| (see SPACE-OPT placeholder definition)  payment parameters- %PARAMS:payment-parameters% (see payment-parameters placeholder) Request sample: Payment 5381*1234Electricity 10 meter=10012341;value=6451.24 Success reply sample: Card5381*1234 24.08.2016 18:21:15 Payment 10.00 USDwith service Electricity and parametersmeter=10012341;value=6451.24 successful © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 205 of 210 Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Payment Error: Unknown service id Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Payment Failure L. PAYMENT BY TEMPLATE Perform a payment by template registered in the system. See command definition to be provided in smscommands.properties. For placeholders details refer to SMS commands properties table. Template configuration: txtcommand.saved_payment = SPayment|SPACE|%CARD_MASK:card-numbermasked%|SPACE|%PAYMENT:payment-id%|SPACE-OPT|%AMT:amount-opt%|SPACEOPT|%CURR:currency-symbolic-opt% txtcommand.saved_payment_reply = Card %CARD_MASK:% %DATE:date-timestamp% Payment with template %PAYMENT:% successful txtcommand.saved_payment_reply_error_reason = Card %CARD_MASK:% %DATE:datetimestamp% Template Payment Error: %ERROR:% txtcommand.saved_payment_reply_error_noreason = Card %CARD_MASK:% %DATE:date-timestamp% Template Payment Failure Description: Text command structure:  “SPayment” word  Space character - |SPACE| (see SPACE placeholder definition)  client masked card number - %CARD_MASK:card-number-masked% (source card number see card-number-masked placeholder)  Space character - |SPACE| (see SPACE placeholder definition)  payment template id - %PAYMENT:payment-id% (see payment-id placeholder)  Optional space character (exist when payment amount exists) - |SPACE-OPT| (see SPACE-OPT placeholder definition)  optional payment amount- %AMT:amount-opt% (may be present if it is not defined in the template or to override template amount,seeamount-opt placeholder)  Optional space character (exists when currency is provided) - |SPACE-OPT| (see SPACE-OPT placeholder definition)  Optional payment currency - %CURR:currency-symbolic-opt% (see currencysymbolic-opt placeholder). If currency is not provided then source card’s currency will be chosen. Request sample: SPyment 5381*1234MyTemplateId5.87USD © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 206 of 210 Success reply sample: Card5381*1234 24.08.2016 18:21:15 Payment with template MyTemplateId successful Failure reply sample: Card 5381*1234 24.08.2016 18:21:15 Template Payment Error:Unknown template id Unknown error reply sample: Card 5381*1234 24.08.2016 18:21:15 Template Payment Failure © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 207 of 210 9. SMARTVISTA2 DOCUMENTATION SmartIVtsa2 web services are designed to integrate SVWG with SmartVista2 via SV2 protocols SVIS and SVAP. For more technical details see attachments for SVIS and SVAP web services. Documentation for SVIS web service is attached in the next file IntegrationServices_eng.zip © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 208 of 210 10. ATTACHMENTS SVWG schema installation.zip 1. SVWG DB 2. Certs certs.zip 3. ICardWSDL iCard.wsdl 4. ITransaction WSDL ITransaction.wsdl 5. IVirtualIssuing WSDL IUssdGateway.wsdl 6. IUSSD WSDL 7. IService WSDL IService.wsdl svap_iss.wsdl 8. SVAP WSDL 9. SVIS WSDL IVirtualIssuing.wsld info.wsdl 10. Issuing WSDL svap_iss.xsd info_info.xsd IssuerService.wsdl 11. PIN Change WSD pinws.wsdl IOtpGateway.wsdl 12. IOTPGateway WSDL © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 209 of 210 IIvrGateway.wsdl 13. IIvrGateway WSDL 14. MVisa WSDL middleware.wsdl middleware-excepti middleware-entity.x on.xsd sd © 2019 BPC Banking Technologies. Proprietary and Confidential. Page 210 of 210

SmartVista Webgate Product Documentation installation

Products

Support

SmartVista Webgate Product Documentation installation

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib