[WXApi registerApp:@"wxd930ea5d5a258f4f" withDescription:@"demo 2.0"];

PayReq *request = [[[PayReq alloc] init] autorelease];
request.partnerId = @"10000100";
request.prepayId= @"1101000000140415649af9fc314aa427";
request.package = @"Sign=WXPay";
request.nonceStr= @"a462b76e7436e98e0ed6e13c64b4fd1c";
request.timeStamp= @"1397527777";
request.sign= @"582282d72dd2b03ad892830965f428cb16e7a256";
[WXApi safeSendReq:request];

- (void)onResp:(BaseResp *)resp {
    if ([resp isKindOfClass:[PayResp class]]) {
        PayResp *response = (PayResp *)resp;
        switch (response.errCode) {
            case WXSuccess:
     	    		//Prompt of successful payment according to server-based query result or API returned data
     	     		NSlog(@"Payment Successful");
            	break;
        	 default: 
           	NSlog(@"Payment Failed， retcode=%d",resp.errCode);
            	break;
            }
	}
}

errCode value list:

Instructions for Android

1. Backend Settings

After the Merchant has successfully applied for an App in the WeChat Open Platform, the Platform will provide an unique APPID to the Merchant. For payment security reasons, the Merchant's app package name and signature must match in the Platform. Only when these are configured properly can payment be initiated. This can be done in “App Platform (應(yīng)用平臺)”->”Android App (Android 應(yīng)用)” on the WeChat Open Platform, as marked in red in Figure 8.8.

Figure 8.8

The App package name is the same as the one set in the configuration file "AndroidManifest.xml" of the app’s project settings. For an example, look at the package name "net.sourceforge.simcpux" in Figure 8.9.

The App signature is the keystore used for compiling according to project's app package name, which should be a 32-bit md5 string generated by a signature tool. If developers install the signature tool on a testing phone, they can run it to generate the app’s signature string, as shown in the strings in green in Figure 8.9. Download a signature tool

Figure 8.9

2. APPID for Registration

The WeChat JAR package should be imported into the App project. Before calling the API, you need to register your APPID with WeChat, as shown below:

Before calling the API, you should register your APPID with WeChat, as shown below:

final IWXAPI msgApi = WXAPIFactory.createWXAPI(context, null);
// Register this app with WeChat
msgApi.registerApp("wxd930ea5d5a258f4f");

3. Call Payment

The Merchant's server calls the Unified Order API (for more information, see Section 9.1 Unified Order) to create an advance transaction. After obtaining prepay_id and signing relevant parameters, the advance transaction data is transferred to the App to start a payment. See below for an example of how to do this:

IWXAPI api;
PayReq request = new PayReq();
request. appId = "wxd930ea5d5a258f4f";
request. partnerId = "1900000109";
request.prepayId= "1101000000140415649af9fc314aa427",;
request. packageValue = "Sign=WXPay";
request.nonceStr= "1101000000140429eb40476f8896f4c9";
request.timeStamp= "1398746574";
request.sign= "7ffecb600d7157c5aa49810d2d8f28bc2811827b";
api.sendReq(req);

4. Payment Result Callback

As shown in the sample included in the SDK, onResp() can be added to WXPayEntryActivity. After completing payment, WeChat will be redirected to Merchant's app and do a callback using onResp(). The Developer receives notifications in this function and determines the returned error code if necessary. If the payment is successful, the payment result shall be queried from the WeChat payment system and shown to Payer. The payment result is subject to the payment notifications from the WeChat payment system and the result returned to the Payer after querying the API. See below for an example on how to do so:

public void onResp(BaseResp resp) {
	if (resp.getType() == ConstantsAPI.COMMAND_PAY_BY_WX) {
		Log.d(TAG, "onPayFinish, errCode = " + resp.errCode);
		AlertDialog.Builder builder = new AlertDialog.Builder(this);
		builder.setTitle(R.string.app_tip);
	}
}

errCode value list: