Payments in your mobile apps

In summary: Here are the available ways to do this

  1. An in-app payment SDK for Android & Windows Phone – details here and here (sample apps built with it are here)
  2. A workaround Webview-based mechanism for other platforms – details here
  3. Both implementations require that you sign up as Quickteller Merchant, as described here

The WebView or mobile browser approach

You would be provided with a url similar to this

http://testwebpay.interswitchng.com/quicktellercheckout?paymentCode=10425&amount=1000&customerId=0000000009&mobileNumber=080111111111&emailAddress=xxxx@gmail.com&ispopup=true&site=testwebpay.interswitchng.com

The url redirects to the “Pay With Quickteller” payment page. You can programmatically construct the url and launch the browser control of your mobile or desktop application and redirect the page to the url provided. The query not strings needed in the url can be removed.

Query String Fields

  • PaymentCode is mandatory. This value would be provided by interswitch to the merchant
  • “IsPopUp” is mandatory and is either “true” or “false”
  • “Site” is mandatory. This is the domain from which “Pay With Quickteller” is implemented by the merchant. This domain name must be supplied by the customer during setup.
  • “Amount” is not mandatory. This represents the “amount” payable by the customer. If the value is not set, the amount field on the “Pay With Qucikteller” form would be editable by the customer.
  • “CustomerId” is not mandatory. This is value is used for customer identification (e.g. email address, decoder number etc). If the value is not set, the “customerId” field on the “Pay With Quickteller” form would be editable by the customer.
  • “EmailAddress” is not mandatory. If the value is not set, the “emailAddress” field on the “Pay With Quickteller” form would be editable by the customer.
  • “MobileNumber” is not mandatory. If the value is not set, the “customerId” field on the “Pay With Quickteller” form would be editable by the customer