Scribd
Upload
24 views

B2C Payment API

The Individual B2C Payment feature enables organizations to make payments to individual customers, applicable for various purposes such as salaries and government relief. It supports both registered and unregistered customers, with unregistered customers receiving a withdrawal voucher. The document outlines the process for initiating a payment transaction, including required parameters and example request and response messages.

Uploaded by

Gebretnsae Sibhatu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
24 views

B2C Payment API

The Individual B2C Payment feature enables organizations to make payments to individual customers, applicable for various purposes such as salaries and government relief. It supports both registered and unregistered customers, with unregistered customers receiving a withdrawal voucher. The document outlines the process for initiating a payment transaction, including required parameters and example request and response messages.

Uploaded by

Gebretnsae Sibhatu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.1.

1 Individual B2C payment


The Individual B2C Payment feature allows an organization to pay for individual
customers one by one. Typical applications include paying salaries to many individual
customers, distributing government relief, allowances, and subsidies, providing rewards or
bonuses as merchants for promotion, and paying interest as banks for micro-saving. This
feature is a supplement to the Bulk B2C Payment feature.

1.1.1.1 Initiate an Individual B2C Payment Transaction


(Organization Operator or SP Operator)
The Mobile Money system supports the Individual B2C Payment service that allows an
organization to pay for individual customers. The recipient can be a registered or
unregistered customer. A withdrawal voucher will be sent if the recipient is an unregistered
customer. The recipient (unregistered customer) can withdraw money at an agent using the
voucher. This interface is invoked by a third party of the Mobile Money system to initiate
an individual B2C payment transaction.

Request Parameter Specification


Common field specification

Command Follow InitTrans_{ServiceCode} format


ID
Initiator 
Operator ID of an Organization Operator/PIN/ShortCode

User Name of an Organization Operator/Password/ShortCode

User Name of an SP Operator/Password
PrimaryPar Organization ShortCode
ty NOTE
It is mandatory when the initiator is an SP operator. Otherwise the value remains
empty.

ReceiverPa Customer MSISDN


rty
Requester Not required
Specific parameters in Request/TransactionRequest/Parameters
Mandatory
Parameter Data Type or Optional Description Example
Amount xs:string Mandatory Indicates the payment 10.00
amount. The precision
ranges from the minimum
currency unit to 10^9 *
minimum currency unit. For
example, for CNY, the value
of this parameter ranges
from 1 to 1000000000.00.
Currency xs:string Mandatory Indicates the currency type. CNY
It is specified by using the
Char 3 Code defined in the
Common field specification

ISO 4217 standard.


ReasonType xs:string Mandatory Indicates the reason type for Pay for
a service or transaction. This Individual
field can be set to the reason B2C_VDF_
type alias. Demo
Rules: If this field is not NOTE
configured, the system The values
queries the reason type to be of this
applied to the current parameter is
customizabl
transaction based on
e.
configurations made by the
system operator. If a request
specifies a reason type, the
reason type in the request is
directly used. However, the
reason type must belong to
the requested transaction
type.
This field is mandatory if a
reason type must be
manually specified as
required by the requested
service.

Result Parameter Specification


Specific parameters in Result/ResultParameters

No specific parameter for this result message.

Instance
 Request messages
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:req="http://cps.huawei.com/cpsinterface/request">
<soapenv:Header/>
<soapenv:Body>
<req:RequestMsg><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<Request>
<KeyOwner>1</KeyOwner>
<Identity>
<Caller>
<CallerType>2</CallerType>
<ThirdPartyID>POS_Broker</ThirdPartyID>
<Password>B1YNY8GylVo=</Password>
<ResultURL>http://10.71.109.150:8888/mockResultBinding</ResultURL>
</Caller>
<Initiator>
<IdentifierType>11</IdentifierType>
<Identifier>aaa</Identifier>
<SecurityCredential>iUoiP9iGVwE=</SecurityCredential>
<ShortCode>1008</ShortCode>
</Initiator>
<ReceiverParty>
<IdentifierType>1</IdentifierType>
<Identifier>8613500000000</Identifier>
</ReceiverParty>
</Identity>
<Transaction>
<CommandID>InitTrans_2304</CommandID>
<Timestamp>20130402152345</Timestamp>
<Parameters>
<Parameter>
<Key>Amount</Key>
<Value>10.00</Value>
</Parameter>
<Parameter>
<Key>Currency</Key>
<Value>RON</Value>
</Parameter>
<Parameter>
<Key>ReasonType</Key>
<Value>Pay for Individual B2C_VDF_Demo</Value>
</Parameter>
<Parameter>
<Key>Remark</Key>
<Value>For buy good refund, the original transaction number can be
filled in remark.</Value>
</Parameter>
</Parameters>
<ReferenceData>
<ReferenceItem>
<Key>POSDeviceID</Key>
<Value>POS234789</Value>
</ReferenceItem>
</ReferenceData>
</Transaction>
</Request>]]></req:RequestMsg>
</soapenv:Body>
</soapenv:Envelope>

 Response messages
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Header/>
<soapenv:Body>
<req:ResponseMsg><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<Response>
<ResponseCode>0</ResponseCode>
<ResponseDesc>Process service request successfully.</ResponseDesc>
<OriginatorConversationID>S_X2013012921001</OriginatorConversationID>
<ConversationID>AG_20130129T102103</ConversationID>
<ServiceStatus>0</ServiceStatus>
</Response>]]></req:ResponseMsg>
</soapenv:Body>
</soapenv:Envelope>

 Result messages
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Header/>
<soapenv:Body>
<req:ResultMsg xmlns:req="http://cps.huawei.com/cpsinterface/result"><!
[CDATA[<?xml version="1.0" encoding="UTF-8"?>
<Result>
<ResultType>0</ResultType>
<ResultCode>0</ResultCode>
<ResultDesc>Process service request successfully.</ResultDesc>
<OriginatorConversationID>S_X2013012921001</OriginatorConversationID>
<ConversationID>AG_20130129T102103</ConversationID>
<TranactionID>XD2013012923789234</TranactionID>
<ResultParameters></ResultParameters>
</Result>]]></req:ResultMsg>
</soapenv:Body>
</soapenv:Envelope>

You might also like