Micropayment Version: 01 Last version: June 3, 2013 Page 1 of 28 All rights reserved, proprietary information
Project ID No: Table of Contents Proprietary Notice 4 DOCUMENT CONTROL SECTION 5 Version History 5 Definition, acronyms and abbreviations 5 1 Introduction 6 2 System Overview 6 3 PIMS Micropayment User Interface 6 Login 7 Main Menu 8 Merchants 8 Services 10 4 PIMS Micropayment API 12 DirectPayment 12 InstalmentPayment 14 Reservation 16 ReservationCancel 18 CheckCredit 19 8 Error Codes 21 AVEA Page 2 of 28 Valid agreement required
Project ID No: PIMS Page 3 of 28 Valid agreement required
Project ID No: Proprietary Notice AVEA Software makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of the merchantability and fitness for a particular purpose AVEA Software shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material The copyright in this work is vested in AVEA Software Company ("AVEA") The recipient shall not reproduce or use the work either in whole or in part or for tendering, manufacturing purposes or any other purpose without obtaining AVEA's prior agreement or consent in writing A further condition of such reproduction or use is that this notice shall be included in the reproduction or use Copyright 2010 AVEA All rights are reserved No part of this document may be photocopied, reproduced or translated to another program language without prior consent of AVEA Software Company This document is furnished to you for your evaluation purposes only and shall not be deemed or be construed as an offer of sale by AVEA Disclaimer of Liability While every effort has been made to ensure the accuracy of all information and statements contained in this document, the service levels, performance and capabilities referred to are best estimates only, based on our understanding of data and information supplied by you and the assumptions listed Given that changes in your requirements may occur, and that final performance will depend on a variety of factors, not all of which are known in detail at this stage, none of the statements in this document constitutes a representation for which AVEA can accept any liability Your receipt of this document shall constitute your acceptance of the terms stated herein PIMS Page 4 of 28 Valid agreement required
Project ID No: DOCUMENT CONTROL SECTION Version History Status Version Author Change description Date Draft 01 AVEA PIMS Micropayment March 01, 2011 Definition, acronyms and abbreviations PIMS GUI Partner(Brand) Partner User Avea Operations (IT) Avea Marketing Merchant Service Service Category Limit Constraint GPO Blacklist Web based application provided by PIMS system, allowing management of service catalogue, subscriptions and charging operations A dealer company providing Micropayment services to its merchants through Avea infrastructure PIMS GUI application users allowed accessing only partner data and functionality Avea department responsible for running PIMS system Avea department responsible for service catalogue management A company using Avea Micropayment system for charging of its services or products Definition of a merchant provided service or product in Micropayment system A specific category of services Payment limitation of micropayment system at different levels Rules for phone user to use some advantages Virtual Mobile Operator running on Avea infrastructure Rules for authorizing Micropayment transactions PIMS Page 5 of 28 Valid agreement required
Project ID No: 1 Introduction This document explains PIMS s (Partner Interface Management System) Micropayment module for partners including usage scenarios, management GUI and API reference 2 System Overview PIMS is an Avea integration system providing service management tools and interfaces to partners By using PIMS Micropayment functionality; merchants and services are managed easily by partners 3 Micropayment Catalogue Workflow PIMS Micropayment catalogue management workflow is shown in the following diagram: PIMS Page 6 of 28 Valid agreement required
Project ID No: Step Task 1 Partner (Brand) is created by Avea Operations 2 PIMS GUI user is created for partner to allow access to PIMS GUI application 3 Partner creates merchant 4 Marketing approves merchant 5 Partner creates service for merchant 6 Marketing approves merchant 7 Partner edits service and generates user/password for merchant API access 8 Merchant puts API user/password into its application/configuration to access PIMS Micropayment API 4 PIMS Micropayment User Interface Partner users access PIMS GUI through http://partneraveacomtr Login Partner users are authenticated with assigned user names and passwords provided by Avea Operations PIMS Page 7 of 28 Valid agreement required
Project ID No: Main Menu Partners users can access micropayment pages under Catalog menu Merchants Merchants are companies using Avea Micropayment system for charging their services and products Merchants are managed by partners You can access to merchant list via CATALOG> Micro Payment> Merchant List PIMS Page 8 of 28 Valid agreement required
Project ID No: New merchants can be added or existing merchants can be edited through merchant list screen PIMS Page 9 of 28 Valid agreement required
Project ID No: Merchant Name: Name used in reports and GUI GSM: Contact phone of the merchant Description: Description and notes about the merchant Staff: Contact person from the merchant Start date: Launch date and may be later then system date End date: Planned/estimated end of life date for the merchant Requested status: Merchants can be deactivated/activated by partners but merchant status is changed after Avea Marketing approval History: list of merchant s versions ordered by date When merchant is created, it waits for approval to be active IT or Marketing can approve created merchants Without approval, a merchant can t be used Services Service is a definition of service/product provided by a merchant Services are managed by partners You can access to service list via CATALOG> Micro Payment> Mpay Services PIMS Page 10 of 28 Valid agreement required
Project ID No: New services can be added or existing services can be edited through service list screen PIMS Page 11 of 28 Valid agreement required
Project ID No: Start date: Launch date and may be later then system date End date: Planned/estimated end of life date for the service Service short code: Short code assigned to the service Payment remark: Short explanation of payment Service subscriber: Indicates that service is subscription based or not Service Payment Type: Payment type, prepaid or postpaid Service category: Category of the service Commission Amount: Revenue sharing ration between partner and merchant Permission: Micropayment API access permissions for direct payment, reservation, check credit and installment payment services History: list of service s versions ordered by date After service creation, service is approved by Avea operations and then PIMS API user and password information can be assigned to the service 5 PIMS Micropayment API DirectPayment PIMS Page 12 of 28 Valid agreement required
Project ID No: DirectPayment Request: Partner Application PIMS Name Type Required Description PimsApiUserInformation PimsApiUserInformation TRUE PIMS API access information assigned to service PimsApiUsername String TRUE User name PimsApiPassword String TRUE Password TransactionId String FALSE Transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) Amount Double TRUE Amount to be charged MerchantTransactionDateTime String TRUE Transaction timestamp at merchant system, useful transaction tracking Description String TRUE Text about transaction SmsOptInId String TRUE Verification information NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: <soapenv:envelope xmlns:soapenv="http://schemasxmlsoaporg/soap/envelope/" xmlns:sch="http://wwwaveacomtr/pims-mpay/schema"> <soapenv:header/> <soapenv:body> <sch:directpaymentrequest> <PimsApiUserInformation> <PimsApiUsername>MTM2NTM1MTEwODA1NU1QMjQ1MjE</PimsApiUsername> <PimsApiPassword>MTM2NTM1MTA2MjM2NU1QMjQ1MjE</PimsApiPassword> </PimsApiUserInformation> <!--Optional:--> <TransactionId>56546456</TransactionId><OrderId>21</OrderId> <Amount>1</Amount> <MerchantTransactionDateTime>2013-05-09T00:00:00000-04:00</MerchantTransactionDateTime> <Description>rewre</Description> <SmsOptInId>1</SmsOptInId> <Msisdn>00905079850555</Msisdn> <!--Zero or more repetitions:--> </sch:directpaymentrequest> </soapenv:body> </soapenv:envelope> DirectPayment Response: Name Type Required Description PIMS Page 13 of 28 Valid agreement required
Project ID No: ResponseCode String TRUE Code for the response of the operation ResponseMessage String TRUE Description of the response ResponseStatus int TRUE 0: Error / 1: S / 2: Warning ResponseDateTime String TRUE Transaction timestamp of Micropayment TransactionId String FALSE Transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) NamedParams NamedParam [0*] FALSE Key String FALSE Parameter key Value String FALSE Parameter value List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Example: <SOAP-ENV:Envelope xmlns:soap-env="http://schemasxmlsoaporg/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:directpaymentresponse xmlns:ns3="http://wwwaveacomtr/pims-mpay/schema"> <ServiceResponse> <ResponseCode>9008</ResponseCode> <ResponseMessage>Transaction Id Sent Before</ResponseMessage> <ResponseStatus>0</ResponseStatus> <ResponseDateTime>2013-05-28T15:01:34916+03:00</ResponseDateTime> </ServiceResponse> <TransactionId>56546456</TransactionId> </ns3:directpaymentresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> InstalmentPayment InstalmentPayment Request: Partner Application PIMS Name Type Required Description PimsApiUserInformation PimsApiUserInformation TRUE PIMS API access information assigned to service PimsApiUsername String TRUE User name PimsApiPassword String TRUE Password TransactionId String FALSE Transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) Amount Double TRUE Amount to be charged InstalmentCount Integer TRUE Total instalment count InstalmentNo Integer TRUE Instalment number MerchantTransactionDateTime String TRUE Transaction timestamp at merchant system, useful transaction tracking Description String TRUE Text about transaction PIMS Page 14 of 28 Valid agreement required
Project ID No: SmsOptInId String TRUE Verification information NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: <soapenv:envelope xmlns:soapenv="http://schemasxmlsoaporg/soap/envelope/" xmlns:sch="http://wwwaveacomtr/pims-mpay/schema"> <soapenv:header/> <soapenv:body> <sch:instalmentpaymentrequest> <PimsApiUserInformation> <PimsApiUsername>MTM2NTM1MTEwODA1NU1QMjQ1MjE</PimsApiUsername> <PimsApiPassword>MTM2NTM1MTA2MjM2NU1QMjQ1MjE</PimsApiPassword> </PimsApiUserInformation> <!--Optional:--> <TransactionId>65756756</TransactionId><OrderId>22</OrderId> <Amount>100</Amount> <InstalmentCount>5</InstalmentCount> <InstalmentNo>1</InstalmentNo> <MerchantTransactionDateTime>2013-05-09T00:00:00000-04:00</MerchantTransactionDateTime> <Description>eerter</Description> <SmsOptInId>1</SmsOptInId> <Msisdn>00905079850555</Msisdn> <!--Zero or more repetitions:--> </sch:instalmentpaymentrequest> </soapenv:body> </soapenv:envelope> InstalmentPayment Response: Name Type Required Description ResponseCode String TRUE Code for the response of the operation ResponseMessage String TRUE Description of the response ResponseStatus int TRUE 0: Error / 1: S / 2: Warning ResponseDateTime String TRUE Transaction timestamp of Micropayment TransactionId String FALSE Micropayment transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) InstalmentCount Integer TRUE Installment count InstalmentNo Integer TRUE Installment number NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed PIMS Page 15 of 28 Valid agreement required
Project ID No: New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: <SOAP-ENV:Envelope xmlns:soap-env="http://schemasxmlsoaporg/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:instalmentpaymentresponse xmlns:ns3="http://wwwaveacomtr/pims-mpay/schema"> <ServiceResponse> <ResponseCode>6008</ResponseCode> <ResponseMessage>InvalidInstallmentCount</ResponseMessage> <ResponseStatus>0</ResponseStatus> <ResponseDateTime>2013-05-28T15:08:10303+03:00</ResponseDateTime> </ServiceResponse> <InstalmentCount>0</InstalmentCount> <InstalmentNo>0</InstalmentNo> </ns3:instalmentpaymentresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Reservation Reservation Request: Partner Application PIMS Name Type Required Description PimsApiUserInformation PimsApiUserInformation TRUE PIMS API access information assigned to service PimsApiUsername String TRUE User name PimsApiPassword String TRUE Password TransactionId String FALSE Transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) Amount Double TRUE Amount to be charged MerchantTransactionDateTime String TRUE Transaction timestamp at merchant system, useful transaction tracking Description String TRUE Text about transaction SmsOptInId String TRUE Verification information NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: PIMS Page 16 of 28 Valid agreement required
Project ID No: <soapenv:envelope xmlns:soapenv="http://schemasxmlsoaporg/soap/envelope/" xmlns:sch="http://wwwaveacomtr/pims-mpay/schema"> <soapenv:header/> <soapenv:body> <sch:reservationrequest> <PimsApiUserInformation> <PimsApiUsername>MTM2NTM1MTEwODA1NU1QMjQ1MjE</PimsApiUsername> <PimsApiPassword>MTM2NTM1MTA2MjM2NU1QMjQ1MjE</PimsApiPassword> </PimsApiUserInformation> <!--Optional:--> <TransactionId>8979</TransactionId><OrderId>23</OrderId> <Amount>1</Amount> <MerchantTransactionDateTime>2013-05-09T00:00:00000-04:00</MerchantTransactionDateTime> <Description>rtyrty</Description> <SmsOptInId>1</SmsOptInId> <Msisdn>00905079850555</Msisdn> <!--Zero or more repetitions:--> </sch:reservationrequest> </soapenv:body> </soapenv:envelope> Reservation Response: Name Type Required Description ResponseCode String TRUE Code for the response of the operation ResponseMessage String TRUE Description of the response ResponseStatus int TRUE 0: Error / 1: S / 2: Warning ResponseDateTime String TRUE Transaction timestamp of Micropayment TransactionId String FALSE Transaction id If empty, it is generated by Micropayment OrderId String TRUE Order Id, client side reference to transaction(s) NamedParams NamedParam [0*] FALSE Key String FALSE Parameter key Value String FALSE Parameter value List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Example: <SOAP-ENV:Envelope xmlns:soap-env="http://schemasxmlsoaporg/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:reservationresponse xmlns:ns3="http://wwwaveacomtr/pims-mpay/schema"> <ServiceResponse> <ResponseCode>9008</ResponseCode> <ResponseMessage>Transaction Id Sent Before</ResponseMessage> <ResponseStatus>0</ResponseStatus> <ResponseDateTime>2013-05-28T15:09:59877+03:00</ResponseDateTime> PIMS Page 17 of 28 Valid agreement required
Project ID No: </ServiceResponse> <TransactionId>8979</TransactionId> </ns3:reservationresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> ReservationCancel ReservationCancel Request: Partner Application PIMS Name Type Required Description PimsApiUserInformation PimsApiUserInformation TRUE PIMS API access information assigned to service PimsApiUsername String TRUE User name PimsApiPassword String TRUE Password TransactionId String FALSE Transaction id If empty, it is generated by Micropayment ReferenceTransactionId String TRUE Reservation Transaction id to be cancelled MerchantTransactionDateTime String TRUE Transaction timestamp at merchant system, useful trasaction tracking NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: <soapenv:envelope xmlns:soapenv="http://schemasxmlsoaporg/soap/envelope/" xmlns:sch="http://wwwaveacomtr/pims-mpay/schema"> <soapenv:header/> <soapenv:body> <sch:reservationcancelrequest> <PimsApiUserInformation> <PimsApiUsername>MTM2NTM1MTEwODA1NU1QMjQ1MjE</PimsApiUsername> <PimsApiPassword>MTM2NTM1MTA2MjM2NU1QMjQ1MjE</PimsApiPassword> </PimsApiUserInformation> <!--Optional:--> <TransactionId>768687</TransactionId><ReferenceTransactionId>8979</ReferenceTransactionId> <MerchantTransactionDateTime>2013-05-09T00:00:00000-04:00</MerchantTransactionDateTime> <!--Zero or more repetitions:--> </sch:reservationcancelrequest> </soapenv:body> PIMS Page 18 of 28 Valid agreement required
Project ID No: </soapenv:envelope> ReservationCancel Response: Name Type Required Description ResponseCode String TRUE Code for the response of the operation ResponseMessage String TRUE Description of the response ResponseStatus int TRUE 0: Error / 1: S / 2: Warning ResponseDateTime String TRUE Transaction timestamp of Micropayment TransactionId String FALSE Micropayment transaction id If empty, it is generated by Micropayment ReferenceTransactionId String TRUE Reservation Transaction id to be cancelled NamedParams NamedParam [0*] FALSE Key String FALSE Parameter key Value String FALSE Parameter value List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Example: <SOAP-ENV:Envelope xmlns:soap-env="http://schemasxmlsoaporg/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:reservationcancelresponse xmlns:ns3="http://wwwaveacomtr/pims-mpay/schema"> <ServiceResponse> <ResponseCode>9008</ResponseCode> <ResponseMessage>Transaction Id Sent Before</ResponseMessage> <ResponseStatus>0</ResponseStatus> <ResponseDateTime>2013-05-28T15:11:09772+03:00</ResponseDateTime> </ServiceResponse> <TransactionId>768687</TransactionId> </ns3:reservationcancelresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> CheckCredit CheckCredit Request: Partner Application PIMS Name Type Required Description PimsApiUserInformation PimsApiUserInformation TRUE PIMS API access information assigned to service PimsApiUsername String TRUE User name PimsApiPassword String TRUE Password TransactionId String FALSE Micropayment transaction id If empty, it is generated by Micropayment Msisdn String TRUE MSISDN to be credit checked PIMS Page 19 of 28 Valid agreement required
Project ID No: Amount Double TRUE Amount to be charged MerchantTransactionDateTime String TRUE Transaction timestamp of merchant system, useful trasaction tracking NamedParams NamedParam [0*] FALSE List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change Key String FALSE Parameter key Value String FALSE Parameter value Example: <soapenv:envelope xmlns:soapenv="http://schemasxmlsoaporg/soap/envelope/" xmlns:sch="http://wwwaveacomtr/pims-mpay/schema"> <soapenv:header/> <soapenv:body> <sch:checkcreditrequest> <PimsApiUserInformation> <PimsApiUsername>MTM2NTM1MTEwODA1NU1QMjQ1MjE</PimsApiUsername> <PimsApiPassword>MTM2NTM1MTA2MjM2NU1QMjQ1MjE</PimsApiPassword> </PimsApiUserInformation> <!--Optional:--> <TransactionId>564556546</TransactionId><Msisdn>00905079850555</Msisdn> <Amount>2</Amount> <MerchantTransactionDateTime>2013-05-09T00:00:00000-04:00</MerchantTransactionDateTime> <!--Zero or more repetitions:--> </sch:checkcreditrequest> </soapenv:body> </soapenv:envelope> CheckCredit Response: Name Type Required Description ResponseCode String TRUE Code for the response of the operation ResponseMessage String TRUE Description of the response ResponseStatus int TRUE 0: Error / 1: S / 2: Warning ResponseDateTime String TRUE Transaction timestamp of Micropayment TransactionId String FALSE Micropayment transaction id If empty, it is generated by Micropayment NamedParams NamedParam [0*] FALSE Key String FALSE Parameter key Value String FALSE Parameter value List of key & value pairs, to be used later when passing a new parameter needed New parameters may be added without WSDL change PIMS Page 20 of 28 Valid agreement required
Project ID No: Example: <SOAP-ENV:Envelope xmlns:soap-env="http://schemasxmlsoaporg/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <ns3:checkcreditresponse xmlns:ns3="http://wwwaveacomtr/pims-mpay/schema"> <ServiceResponse> <ResponseCode>9008</ResponseCode> <ResponseMessage>Transaction Id Sent Before</ResponseMessage> <ResponseStatus>0</ResponseStatus> <ResponseDateTime>2013-05-28T14:54:36346+03:00</ResponseDateTime> </ServiceResponse> </ns3:checkcreditresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> 8 Error Codes Response Code Response Message Description MPAY-ERR-10005 Exception Message General Exception MPAY-ERR-10004 Mpay not implemented MPAY-ERR-10003 Ex: DirectPayment is not allowed Mpay not allowed MPAY-ERR-10002 Returns missing parameter area Ex: msisdn Empty or missing parameter MPAY-ERR-10001 Service Is Not Active Is not active MPAY-ERR-10000 Mpay ws call failed MPAY-ERR-0000 Succeded İşlem başarılıdır MPAY-ERR-0107 Unsufficient Operator Balance Yetersiz operatör bakiyesi MPAY-ERR-0108 MSISDNs Operator Status Is Not Active MSISDN operatör durumu aktif değildir MPAY-ERR-0109 MSISDNs Is In Operators Blacklist MSISDN MicroPayment servislerini kullanım için kısıtlanmıştır MPAY-ERR-0110 Avea Payment Error Avea ödeme hatası MPAY-ERR-0112 MSISDN Operator Activation Error For Postpaid Faturalı MSISDN operatör aktivasyon hatası MPAY-ERR-0113 MPAY-ERR-0118 MPAY-ERR-0119 MSISDN Operator Suspended Error For Postpaid Not Valid According To Activation Definition For Postpaid Not Valid According To Activation Definition For Prepaid Faturalı MSISDN operatör askıya alınma hatası İşlem servis kategorisi, faturalı hatlar için aktivasyon tanımına uygun değildir İşlem servis kategorisi, kontörlü hatlar için aktivasyon tanımına uygun değildir MPAY-ERR-0120 Voice Call Activation By Service Id Error Servis sesli görüşme limiti geçerli değildir MPAY-ERR-0121 Voice Call Activation By Service Category Id Error MPAY-ERR-0122 Avea Integration Error Avea entegrasyon hatası Servis kategori sesli görüşme limiti geçerli değildir MPAY-ERR-1003 MSISDN Not Found MSISDN tanımı bulunamadı MPAY-ERR-1017 Brand Not Found Üye iş ortağı bulunamadı MPAY-ERR-1018 Merchant Not Found Üye iş ortağı bayi bulunamadı PIMS Page 21 of 28 Valid agreement required
Project ID No: MPAY-ERR-1028 Service Not Found Servis bulunamadı MPAY-ERR-1029 ServiceCategory Not Found Service Kategori bulunamadı MPAY-ERR-1043 Invalid Amount Geçersiz tutar MPAY-ERR-1053 Invalid MSISDN Geçersiz MSISDN MPAY-ERR-1056 Conflict With Msisdn And Service Payment Type Msisdn ve Service ödeme tipi uyuşmazlığı MPAY-ERR-2030 Global Limit Should Be Defined Global limit tanımlanmalı MPAY-ERR-2031 Global Daily Amount Total Global günlük tutar limiti aşılmış MPAY-ERR-2032 Global Weekly Amount Total Global haftalık tutar limiti aşılmış MPAY-ERR-2033 Global Monthly Amount Total Global aylık tutar limiti aşılmış MPAY-ERR-2035 Global Instant Amount Global işlemsel tutar limiti aşılmış MPAY-ERR-2036 Global Daily Quantity Total Global günlük adet limiti aşılmış MPAY-ERR-2037 Global Weekly Quantity Total ExceededLimit Global haftalık adet limiti aşılmış MPAY-ERR-2038 Global Monthly Quantity Total ExceededLimit Global aylık adet limiti aşılmış MPAY-ERR-2041 Service Daily Amount Total Servis günlük tutar limiti aşılmış MPAY-ERR-2042 Service Weekly Amount Total Servis haftalık tutar limiti aşılmış MPAY-ERR-2043 Service Monthly Amount Total Servis aylık tutar limiti aşılmış MPAY-ERR-2045 Service Instant Amount Servis işlemsel tutar limiti aşılmış MPAY-ERR-2046 Service Daily Quantity Total Servis günlük adet limiti aşılmış MPAY-ERR-2047 Service Weekly Quantity Total Servis haftalık adet limiti aşılmış MPAY-ERR-2048 Service Monthly Quantity Total Servis aylık adet limiti aşılmış MPAY-ERR-2081 MPAY-ERR-2082 MPAY-ERR-2083 Customer Tariff Daily Amount Total Exceeded Limit Customer Tariff Weekly Amount Total Customer Tariff Monthly Amount Total Tarife günlük tutar limiti aşılmış Tarife haftalık tutar limiti aşılmış Tarife aylık tutar limiti aşılmış MPAY-ERR-2085 Customer Tariff Instant Amount Tarife işlemsel tutar limiti aşılmış MPAY-ERR-2086 MPAY-ERR-2087 MPAY-ERR-2088 Customer Tariff Daily Quantity Total Exceeded Limit Customer Tariff Weekly Quantity Total Customer Tariff Monthly Quantity Total Tarife günlük adet limiti aşılmış Tarife haftalık adet limiti aşılmış Tarife aylık adet limiti aşılmış MPAY-ERR-2203 Order Relation Info Not Found For Blacklist Tarife karaliste kontrolü için sipariş detayı bulunamadı MPAY-ERR-2205 Order Tariff No In Blacklist Siparişin tarife numarası kara listede yer alıyor MPAY-ERR-2281 MPAY-ERR-2282 MPAY-ERR-2283 MPAY-ERR-2285 Customer Group Daily Amount Total ExceededLimit Customer Group Weekly Amount Total ExceededLimit Customer Group Monthly Amount Total Customer Group Instant Amount Exceeded Limit Müşteri grubu günlük tutar limiti aşılmıştır Müşteri grubu haftalık tutar limiti aşılmıştır Müşteri grubu aylık tutar limiti aşılmıştır Müşteri grubu işlemsel tutar limiti aşılmıştır MPAY-ERR-2286 Customer Group Daily Quantity Total Exceeded Müşteri grubu günlük adet limiti aşılmıştır PIMS Page 22 of 28 Valid agreement required
Project ID No: MPAY-ERR-2287 MPAY-ERR-2288 MPAY-ERR-2291 MPAY-ERR-2292 MPAY-ERR-2293 MPAY-ERR-2295 MPAY-ERR-2296 MPAY-ERR-2297 MPAY-ERR-2298 MPAY-ERR-2341 MPAY-ERR-2342 MPAY-ERR-2343 MPAY-ERR-2345 MPAY-ERR-2346 MPAY-ERR-2347 MPAY-ERR-2348 MPAY-ERR-2441 MPAY-ERR-2442 MPAY-ERR-2443 Limit Customer Group Weekly Quantity Total Customer Group Monthly Quantity Total Service Category Daily Amount Total Exceeded Limit Service Category Weekly Amount Total Service Category Monthly Amount Total Service Category Instant Amount Exceeded Limit Service Category Daily Quantity Total Exceeded Limit Service Category Weekly Quantity Total Service Category Monthly Quantity Total Service-Postpaid Daily Amount Total Exceeded Limit Service-Postpaid Weekly Amount Total Service-Postpaid Monthly Amount Total Service-Postpaid Instant Amount Exceeded Limit Service-Postpaid Daily Quantity Total Exceeded Limit Service-Postpaid Weekly Quantity Total Service-Postpaid Monthly Quantity Total Service-Prepaid Daily Amount Total Exceeded Limit Service-Prepaid Weekly Amount Total Service-Prepaid Monthly Amount Total Müşteri grubu haftalık adet limiti aşılmıştır Müşteri grubu aylık adet limiti aşılmıştır Servis kategori günlük tutar limiti aşılmıştır Servis kategori haftalık tutar limiti aşılmıştır Servis kategori aylık tutar limiti aşılmıştır Servis kategori işlemsel tutar limiti aşılmıştır Servis kategori günlük adet limiti aşılmıştır Servis kategori haftalık adet limiti aşılmıştır Servis kategori aylık adet limiti aşılmıştır Faturalı hatlar için servis günlük tutar limiti aşılmıştır Faturalı hatlar için servis haftalık tutar limiti aşılmıştır Faturalı hatlar için servis aylık tutar limiti aşılmıştır Faturalı hatlar için servis işlemsel tutar limiti aşılmıştır Faturalı hatlar için servis günlük adet limiti aşılmıştır Faturalı hatlar için servis haftalık adet limiti aşılmıştır Faturalı hatlar için servis aylık adet limiti aşılmıştır Kontörlü hatlar için servis günlük tutar limiti aşılmıştır Kontörlü hatlar için servis haftalık tutar limiti aşılmıştır Kontörlü hatlar için servis aylık tutar limiti aşılmıştır MPAY-ERR-2445 Service-Prepaid Instant Amount Kontörlü hatlar için servis işlemsel tutar limiti aşılmıştır MPAY-ERR-2446 MPAY-ERR-2447 MPAY-ERR-2448 Service-Prepaid Daily Quantity Total Exceeded Limit Service-Prepaid Weekly Quantity Total Service-Prepaid Monthly Quantity Total Kontörlü hatlar için servis günlük adet limiti aşılmıştır Kontörlü hatlar için servis haftalık adet limiti aşılmıştır Kontörlü hatlar için servis aylık adet limiti aşılmıştır MPAY-ERR-3000 To Check Limit Service Should Not Be Null Limit kontrolü için gerekli olan servis bilgisi boş olamaz MPAY-ERR-3001 To Check Limit Service Category Should Not Be Null Limit kontrolü için gerekli olan servis kategori bilgisi boş olamaz MPAY-ERR-3002 To Check Limits Conditions Are Not Suitable Limit kontrolü için koşullar uygun değildir MPAY-ERR-3003 To Check Limit General Customer Information Of Customer Group Should Not Be Null Limit kontrolü için gerekli olan müşteri grubu bilgisi boş olamaz MPAY-ERR-3333 Service Category Not Active Servis kategorisi aktif değildir PIMS Page 23 of 28 Valid agreement required
Project ID No: MPAY-ERR-3344 Customer Group Id Not Found Müşteri grubu bilgisi bulunamadı MPAY-ERR-4003 Amount Element Is Not Exits In Asb Response Xml Of Voice Activation Information Sesli görüşme bilgisinde tutar bilgisi bulunmamaktadır MPAY-ERR-5000 Invalid Search Criteria Geçersiz arama kriterleri girilmiştir MPAY-ERR-5001 Missing Refund Reason Parameter Geri ödeme nedeni belirtilmemiştir MPAY-ERR-5003 Max Refund Time Exceeded Maksimum geri ödeme süresi aşılmıştır MPAY-ERR-5004 Refundable Transaction Not Found Geri ödeme yapılacak işlem bulunamamıştır MPAY-ERR-5005 Bankrupt Transaction Can Not Be Refunded Batık işlemler için geri ödeme yapılamaz MPAY-ERR-5006 Reservation Transaction Cancelled Before Rezervasyon işlemi daha önce iptal edilmiştir MPAY-ERR-5009 MPAY-ERR-5010 OriginalTransactionType Not Suitable To Refund OriginalTransactionType Not Suitable To ReservationCancel Orjianal Transactionın işlem tipi, Refund edilmeye uygun değil Orjianal Transactionın işlem tipi, Reservasyon İptal işlemine uygun değil MPAY-ERR-5500 Max Reservation Cancel Time Exceeded Maksimum rezervasyon iptal süresi aşılmıştır MPAY-ERR-5501 Transaction Refunded Before İşlem daha önce geri ödenmiştir MPAY-ERR-6000 Web Service Hour Restriction Error Uygulama saat kısıtı hatası MPAY-ERR-6002 Amount Exceeded Maximum Debt Limit Toplam borç limiti aşılmıştır MPAY-ERR-6003 Once Request Per Day For An Installment Error Taksit aynı gün içerisinde daha önce gönderilmiştir MPAY-ERR-6004 Bankrupt Transaction Can Not Be Paid Batık işlemler için ödeme yapılamaz MPAY-ERR-6005 Wrong Installment Number Error Yanlış taksit sırası MPAY-ERR-6006 Non Equal Installment Amount Error Taksit miktarı aynı gönderilmemiştir MPAY-ERR-6007 Only One Installment Of An Order Can Be Paid In A Day MPAY-ERR-6008 Invalid Installment Count Geçersiz taksit sayısı Bir sipariş için günde bir kez taksitli ödeme isteği gönderilebilir MPAY-ERR-6009 Invalid Installment Number Geçersiz taksit numarası MPAY-ERR-6010 Installment Of Refunded Order Can Not Be Paid Refund edilmiş siparişe ait taksitin ödemesi yapılamaz MPAY-ERR-7000 SMSC Connection Error SMSC iletişim hatası MPAY-ERR-7001 SMSC Technical Error SMSC teknik hata MPAY-ERR-7002 SMSC Client Technical Error SMSC istemci teknik hata MPAY-ERR-7003 MSISDN Not Valid To Send SMS MSISDN SMS gönderimi için geçerli değildir MPAY-ERR-7004 SMS Text Should Not Be Null To Send SMS SMS metinleri boş olmamalıdır MPAY-ERR-7005 Missing SMS Parameter Error To Send SMS SMS gönderimi için eksik parametre bulunmaktadır MPAY-ERR-8000 Merchant Is Not Active Üye iş ortağı bayi aktif değildir MPAY-ERR-8001 Brand Is Not Active Üye iş ortağı aktif değildir MPAY-ERR-8002 Invalid Customer Group Geçersiz müşteri grubu MPAY-ERR-8004 Customer Group Info Is Null Müşteri grup bilgisi boş olamaz MPAY-ERR-8005 Service Category Is Null Servis kategori bilgisi boş olamaz MPAY-ERR-8006 Service Is Not Active Servis aktif değildir MPAY-ERR-9000 Order Id Is Null Sipariş bilgisi boş olamaz MPAY-ERR-9001 Transaction Id Is Null İşlem bilgisi boş olamaz MPAY-ERR-9002 Referenced Transaction Id Is Null Orijinal işlem bilgisi boş olamaz PIMS Page 24 of 28 Valid agreement required