The Payment Management and Processing or MYGW Payment Management system (MYGW-PM) supports all Chinese credit and debit card brands; and the most popular Chinese e-wallets. MYGW-PM uses a Server Hosted architecture for EC merchants where the client has the option to input their account or card details directly at the merchant or on a ‘redirect’ page hosted by the My Gateway Switch. Some payment methods only support the redirect method, including UnionPay and the Chinese e-wallets, in which case the merchant or PSP does not need to take responsibility for securing card details and only needs to provide MYGW-PM with the payment amount and client ID for any transaction. MYGW-PM transactions use the SSL protocol to provide secure transmission of sensitive data between a client’s web browser and the MYGW-PM system. Settlement and Currency Options Settlement Settlement is the process whereby funds are transferred to merchants’ bank accounts from their PSP. Merchant funds are transferred into their bank account after their transactions have been authorised by the card issuing institution and funds have been cleared by the relevant card scheme network. Settlement usually takes place a number of days after the transactions have been approved, the ‘Settlement Date’. The settlement date is generally agreed between the merchant and their PSP prior to enablement. Currency MYGW supports multiple currencies for transactions and supports PSPs to settle in the currency of their choice. The My Gateway Switch allows merchants and PSPs to specify options for : 1.Presentment Currency – This is the currency the merchant or PSP uses to send transactions to the My Gateway Switch, and is specified in the payment API request as described below. Merchants and PSPs may choose to present in more than one currency – the My Gateway Switch is a multi-currency platform. 2.Settlement Currency – This is the currency used to settle transactions to the PSPs and merchants. It is the currency of the funds deposited into merchant bank accounts as described above. 3.Billing Currency – This is the currency the PSP will bill the merchant in and the currency the PSP fees are denominated in. MYGW-PM Interface Calls The following interface calls are available to the merchant or processor from their platform to access the MYGW-PM functions: 1.Purchase – used to initiate a payment process to allow a client to pay for goods and services provided by the merchant using their debit and credit cards or e-wallets. 2.Query – used to establish the status of a previously executed Purchase. 3.Void/Purchase Cancellation – used to cancel a purchase made prior to the merchant being settled for the purchase. 4.Refund – used to refund money to a client’s card after the merchant has been settled for the purchase. Note that the Void and Refund transactions can also be manually performed by the merchant using the merchant administration system described the My Gateway Merchant Administration User Interface Guide. While the Purchase transaction results in the client being directed to a web page served from the merchant, processor or MYGW-PM platform; the Void and Refund transactions can be processed by the system without client input. A detailed explanation of how UnionPay cards, and Alipay and WeChat Pay wallets are used and processed on the MYGW-PM system is provided in the document Using Chinese Payments. The following contains a more high-level overview of that process and should be read in conjunction that document. Whether a client has been registered as a client on the MYGW-PM system or not by the merchant, the typical steps in a MYGW-PM payment transaction are as follows: Payment Transaction Flow 1. The client selects a commodity or service on the merchant’s website. The merchant then initiates a payment transaction request to the MYGW-PM system using an API request, potentially including the existing or a new client ID and payment amount. 2. MYGW-PM confirms the merchant and client identification and starts the payment process. 3. MYGW-PM navigates the cardholder’s browser to the payment page. On this page, the client may be provided with a QR Code and the client may scan this code using the UnionPay, Alipay or WeChat Applications. Alternatively, the client enters payment information including card number, card verification code and expiry date. In addition, clients using some payment cards may input their cell phone number and perform an additional verification process. .svg) Figure 2. Example QR Code 4. MYGW-PM then packages the payment information and sends a payment request message to the card issuer. 5. The issuer processes the transaction and responds to MYGW-PM after completing authorization. 6. MYGW-PM receives the transaction result from the issuer and informs the client of the result of the transaction, via a callback to the client browser. 7. MYGW-PM then sends the transaction result to the merchant. The merchant can then update its order information and if necessary, provide the relevant goods or services to the client. Email Pay Email Pay is a more secure payment method implemented for some merchants connected to the My Gateway system. This payment method is currently only available for UnionPay cards and wallets; and requires the client to have a valid registered email address stored in their client profile at the MYGW client management system. 1. The client selects a commodity or service on the merchant’s website. The merchant then initiates a request to the MYGW-PM system using an API request and including the new or existing client ID and payment amount. 2. MYGW-PM confirms the merchant and client identification and starts the enablement process. 3. MYGW-PM sends a payment enablement email to the client’s registered email address, or the email address provided for the newly created client. 4. The response to this call will indicate whether the email has been sent to the client’s email address successfully – a response of 210 means the email has been sent. 5. Once the client receives the email and follows the instructions contained therein, the payment process is similar to the one described above under Payment Transaction Flow, from step 3. Alipay and WeChat Pay E-Wallets 1. The client selects a commodity or service on the merchant’s website. The merchant then initiates a request to the MYGW-PM system using an API request and including the existing or new client ID and payment amount. 2. MYGW-PM confirms the merchant and client identification and starts the payment process. 3. MYGW-PM navigates the cardholder’s browser to the payment page. On this page, the client is presented with a unique QR Code and information on the payment amount and payment currency. 4. The client then scans the QR Code using their wallet application payment function, the amount of the transaction is then presented to the client who is asked to approve the transaction and enter their payment password on the Application. The payment information is sent in a payment request message to the card issuer. 5. The issuer processes the transaction and if approved a ‘Success’ message is displayed on the client Application with the amount and a response is sent to MYGW-PM after completing authorization. 6. MYGW-PM receives the transaction result from the issuer and informs the client of the result of the transaction. 7. MYGW-PM then sends the transaction result to the merchant. The merchant can then update its order information and provide the relevant goods or services to the client. The payment interface calls are initiated in the same way as the previously described client management APIs. Described below are the details of the payment management API calls. Client Details The client, the person making the purchase at the merchant’s website, could be a guest (i.e. a one time or sporadic customer), a client managed by the merchant themselves or a client with a record stored on the MYGW-CM server, as described above. Some PSPs and merchants will be required to only initiate payment transactions for clients who have been added to the MYGW-CM server. In this case the payment request will either need to include a valid client ID of an existing client or the details of a new client. In the latter case a new client with the information provided will be created at the server, prior to the payment transaction being initiated. | 
