PIMS Micropayment
Partner Reference
Version: 0.1
Last version: June 3, 2013
Page 1 of 28
© All rights reserved, proprietary information
PIMS
Partner Reference
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.
PIMS
Partner Reference
Project ID No.:
PIMS
Page 3 of 28
.
Valid agreement required.
PIMS
Partner Reference
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.
PIMS
Partner Reference
Project ID No.:
DOCUMENT CONTROL SECTION
Version History
Status
Draft
Version
0.1
Author
Change description
AVEA
PIMS Micropayment
Date
March 01, 2011
Definition, acronyms and abbreviations
PIMS GUI
Web based application provided by PIMS system, allowing
management of service catalogue, subscriptions and charging
operations.
Partner(Brand)
A dealer company providing Micropayment services to its merchants
through Avea infrastructure
Partner User
PIMS GUI application users allowed accessing only partner data and
functionality.
Avea Operations (IT)
Avea department responsible for running PIMS system.
Avea Marketing
Avea department responsible for service catalogue management.
Merchant
Service Category
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
Limit
Payment limitation of micropayment system at different levels
Constraint
Rules for phone user to use some advantages.
GPO
Virtual Mobile Operator running on Avea infrastructure
Blacklist
Rules for authorizing Micropayment transactions
Service
PIMS
Page 5 of 28
.
Valid agreement required.
PIMS
Partner Reference
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.
PIMS
Partner Reference
Project ID No.:
Step
1
2
3
4
5
6
7
8
Task
Partner (Brand) is created by Avea Operations
PIMS GUI user is created for partner to allow access to PIMS GUI application
Partner creates merchant
Marketing approves merchant
Partner creates service for merchant
Marketing approves merchant
Partner edits service and generates user/password for merchant API access
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://partner.avea.com.tr
Login
Partner users are authenticated with assigned user names and passwords provided by Avea
Operations.
PIMS
Page 7 of 28
.
Valid agreement required.
PIMS
Partner Reference
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.
PIMS
Partner Reference
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.
PIMS
Partner Reference
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.
PIMS
Partner Reference
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.
PIMS
Partner Reference
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.
PIMS
Partner Reference
Project ID No.:
DirectPayment Request: Partner Application  PIMS
Name
Type
PimsApiUserInformation
PimsApiUserInformation
Required
TRUE
Description
PIMS API access information
assigned to service
String
String
TRUE
TRUE
User name
Password
TransactionId
String
FALSE
OrderId
String
TRUE
Amount
MerchantTransactionDateTime
Double
String
TRUE
TRUE
Description
SmsOptInId
NamedParams
String
String
NamedParam [0..*]
TRUE
TRUE
FALSE
Transaction id. If empty, it is
generated by Micropayment
Order Id, client side
reference to transaction(s)
Amount to be charged
Transaction timestamp at
merchant system, useful
transaction tracking
Text about transaction
Verification information
List of key & value pairs, to be
used later when passing a
new parameter needed.
New parameters may be
added without WSDL
change.
String
String
FALSE
FALSE
PimsApiUsername
PimsApiPassword
Key
Value
Parameter key
Parameter value
Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sch="http://www.avea.com.tr/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:00.00004: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.
PIMS
Partner Reference
Project ID No.:
ResponseCode
String
TRUE
Code for the response of the operation
ResponseMessage
ResponseStatus
ResponseDateTime
TransactionId
String
int
String
String
TRUE
TRUE
TRUE
FALSE
OrderId
String
TRUE
NamedParams
NamedParam
[0..*]
FALSE
Description of the response
0: Error / 1: S... / 2: Warning
Transaction timestamp of Micropayment
Transaction id. If empty, it is generated by
Micropayment
Order Id, client side reference to
transaction(s)
List of key & value pairs, to be used later
when passing a new parameter needed.
New parameters may be added without
WSDL change.
String
String
FALSE
FALSE
Key
Value
Parameter key
Parameter value
Example:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:DirectPaymentResponse xmlns:ns3="http://www.avea.com.tr/pims-mpay/schema">
<ServiceResponse>
<ResponseCode>9008</ResponseCode>
<ResponseMessage>Transaction Id Sent Before</ResponseMessage>
<ResponseStatus>0</ResponseStatus>
<ResponseDateTime>2013-05-28T15:01:34.916+03:00</ResponseDateTime>
</ServiceResponse>
<TransactionId>56546456</TransactionId>
</ns3:DirectPaymentResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
InstalmentPayment
InstalmentPayment Request: Partner Application  PIMS
Name
Type
Required
PimsApiUserInformation
PimsApiUserInformation
TRUE
PimsApiUsername
PimsApiPassword
Description
PIMS API access information
assigned to service
String
String
TRUE
TRUE
User name
Password
TransactionId
String
FALSE
OrderId
String
TRUE
Amount
InstalmentCount
InstalmentNo
MerchantTransactionDateTime
Double
Integer
Integer
String
TRUE
TRUE
TRUE
TRUE
Description
String
TRUE
Transaction id. If empty, it is
generated by Micropayment
Order Id, client side
reference to transaction(s)
Amount to be charged
Total instalment count
Instalment number
Transaction timestamp at
merchant system, useful
transaction tracking
Text about transaction
PIMS
Page 14 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
SmsOptInId
NamedParams
Key
Value
String
NamedParam [0..*]
TRUE
FALSE
Verification information
List of key & value pairs, to be
used later when passing a
new parameter needed.
New parameters may be
added without WSDL
change.
String
String
FALSE
FALSE
Parameter key
Parameter value
Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sch="http://www.avea.com.tr/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:00.00004: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
ResponseCode
String
Required
TRUE
Description
Code for the response of the operation
ResponseMessage
ResponseStatus
ResponseDateTime
TransactionId
String
int
String
String
TRUE
TRUE
TRUE
FALSE
OrderId
String
TRUE
InstalmentCount
InstalmentNo
NamedParams
Integer
Integer
NamedParam
[0..*]
TRUE
TRUE
FALSE
Description of the response
0: Error / 1: S... / 2: Warning
Transaction timestamp of Micropayment
Micropayment transaction id. If empty, it is
generated by Micropayment
Order Id, client side reference to
transaction(s)
Installment count
Installment number
List of key & value pairs, to be used later
when passing a new parameter needed.
PIMS
Page 15 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
New parameters may be added without
WSDL change.
Key
Value
String
String
FALSE
FALSE
Parameter key
Parameter value
Example:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:InstalmentPaymentResponse xmlns:ns3="http://www.avea.com.tr/pims-mpay/schema">
<ServiceResponse>
<ResponseCode>6008</ResponseCode>
<ResponseMessage>InvalidInstallmentCount</ResponseMessage>
<ResponseStatus>0</ResponseStatus>
<ResponseDateTime>2013-05-28T15:08:10.303+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
PimsApiUserInformation
PimsApiUserInformation
Required
TRUE
Description
PIMS API access information
assigned to service
String
String
TRUE
TRUE
User name
Password
TransactionId
String
FALSE
OrderId
String
TRUE
Amount
MerchantTransactionDateTime
Double
String
TRUE
TRUE
Description
SmsOptInId
NamedParams
String
String
NamedParam [0..*]
TRUE
TRUE
FALSE
Transaction id. If empty, it is
generated by Micropayment
Order Id, client side
reference to transaction(s)
Amount to be charged
Transaction timestamp at
merchant system, useful
transaction tracking
Text about transaction
Verification information
List of key & value pairs, to be
used later when passing a
new parameter needed.
New parameters may be
added without WSDL
change.
String
String
FALSE
FALSE
PimsApiUsername
PimsApiPassword
Key
Value
Parameter key
Parameter value
Example:
PIMS
Page 16 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sch="http://www.avea.com.tr/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:00.00004:00</MerchantTransactionDateTime>
<Description>rtyrty</Description>
<SmsOptInId>1</SmsOptInId>
<Msisdn>00905079850555</Msisdn>
<!--Zero or more repetitions:-->
</sch:ReservationRequest>
</soapenv:Body>
</soapenv:Envelope>
Reservation Response:
Name
ResponseCode
Type
String
Required
TRUE
Description
Code for the response of the operation
ResponseMessage
ResponseStatus
ResponseDateTime
TransactionId
String
int
String
String
TRUE
TRUE
TRUE
FALSE
OrderId
String
TRUE
NamedParams
NamedParam
[0..*]
FALSE
Description of the response
0: Error / 1: S... / 2: Warning
Transaction timestamp of Micropayment
Transaction id. If empty, it is generated by
Micropayment
Order Id, client side reference to
transaction(s)
List of key & value pairs, to be used later
when passing a new parameter needed.
New parameters may be added without
WSDL change.
String
String
FALSE
FALSE
Key
Value
Parameter key
Parameter value
Example:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:ReservationResponse xmlns:ns3="http://www.avea.com.tr/pims-mpay/schema">
<ServiceResponse>
<ResponseCode>9008</ResponseCode>
<ResponseMessage>Transaction Id Sent Before</ResponseMessage>
<ResponseStatus>0</ResponseStatus>
<ResponseDateTime>2013-05-28T15:09:59.877+03:00</ResponseDateTime>
PIMS
Page 17 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
</ServiceResponse>
<TransactionId>8979</TransactionId>
</ns3:ReservationResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
ReservationCancel
ReservationCancel Request: Partner Application  PIMS
Name
Type
Required
PimsApiUserInformation
PimsApiUserInformation
TRUE
PimsApiUsername
PimsApiPassword
Description
PIMS API access
information assigned to
service
String
String
TRUE
TRUE
User name
Password
TransactionId
String
FALSE
ReferenceTransactionId
String
TRUE
MerchantTransactionDateTime
String
TRUE
NamedParams
NamedParam [0..*]
FALSE
Transaction id. If empty, it
is generated by
Micropayment
Reservation Transaction
id to be cancelled
Transaction timestamp at
merchant system, useful
trasaction tracking
List of key & value pairs,
to be used later when
passing a new parameter
needed. New
parameters may be
added without WSDL
change.
String
String
FALSE
FALSE
Key
Value
Parameter key
Parameter value
Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sch="http://www.avea.com.tr/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:00.00004:00</MerchantTransactionDateTime>
<!--Zero or more repetitions:-->
</sch:ReservationCancelRequest>
</soapenv:Body>
PIMS
Page 18 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
</soapenv:Envelope>
ReservationCancel Response:
Name
Type
ResponseCode
String
Required
TRUE
Description
Code for the response of the operation
ResponseMessage
ResponseStatus
ResponseDateTime
TransactionId
String
int
String
String
TRUE
TRUE
TRUE
FALSE
ReferenceTransactionId
NamedParams
String
NamedParam
[0..*]
TRUE
FALSE
Description of the response
0: Error / 1: S... / 2: Warning
Transaction timestamp of Micropayment
Micropayment transaction id. If empty, it is
generated by Micropayment
Reservation Transaction id to be cancelled
List of key & value pairs, to be used later
when passing a new parameter needed.
New parameters may be added without
WSDL change.
String
String
FALSE
FALSE
Key
Value
Parameter key
Parameter value
Example:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:ReservationCancelResponse xmlns:ns3="http://www.avea.com.tr/pims-mpay/schema">
<ServiceResponse>
<ResponseCode>9008</ResponseCode>
<ResponseMessage>Transaction Id Sent Before</ResponseMessage>
<ResponseStatus>0</ResponseStatus>
<ResponseDateTime>2013-05-28T15:11:09.772+03:00</ResponseDateTime>
</ServiceResponse>
<TransactionId>768687</TransactionId>
</ns3:ReservationCancelResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
CheckCredit
CheckCredit Request: Partner Application  PIMS
Name
Type
PimsApiUserInformation
PimsApiUserInformation
Required
TRUE
Description
PIMS API access
information assigned to
service
String
String
TRUE
TRUE
User name
Password
TransactionId
String
FALSE
Msisdn
String
TRUE
Micropayment
transaction id. If empty, it
is generated by
Micropayment
MSISDN to be credit
checked
PimsApiUsername
PimsApiPassword
PIMS
Page 19 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
Amount
MerchantTransactionDateTime
Double
String
TRUE
TRUE
NamedParams
NamedParam [0..*]
FALSE
String
String
FALSE
FALSE
Key
Value
Amount to be charged
Transaction timestamp of
merchant system, useful
trasaction tracking
List of key & value pairs,
to be used later when
passing a new parameter
needed. New
parameters may be
added without WSDL
change.
Parameter key
Parameter value
Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:sch="http://www.avea.com.tr/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:00.00004:00</MerchantTransactionDateTime>
<!--Zero or more repetitions:-->
</sch:CheckCreditRequest>
</soapenv:Body>
</soapenv:Envelope>
CheckCredit Response:
Name
Type
ResponseCode
String
Required
TRUE
Description
Code for the response of the operation
ResponseMessage
ResponseStatus
ResponseDateTime
TransactionId
String
int
String
String
TRUE
TRUE
TRUE
FALSE
NamedParams
NamedParam
[0..*]
FALSE
Description of the response
0: Error / 1: S... / 2: Warning
Transaction timestamp of Micropayment
Micropayment transaction id. If empty, it is
generated by Micropayment
List of key & value pairs, to be used later
when passing a new parameter needed.
New parameters may be added without
WSDL change.
String
String
FALSE
FALSE
Key
Value
Parameter key
Parameter value
PIMS
Page 20 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
Example:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ns3:CheckCreditResponse xmlns:ns3="http://www.avea.com.tr/pims-mpay/schema">
<ServiceResponse>
<ResponseCode>9008</ResponseCode>
<ResponseMessage>Transaction Id Sent Before</ResponseMessage>
<ResponseStatus>0</ResponseStatus>
<ResponseDateTime>2013-05-28T14:54:36.346+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
MSISDN Operator Suspended Error For
Postpaid
Not Valid According To Activation Definition
For Postpaid
Not Valid According To Activation Definition
For Prepaid
Voice Call Activation By Service Id Error
Faturalı MSISDN operatör askıya alınma hatası.
Servis kategori sesli görüşme limiti geçerli değildir.
MPAY-ERR-0122
Voice Call Activation By Service Category Id
Error
Avea Integration Error
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ı.
MPAY-ERR-0118
MPAY-ERR-0119
MPAY-ERR-0120
MPAY-ERR-0121
İş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.
Servis sesli görüşme limiti geçerli değildir.
Avea entegrasyon hatası.
PIMS
Page 21 of 28
.
Valid agreement required.
PIMS
Partner Reference
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
Msisdn ve Service ödeme tipi uyuşmazlığı
MPAY-ERR-2030
Conflict With Msisdn And Service Payment
Type
Global Limit Should Be Defined
MPAY-ERR-2031
Global Daily Amount Total Exceeded Limit
Global günlük tutar limiti aşılmış.
MPAY-ERR-2032
Global Weekly Amount Total Exceeded Limit
Global haftalık tutar limiti aşılmış.
MPAY-ERR-2033
Global Monthly Amount Total Exceeded Limit
Global aylık tutar limiti aşılmış.
MPAY-ERR-2035
Global Instant Amount Exceeded Limit
Global işlemsel tutar limiti aşılmış.
MPAY-ERR-2036
Global Daily Quantity Total Exceeded Limit
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 Exceeded Limit
Servis günlük tutar limiti aşılmış.
MPAY-ERR-2042
Service Weekly Amount Total Exceeded Limit
Servis haftalık tutar limiti aşılmış.
MPAY-ERR-2043
Service Monthly Amount Total Exceeded Limit
Servis aylık tutar limiti aşılmış.
MPAY-ERR-2045
Service Instant Amount Exceeded Limit
Servis işlemsel tutar limiti aşılmış..
MPAY-ERR-2046
Service Daily Quantity Total Exceeded Limit
Servis günlük adet limiti aşılmış.
MPAY-ERR-2047
Service Weekly Quantity Total Exceeded Limit
Servis haftalık adet limiti aşılmış.
MPAY-ERR-2048
Service Monthly Quantity Total Exceeded Limit
Servis aylık adet limiti aşılmış.
MPAY-ERR-2081
Customer Tariff Daily Amount Total Exceeded
Limit
Customer Tariff Weekly Amount Total
Exceeded Limit
Customer Tariff Monthly Amount Total
Exceeded Limit
Customer Tariff Instant Amount Exceeded Limit
Tarife günlük tutar limiti aşılmış.
Tarife günlük adet limiti aşılmış.
MPAY-ERR-2203
Customer Tariff Daily Quantity Total Exceeded
Limit
Customer Tariff Weekly Quantity Total
Exceeded Limit
Customer Tariff Monthly Quantity Total
Exceeded Limit
Order Relation Info Not Found For Blacklist
MPAY-ERR-2205
Order Tariff No In Blacklist
Siparişin tarife numarası kara listede yer alıyor.
MPAY-ERR-2281
Customer Group Daily Amount Total
ExceededLimit
Customer Group Weekly Amount Total
ExceededLimit
Customer Group Monthly Amount Total
Exceeded Limit
Customer Group Instant Amount Exceeded
Limit
Customer Group Daily Quantity Total Exceeded
Müşteri grubu günlük tutar limiti aşılmıştır.
MPAY-ERR-2082
MPAY-ERR-2083
MPAY-ERR-2085
MPAY-ERR-2086
MPAY-ERR-2087
MPAY-ERR-2088
MPAY-ERR-2282
MPAY-ERR-2283
MPAY-ERR-2285
MPAY-ERR-2286
Global limit tanımlanmalı.
Tarife haftalık tutar limiti aşılmış.
Tarife aylık tutar limiti aşılmış.
Tarife işlemsel tutar limiti aşılmış.
Tarife haftalık adet limiti aşılmış.
Tarife aylık adet limiti aşılmış.
Tarife karaliste kontrolü için sipariş detayı bulunamadı.
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.
Müşteri grubu günlük adet limiti aşılmıştır.
PIMS
Page 22 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
Limit
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
MPAY-ERR-2445
MPAY-ERR-2446
MPAY-ERR-2447
MPAY-ERR-2448
MPAY-ERR-3000
MPAY-ERR-3001
MPAY-ERR-3002
MPAY-ERR-3003
MPAY-ERR-3333
Customer Group Weekly Quantity Total
Exceeded Limit
Customer Group Monthly Quantity Total
Exceeded Limit
Service Category Daily Amount Total Exceeded
Limit
Service Category Weekly Amount Total
Exceeded Limit
Service Category Monthly Amount Total
Exceeded Limit
Service Category Instant Amount Exceeded
Limit
Service Category Daily Quantity Total Exceeded
Limit
Service Category Weekly Quantity Total
Exceeded Limit
Service Category Monthly Quantity Total
Exceeded Limit
Service-Postpaid Daily Amount Total Exceeded
Limit
Service-Postpaid Weekly Amount Total
Exceeded Limit
Service-Postpaid Monthly Amount Total
Exceeded Limit
Service-Postpaid Instant Amount Exceeded
Limit
Service-Postpaid Daily Quantity Total Exceeded
Limit
Service-Postpaid Weekly Quantity Total
Exceeded Limit
Service-Postpaid Monthly Quantity Total
Exceeded Limit
Service-Prepaid Daily Amount Total Exceeded
Limit
Service-Prepaid Weekly Amount Total
Exceeded Limit
Service-Prepaid Monthly Amount Total
Exceeded Limit
Service-Prepaid Instant Amount Exceeded Limit
Müşteri grubu haftalık adet limiti aşılmıştır.
Service-Prepaid Daily Quantity Total Exceeded
Limit
Service-Prepaid Weekly Quantity Total
Exceeded Limit
Service-Prepaid Monthly Quantity Total
Exceeded Limit
To Check Limit Service Should Not Be Null
Kontörlü hatlar için servis günlük adet limiti aşılmıştır.
To Check Limit Service Category Should Not Be
Null
To Check Limits Conditions Are Not Suitable
Limit kontrolü için gerekli olan servis kategori bilgisi boş
olamaz.
Limit kontrolü için koşullar uygun değildir.
To Check Limit General Customer Information
Of Customer Group Should Not Be Null
Service Category Not Active
Limit kontrolü için gerekli olan müşteri grubu bilgisi boş
olamaz.
Servis kategorisi aktif değildir.
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.
Kontörlü hatlar için servis işlemsel tutar 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.
Limit kontrolü için gerekli olan servis bilgisi boş olamaz.
PIMS
Page 23 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
MPAY-ERR-3344
Customer Group Id Not Found
Müşteri grubu bilgisi bulunamadı.
MPAY-ERR-4003
Sesli görüşme bilgisinde tutar bilgisi bulunmamaktadır.
MPAY-ERR-5000
Amount Element Is Not Exits In Asb Response
Xml Of Voice Activation Information
Invalid Search Criteria
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
Orjianal Transactionın işlem tipi, Refund edilmeye uygun değil
MPAY-ERR-5500
OriginalTransactionType Not Suitable To
Refund
OriginalTransactionType Not Suitable To
ReservationCancel
Max Reservation Cancel Time Exceeded
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
MPAY-ERR-6008
Only One Installment Of An Order Can Be Paid
In A Day
Invalid Installment Count
Bir sipariş için günde bir kez taksitli ödeme isteği
gönderilebilir.
Geçersiz taksit sayısı.
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.
MPAY-ERR-5010
Geçersiz arama kriterleri girilmiştir.
Orjianal Transactionın işlem tipi, Reservasyon İptal işlemine
uygun değil
Maksimum rezervasyon iptal süresi aşılmıştır.
PIMS
Page 24 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
MPAY-ERR-9003
Ödeme tipi bu servis için uygun değildir.
MPAY-ERR-9004
Service Not Permitted To Use This Payment
Type
Merchant Transaction Date Time Is Null
MPAY-ERR-9005
Brand Id Is Null
Üye iş ortağı bilgisi boş olamaz.
MPAY-ERR-9006
Referenced Transaction Id Not Found
Orijinal işlem bilgisi bulunamadı.
MPAY-ERR-9007
Service Id Is Null
Servis bilgisi boş olamaz.
MPAY-ERR-9008
Transaction Id Sent Before
İşlem daha önce gönderilmiştir.
MPAY-ERR-9009
Order Succeded Before
Sipariş daha önce başarılı olmuştur.
MPAY-ERR-9010
Idempotency For Uncompleted Transaction
İşlem sonuçlanmadan tekrar gönderilmiştir.
MPAY-ERR-9011
Transaction Id Is Too Long
TransactionId bilgisi çok uzun.
MPAY-ERR-9012
Order Id Is Too Long
OrderId bilgisi çok uzun.
MPAY-ERR-9017
End Date Must Greater Than Start
Bitiş tarihi başlangıç tarihinden büyük olmalı.
MPAY-ERR-9018
Başlangıç tarihi, minimum tarih değerinden büyük olmalı.
MPAY-ERR-9020
Start Date Must Be Greater Than Date Time
Min Val
End Date Must Be Greater Than Date Time Min
Val
Invalid Search Period
MPAY-ERR-9021
Empty Request
Boş istek.
MPAY-ERR-9022
Start Date Must Be Declared
Başlangıç tarihi tanımlanmalı.
MPAY-ERR-9023
End Date Must Be Declared
Bitiş tarihi tanımlanmalı.
MPAY-ERR-9024
Invalid Operation Type
İşlem tipi geçersiz.
MPAY-ERR-9500
Brand Name Is Null
İş ortağı adı bilgisi boş olamaz.
MPAY-ERR-9501
Brand Name Length Is Too Long
İş ortağı adı bilgisi çok uzun.
MPAY-ERR-9502
Email Length Is Too Long
E-posta bilgisi çok uzun.
MPAY-ERR-9503
GSM No Length Is Too Long
GSM No bilgisi çok uzun.
MPAY-ERR-9504
GSM No Format Is Not Valid
GSM No formatı hatalı.
MPAY-ERR-9505
SN Code Length Is Too Long
SNCode bilgisi çok uzun.
MPAY-ERR-9506
Email Format Is Not Valid
Email formatı hatalı.
MPAY-ERR-9507
Merchant Name Length Is Too Long
İş ortağı bayi adı bilgisi çok uzun.
MPAY-ERR-9508
İş ortağı bayi sorumlu kişi ad-soyad bilgisi çok uzun.
MPAY-ERR-9509
Merchant Employee Name Surname Is Too
Long
Service Name Length Is Too Long
MPAY-ERR-9510
Service Short Code Is Too Long
Servis kısa kod bilgisi çok uzun.
MPAY-ERR-9512
Payment Type Is Null
Ödeme şekli bilgisi boş olamaz.
MPAY-ERR-9513
Payment Type Is Too Long
Ödeme şekli bilgisi çok uzun.
MPAY-ERR-9515
Payment Remark Is Null
Servis tanım bilgisi boş olamaz.
MPAY-ERR-9516
Payment Remark Is Too Long
Servis tanım bilgisi çok uzun.
MPAY-ERR-9518
Service Category Name Is Null
Servis kategori adı bilgisi boş olamaz.
MPAY-ERR-9519
Service Category Name Is Too Long
Servis kategori adı bilgisi çok uzun.
MPAY-ERR-9520
No Records Found That Match Your Criteria
Arama kriterlerinize uygun kayıt bulunamadı.
MPAY-ERR-9521
GPO Id Is Null
GPO Id bilgisi boş olamaz.
MPAY-ERR-9019
Üye iş ortağı bayisinden gelen işlem zaman bilgisi boş olamaz.
Bitiş tarihi, minimum tarih değerinden büyük olmalı.
Arama periyodu geçersiz.
Servis adı bilgisi çok uzun.
PIMS
Page 25 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
MPAY-ERR-9522
GPO Name Is Null
GPO adı bilgisi boş olamaz.
MPAY-ERR-9523
GPO Name Is Too Long
GPO adı bilgisi çok uzun.
MPAY-ERR-9524
Voice Call Constraint Type Is Null
Sesli arama kısıt tipi bilgisi boş olamaz.
MPAY-ERR-9525
Voice Call Constraint Type Is Invalid
Sesli arama kısıt tipi hatalı.
MPAY-ERR-9526
Voice Call Constraint Type Id Is Null
Sesli arama kısıt tipi Id bilgisi boş olamaz.
MPAY-ERR-9527
Is Check Voice Call Amount Is Null
Sesli arama kısıt kontrolü bilgisi boş bırakılamaz
MPAY-ERR-9528
Voice Call Amount Is Null
Sesli arama kısıt değeri boş olamaz.
MPAY-ERR-9531
Postpaid Activation Day Count Is Null
Faturalı hat aktivasyon gün miktar bilgisi boş olamaz.
MPAY-ERR-9532
Prepaid Activation Day Count Is Null
Kontörlü hat aktivasyon gün miktar bilgisi boş olamaz.
MPAY-ERR-9533
Postpaid Activation Day Count Is Invalid
Faturalı hat aktivasyon gün miktar bilgisi geçersiz.
MPAY-ERR-9534
Prepaid Activation Day Count Is Invalid
Kontörlü hat aktivasyon gün miktar bilgisi geçersiz.
MPAY-ERR-9535
Parameter Key Is Null
Anahtar parametre bilgisi boş olamaz.
MPAY-ERR-9536
Parameter Value Is Null
Anahtar parametre değer bilgisi boş olamaz.
MPAY-ERR-9537
Parameter Value Is Invalid
Anahtar parametre değeri geçersiz
MPAY-ERR-9538
Limit Name Is Null
Limit isim bilgisi boş olamaz.
MPAY-ERR-9539
Limit Name Is Too Long
Limit isim bilgisi çok uzun.
MPAY-ERR-9540
Limit Type Is Null
Limit tipi bilgisi boş olamaz.
MPAY-ERR-9541
Limit Type Is Invalid
Limit tipi geçersiz.
MPAY-ERR-9542
Limit Type Id Is Null
Limit tipi Id bilgisi boş olamaz.
MPAY-ERR-9543
Limit Period Is Null
Limit periyot bilgisi boş olamaz.
MPAY-ERR-9544
Limit Period Is Invalid
Limit periyot bilgisi geçersiz.
MPAY-ERR-9545
Limit Value Type Is Null
Limit değer tipi bilgisi boş olamaz.
MPAY-ERR-9546
Limit Value Type Is Invalid
Limit değer tipi geçersiz.
MPAY-ERR-9547
Limit Value Is Invalid
Limit değer bilgisi geçersiz.
MPAY-ERR-9548
Limit Id Is Null
Limit Id bilgisi boş olamaz.
MPAY-ERR-9549
Customer Tariff Blacklist Type Is Null
Müşteri tarife kara liste tipi bilgisi boş olamaz.
MPAY-ERR-9550
Customer Tariff Blacklist Type Is Invalid
Müşteri tarife kara liste tipi bilgisi geçersiz.
MPAY-ERR-9551
Customer Tariff Blacklist Type Id Is Null
Müşteri tarife kara liste tipi Id bilgisi boş olamaz.
MPAY-ERR-9552
Customer Tariff Id Is Null
Müşteri tarife Id bilgisi boş olamaz.
MPAY-ERR-9553
Response Code Is Null
Cevap kodu bilgisi boş olamaz.
MPAY-ERR-9554
Response Code Is Too Long
Cevap kodu bilgisi çok uzun.
MPAY-ERR-9555
Response Code Format Is Invalid
Cevap kodu formatı geçersiz.
MPAY-ERR-9556
Is Sent Prepaid Is Null
Kontörlü hatlar için gönderilme bilgisi boş olamaz.
MPAY-ERR-9557
Is Sent Postpaid Is Null
Fatura hatlar için gönderilme bilgisi boş olamaz.
MPAY-ERR-9558
SMS Text Prepaid Is Null
Kontörlü hatlar için SMS metin bilgisi boş olamaz.
MPAY-ERR-9559
SMS Text Prepaid Is Too Long
Kontörlü hatlar için SMS metin bilgisi çok uzun.
MPAY-ERR-9560
SMS Text Postpaid Is Null
Faturalı hatlar için SMS metin bilgisi boş olamaz.
MPAY-ERR-9561
SMS Text Postpaid Is Too Long
Faturalı hatlar için SMS metin bilgisi çok uzun.
PIMS
Page 26 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
MPAY-ERR-9562
SMS List Is Null
SMS listesi boş olamaz.
MPAY-ERR-9563
Start Date Cannot Be After End Date
Başlangıç tarihi bitiş tarihinden sonra olamaz.
MPAY-ERR-9564
Operation Type Id Is Invalid
Operasyon tipi bilgisi geçersiz.
MPAY-ERR-9565
Max Grouped Exception Count Before Alert Is
Null
Max Transactionless Time Interval In Minutes
Before
Alert Is Null
Max SMS Submit Received Average Date
Difference
Duration In Seconds Is Null
Max Pending SMS Count Is Null
Alarm öncesi maksimum gruplanmış hata miktarı bilgisi boş
olamaz.
Alarm öncesi maksimum işlem geçmeyen, dakika cinsinden
zaman aralığı bilgisi boş olamaz.
MPAY-ERR-9570
Request Response Date Difference Average
Control In Seconds Is Null
Min Achievement List Count Is Null
Saniye cinsinden işlem geliş-gidiş zaman farkı bilgisi boş
olamaz.
Minimum başarılı işlem listesi miktarı bilgisi boş olamaz
MPAY-ERR-9571
System Limit Id Is Null
Sistem limit Id bilgisi boş olamaz.
MPAY-ERR-9572
Is Declared System Alert Limit Is Null
Sistem alarm bilgisi boş olamaz.
MPAY-ERR-9573
Start Hour Can Not Be After End Hour
Başlangıç saati bitiş saatinden sonra olamaz.
MPAY-ERR-9574
Merchant Alert Limit IdIs Null
İş ortağı bayi alarm limit Id bilgisi boş olamaz.
MPAY-ERR-9575
Is Declared Alert Is Null
Alarm bilgisi boş olamaz.
MPAY-ERR-9576
Max Transactionless Time In Minutes Is Null
MPAY-ERR-9577
Brand Alert Limit Id Is Null
Dakika bazında maksimum işlem geçmeme süresi bilgisi boş
olamaz.
İş ortağı alarm limit Id bilgisi boş olamaz.
MPAY-ERR-9578
Client Request Id Is Null
İstemci istek Id bilgisi boş olamaz.
MPAY-ERR-9579
Client Request Id Is Too Long
İstemci istek Id bilgisi çok uzun.
MPAY-ERR-9580
Client Id Is Null
İstemci bilgisi boş olamaz.
MPAY-ERR-9581
Client Password Is Null
İstemci şifre bilgisi boş olamaz.
MPAY-ERR-9582
Client Password Is Too Long
İstemci şifre bilgisi çok uzun.
MPAY-ERR-9583
Client Request Date Time Is Null
İstemci işlem tarihi bilgisi boş olamaz.
MPAY-ERR-9584
Page Index Is Null
Listenin kaçıncı sayfasının gösterileceği bilgisi boş olamaz.
MPAY-ERR-9585
Page Size Is Null
MPAY-ERR-9586
Sort Type Is Invalid
Listenin tek sayfasında kaç kayıt gösterileceği bilgisi boş
olamaz.
Listenin sıralama tipi bilgisi geçersizdir.
MPAY-ERR-9587
Client Id And Password Is Wrong
İstemci Id ve şifre bilgisi yanlıştır.
MPAY-ERR-9588
SnCode Is Null
SnCode bilgisi boş olamaz
MPAY-ERR-9589
Merchant Name Is Null
Merchant Name bilgisi boş olamaz
MPAY-ERR-9590
Service Name Is Null
Service Name bilgisi boş olamaz
MPAY-ERR-9591
Payment Type Format Is Not Valid
PaymentType formatı geçersiz
MPAY-ERR-9593
Service Category Name Is Null
Service Category Name bilgisi boş olamaz
MPAY-ERR-9594
Service Category Name Is Too Long
Service Category Name bilgisi çok uzun
MPAY-ERR-9595
ThisRecordAlreadyExists
Kayıt zaten var
MPAY-ERR-9596
ThisRecordDoesNotAlreadyExist
Kayıt zaten yok
MPAY-ERR-9607
Limit Not Found
Limit bulunamadı
MPAY-ERR-9566
MPAY-ERR-9567
MPAY-ERR-9568
MPAY-ERR-9569
Saniye cinsinden maksimum ortalama SMS gönderim-alım
zaman farkı bilgisi boş olamaz.
Maksimum bekleyen SMS miktarı bilgisi boş olamaz.
PIMS
Page 27 of 28
.
Valid agreement required.
PIMS
Partner Reference
Project ID No.:
MPAY-ERR-9608
Parameter Key Length Is Too Long
Parameter Key bilgisi çok uzun
MPAY-ERR-9609
Parameter Value Length Is TooLong
Parameter Value bilgisi çok uzun
MPAY-ERR-9610
Parameter Description Length Is Too Long
Parameter Description bilgisi çok uzun
MPAY-ERR-9612
Page Index Is Less Than Or Equal To Zero
Page Index bilgisi 0 veya daha az
MPAY-ERR-9614
Page Size Is Less Than Or Equal To Zero
Page Size bilgisi 0 veya daha az
MPAY-ERR-9615
Parameter Key Invalid
Parameter Key değeri geçersiz
MPAY-ERR-9616
Response Code Lenght Is Too Long
Response code değeri tanımlı olandan uzun.
MPAY-ERR-9617
Language Id Is Less Than Or Equal To Zero
LanguageId 0 veya daha az
MPAY-ERR-9618
Response Code Not Found
Response code bulunamadı
MPAY-ERR-9995
Unknown Language Code
Lisan tanımlı değildir.
MPAY-ERR-9996
Technical Exception
Teknik hata.
MPAY-ERR-9998
ASB Validation Error
Avea entegrasyonu validasyon hatası.
MPAY-ERR-9999
Unknown Response Code
Hata tanımlı değildir.
PIMS
Page 28 of 28
.
Valid agreement required.
Download

PIMS Micropayment Partner Reference