API

Docs

Support

Sign in

Try Citcon Sandbox Right Now

API Reference​

Citcon Integration APIs provide easy to use interfaces to fulfill all kinds of online payment needs. Citcon supports Alipay, WeChat Pay, UnionPay, and all kinds of Credit Card products. There are two types of integration provided: a simple yet flexible Citcon Hosted Online Payment (CHOP) method which helps merchants to get integrated fast and reduces PCI Compliance burden for merchants; and a classic backend API integration which provides the utmost granularity and flexibility but may require some development effort on merchant side.

API Reference

							
					
https://citconpay.com/				
			

This website represents the domain for Citcon’s production site.

							
					
https://uat.citconpay.com/				
			

Please note that in the examples in this documentation, the testing site is used instead of the production site.

Citcon Hosted Online Payment

The Citcon Hosted Online Payment (CHOP) provides a flexible, secure and easy way for shoppers to purchase goods and services:

Shoppers go to your site, where they select and add the desired items to their shopping cart.

When they are ready to checkout to pay and finalize their order, they are redirected to the hosted payment page, where they enter the necessary details to complete the payment.

After submitting the payment information, they are redirected back to your web site, where they can land on a summary information page displaying the result of the payment.

Our forms are mobile-optimized and designed to reduce friction in your customer experience. You can use CHOP’s payment form template technology to create a brand-consistent, seamless checkout experience for your shoppers.

Why Use CHOP (Citcon Hosted Online Payment)

You always need to put your best foot forward and present the perfect image to your shoppers in order to demonstrate that you are a top-notch merchant. In order to achieve this, many merchants choose to integrate to a payment processor via an API so that that they can build a fully customized checkout experience, rather than using an out-of-the-box solution.

The drawback to this, of course, is that it usually means that you will have a higher PCI compliance burden because you are dealing directly with sensitive payment information like credit card numbers.

Citcon’s hosted payment helps you reduce the PCI compliance burden, so you can spend more time providing better e-commerce experience.

CHOP also provides a single unified API interface for various payment methods Citcon supports, including credit cards, Alipay, WeChat Pay. This means that, even though these payment methods are from different countries, have a vastly different processes, CHOP helps you simplify integration.

A Word On PCI Compliance

*Do I have to get PCI certified?

If you accept credit cards from your customers then, yes. However, CHOP helps you reduce PCI Compliance complexity and work.

*Which level of PCI Compliance do I need?

PCI certification takes two forms: Self-assessment (i.e. do-it-yourself) or hiring a third party QSA (Qualified Security Assessor). Though there are obvious advantages to self-assessing, including effort and cost, your ability to self-asses is dependent on your annual transaction volume and is reflected in the resulting level of PCI certification (1-4) you attain.

The following table describes the relationship between your transaction volume, required assessment approach, and level of certification:

If you havethen you canto achieve
less than 20,000 online transactions per yearself-assessPCI Level 4 certification
between 20,000 and 1 million online transactions per yearself-assessPCI Level 3 certification
between 1 million and 6 million online transactions per yearself-assessPCI Level 2 certification
over 6 million online transactions per yearhire an independent assessor (QSA)PCI Level 1 certification

*What kind of Self-Assess

If your systemsthen use
do not touch, process or store cardholder data, and do not serve any card collection formsSAQ A-EP
do touch, process or store cardholder dataSAQ D

Chop Reduces PCI Compliance to SAQ A-EP for Merchants

Because CHOP hosts payment forms, handles payment data transmission, and processes payments, it reduces PCI Compliance burden for merchants down to SAQ A-EP.

Integration Architecture

CHOP for Alipay and WeChatPay

CHOP for Credit Cards

CHOP for China UnionPay

Description

  1. After the customer selects which payment method, the merchant’s checkout page posts data to Citcon’s dynamic hosted payment form. Hosted payment form serves UI based on the selected payment method, such as QR code or credit card entry form.
  2. When the customer completes entries on the hosted payment form, Citcon processes payments in the backend.
  3. Upon successful payments, the customer is redirected to a merchant-hosted confirmation page, together with data related to the payment. If the merchant’s confirmation page is capable of handling dynamic input data, it can display personalized confirmation using the merchant’s own data as well as the data sent by Citcon.
  4. Asynchronously, Citcon notifies the merchant’s backend of successful payments.

Integration Details

Integration Details
CHOP expects minimal parameters passed in at entry point, because all the other payment data will be entered by consumers on the hosted payment form.

The parameters are:

authorization

REQUIRED

The merchant-specific token distributed by Citcon at the time of merchant onboarding. Please keep the token secure, as this is used for authenticating merchant API calls.

payment_method

REQUIRED

This is the consumer-selected payment method. Possible values are alipay, wechatpay, cc, ccrecurring and upop. Based on payment method, CHOP renders corresponding payment forms using a merchant-predefined template.

reference

REQUIRED

Merchant’s identifier to locate an order, such as order ID, transaction ID, etc. This is used for merchant to inquire, refund, or internally track order and payment status. Within a merchant, this reference should be unique.

amount

or

trans_amount

ONLY ONE IS REQUIRED

The amount your customers are going to pay is an integer entered in cents. Only numbers without decimal places, thousand separators or $, rounded to cents. For example, if the total amount is $9.99, the amount passed in the API parameter should be 999.

currency

or

trans_currency

ONLY ONE IS REQUIRED

3-character ISO currency code, such as USD

Please use a combination of amount and currency or another combination of trans_amount and trans_currency

ipn_url

Optional

This url is invoked when Alipay, WeChat Pay, UnionPay and or a Credit Card has a successful payment status. It serves the purpose to notify merchants of this successful payment status. This URL should be able to accept HTTP POST with multiple transaction parameters. See next section IPN (Instant Payment Notification) for details.

ext

Optional

Parameter ext is used to pass additional info to Citcon. It should be in json format and urlencoded.

callback_url_success

Optional

This page will be shown to consumers after payment has been successfully completed. It could be a static “Thank you for payment” HTML page, or, could be a dynamic page that shows customized content. The URL here is in the format of https://domain.com/path. The status and other payment related parameters will be appended to the supplied url as query string.

callback_url_fail

Optional

This page will be shown to consumers after payment has timed out. It could be a static “Sorry that payment has timed out” HTML page, or, could be a dynamic page that shows customized content. The URL here is in the format of https://domain.com/path. The status and other payment-related parameters will be appended to the supplied url as a query string. This will be called on the desktop not mobile on timeout. Please note this is really a timeout, not a decline.

mobile_result_url

Optional

If the payment method is either Alipay or WeChat Pay, this page will be shown to consumers inside Alipay or WeChat app, after payment has been successfully completed. It could be a static “Thank you for payment” HTML page, or, could be a dynamic page that shows customized content. The URL here is in the format of https://domain.com/path?query_string. This URL will be loaded directly as-is inside Alipay or WeChat app, without any additional query string parameters.

allow_duplicates

Optional

Allows for multiple transactions to be created from one reference ID. When called, it will create a new transaction with the same reference ID.
If omitted, the call will reference the previously created transaction from the reference ID.

Billing_cycle

Optional

Only valid for recurring payment method.
Billing cycle.

Valid returned values, all caps, and no hyphens:

DAILY
WEEKLY
BIWEEKLY
SEMIMONTHLY
MONTHLY
BIMONTHLY
QUARTERLY
SEMESTER
SEMIANNUALLY
ANNUALLY
SUSPENDED

bill_on_half

Optional

Only valid for ccrecurring payment method together with SEMIMONTHLY as billing_cycle.
Half of the month or Semimonthly indicator.

Valid values are 1 and 2:

1 = the 1st and the 15th of the month
2 = the 15th and the last day of the month

end_of_month

Optional

Only valid for ccrecurring payment method together with MONTHLY or ANNUALLY as billing_cycle.
End of month indicator. Valid values Y or N

You must indicate if the recurring transaction will be processed on the last day of the month for the monthly, bi-monthly, quarterly, semester, and semi-annually billing cycles when the start payment date is any of the following dates:

30-Apr
30-June
30-Sept
30-Nov
28-Feb (non-leap year)
29-Feb (leap year)

You also need to provide the end of the month indicator for the annually billing cycles when the start payment date is any of the following dates:

28-Feb (non-leap year)
29-Feb (leap year)

callback_url_success

CHOP redirects to callback_url_success in the following scenarios:
1) When payment method is Alipay and consumer successfully completes payment in their Alipay app.
2) When payment method is WeChat Pay and consumer successfully completes payment in their WeChat app.
3) When payment method is Credit Card and consumer successfully completes payment in CHOP.
4) When payment method is Recurring Credit Card and consumer successfully sets up credit card for recurring payment.

Merchant’s callback_url_success page can either be static (which ignores all the query string parameters) or dynamic. If it’s a dynamic page, it can handle the following query string parameters:
a. merchant_reference (the same reference merchants use to initiate CHOP)
b. payment_instance_token (CHOP ID that merchants can reference when contacting Citcon)
c. ssl_amount (amount paid in cents, for example, 9.99 is in the form of 999)
d. ssl_result (0 indicates success)
e. ssl_approval_code (only in Credit Card payment)
f. ssl_cvv2_response (only in Credit Card payment; CVV2 validation result, see CVV2/CVC2 section)
g. ssl_avs_response (only in Credit Card payment and when AVS is enabled; AVS validation result, see AVS section)
h. ssl_txn_id (only in Credit Card payment; credit card transaction ID)
i. ssl_card_number (only in Credit Card payment; masked credit card number, such as 4111xxxxxxxx1111)
j. ssl_exp_date (only in Credit Card payment; expiration date in 2-digit month followed by 2-digit year, such as 1020)
k. ssl_txn_time (only in Credit Card payment; credit card transaction time, in mm/dd/yyyy HH:mm:ss AM)

callback_url_fail

CHOP redirects to callback_url_fail in the following scenarios:
1) When payment method is Credit Card and consumer’s credit card gets a decline.
2) When payment method is Recurring Credit Card and consumer’s credit card gets a decline.

Merchant’s callback_url_fail page can either be static (which ignores all the query string parameters) or dynamic. If it’s a dynamic page, it can handle the following query string parameters:
a. merchant_reference (the same reference merchants use to initiate CHOP)
b. payment_instance_token (CHOP ID that merchants can reference when contacting Citcon)
c. ssl_amount (amount paid in cents, for example, 9.99 is in the form of 999)
d. ssl_result (in Alipay/WeChat pay, any value other than 0 is a failed one. In Credit Card transactions, it’s the decline code, see Error Codes section)
e. ssl_cvv2_response (only in Credit Card payment; CVV2 validation result, see CVV2/CVC2 section)
f. ssl_avs_response (only in Credit Card payment and when AVS is enabled; AVS validation result, see AVS section)
g. ssl_txn_id (only in Credit Card payment; credit card transaction ID)
h. ssl_card_number (only in Credit Card payment; masked credit card number, such as 4111xxxxxxxx1111)
h. ssl_exp_date (only in Credit Card payment; expiration date in 2-digit month followed by 2-digit year, such as 1020)
i. ssl_txn_time (only in Credit Card payment; credit card transaction time, in mm/dd/yyyy HH:mm:ss AM)

IPN (Instant Payment Notification)

For a merchant to get notified when a payment has been successfully completed for an order, merchants will provide an ipn_url in chop API call. When payment is successfully completed, Citcon, asynchronously, sends an HTTP POST to this url and passes in the following parameters:
a. id (the CHOP id merchants can reference to when contacting Citcon or initiate a refund)
b. amount (the payment amount in cents. For example, 9.99 is in the form of 999)
c. notify_status (success/fail)
d. currency (ISO 3-character currency code, for example, USD)
e. time (time of payment, in the format of yyyy-MM-dd HH:mm:ss)
f. reference (Merchant’s internal identifier that is used to initiate CHOP)
g. notify_id (the ID related to a notification. Merchants can reference to it when contacting Citcon)
h. approval_code (only available for successful credit card transactions)
i. card_token (only available for successful credit card transactions)
j. result_message (only available for credit card or credit card recurring transactions. detailed messsage of responses)
k. card_number (only available for credit card or credit card recurring transactions. masked credit card number)
l. exp_date (only available for credit card or credit card recurring transactions. expiration date in the format of MMYY)
m. transaction_type (only available for credit card or credit card recurring transactions, such as SALE, RECURRING)
n. recurring_id (only available for credit card recurring transactions, the identifier of a recurring payment setup. This recurring_id can be used to update or delete recurring)
o. fields (a comma separated list of field names included in IPN. for example, “id,amount,notify_status,currency,time,reference,notify_id”)
p. sign (a signature for merchants to authenticate the IPN content)

To verify and authenticate the IPN,
1) Construct a string of all key/value pairs using only keys in the “fields” field,including the “fields” using the format of key1=value1&key2=value2, this list should be sorted alphabetically by keys. Note that neither the keys or values should be URL encoded. For example,
amount=1&card_number=41**********1111&currency=USD&exp_date=1020&fields=id, amount,notify_status,currency,time,reference,notify_id, result_message,card_number,exp_date,transaction_type, recurring_id&id=af37ffeb2f4785a97bba4e0496cc0c80& notify_id=090217A15-6222841B-5363-4FB7-886F-3CE38415ACDD& notify_status=success&recurring_id=af37ffeb2f4785a97bba4e0496cc0c80& reference=7ed9e2623acdd8ffb8c6a90dd605c6cf& result_message=SUCCESS&time=2017-02-09 13:50:42& transaction_type=CCADDRECURRING
2) Append &token=<merchant token> to the end of the string above:
amount=1&card_number=41**********1111& currency=USD& exp_date=1020&fields=id,amount,notify_status, currency,time,reference,notify_id,result_message, card_number,exp_date,transaction_type, recurring_id&id=af37ffeb2f4785a97bba4e0496cc0c80& notify_id=090217A15-6222841B-5363-4FB7-886F-3CE38415ACDD&notify_status=success& recurring_id=af37ffeb2f4785a97bba4e0496cc0c80& reference=7ed9e2623acdd8ffb8c6a90dd605c6cf& result_message=SUCCESS&time=2017-02-09 13:50:42& transaction_type=CCADDRECURRING&token=123456
3) MD5 hash the string above, to compute a signature. This signature should match the sign field posted in IPN.

The sample code to compute a signature here:

function sign_ipn($reply, $token) {
    ksort($reply);
    $flat_reply = "";
    foreach ($reply as $key=>$value) {
        $flat_reply = $flat_reply."$key=$value&";
    }
    $flat_reply = $flat_reply."token=$token";
    return md5($flat_reply);
}

$fields = $_POST['fields'];
$data['fields'] = $fields;
$tok = strtok($fields, ",");
while ($tok !== false) {
    $data[$tok] = $_POST[$tok];
    $tok = strtok(",");
}
$mysign = sign_ipn($data, '123456');

Upon receipt of the notification, merchants can mark their internal databases or system of payment status, or communicate with customers accordingly asynchronously.

The IPN are initiated from Citcon’s servers hosted in AWS. Please make sure that merchants allow HTTP incoming traffic from AWS.

An example of IPN HTTP POST field:
“id”=”0c4486d74a30e87adcbc569156a6084d”
“amount”=”1”
“notify_status”=”success”
“currency”=”USD”
“time”=”2016-11-09 07:49:53”
“reference”=”ABCD123457890”
“notify_id”=”78b6d63503e7a97cb6e8d09c23de5f5n0u”
“fields”=”id,amount,notify_status,currency,time,reference,notify_id”

Example Request

$ curl  https://uat.citconpay.com/chop/chop \
-H "Authorization: Bearer 12341234123412341234123412341234" \
-d payment_method="alipay" \
-d amount=2 \
-d currency="USD" \
-d reference="jkh25jh1348fd89sg" \
-d ipn_url="https://merchant.com/ipn" \
-d callback_url_success="https://merchant.com/success" \
-d callback_url_fail="https://merchant.com/fail" \
-d mobile_result_url="https://merchant.com/mobile_confirm?reference=jkh25jh1348fd89sg" \
-d allow_duplicates="yes"

Example Request

$ curl  https://uat.citconpay.com/chop/chop \
-H "Authorization: Bearer JP2N5DSOBLBYAF0GXUNOQ3IONR16KPMA" \
-d payment_method="alipay_hk" \
-d trans_amount=10 \
-d currency="HKD" \
-d reference="jkh25jh1348fd89sg" \
-d ipn_url="https://merchant.com/ipn" \
-d callback_url_success="https://merchant.com/success" \
-d callback_url_fail="https://merchant.com/fail" \
-d mobile_result_url="https://merchant.com/mobile_confirm?reference=jkh25jh1348fd89sg" \
-d allow_duplicates="yes"

It returns a JSON that contains:
1) result (success or fail)
2) URL (only present when result=success
Upon successful invocation, the URL can be used to redirect consumers to CHOP.

Sample Response:

{"result":"success","url":"https:\/\/uat.citconpay.com\/chop\/landing?q=f9cdf9f1bce99b2db73dcf119"}

To redirect consumers to this URL in PHP code:

<?php
header( 'Location: https://uat.citconpay.com/chop/landing?q=34d7bddb79533932a699bd323f224d49' ) ;
?>

Inquire

This API allows merchants to inquire about the status of a particular payment and/or order.

The parameters are:

ARGUMENTS

authorization

REQUIRED

The merchant-specific token distributed by Citcon at the time of merchant onboarding. Please keep the token secure, as this is used for authenticating merchant API calls. Note this is passed in the header.

q

REQUIRED

The payment token specific to the transaction given to merchants that can inquire.

inquire_method

Optional

Set to “real” to return the details of the transaction.

Response Parameters:

VARIABLES

id

Transaction ID

type

Type of transaction. Possible values are charge (payment) and refund (return of money)

amount

Amount of money charged or returned. This is an integer\ without decimal places or thousand separators. For example, 9.99 is returned as 999

currency

3-character ISO country code, for example, USD.

reference

Merchant’s identifier to locate an order, such as order ID, transaction ID, etc. This is used for merchant to inquire, refund, or internal tracking of order and payment status. Within a merchant, this reference should be unique.

time

Time of transaction in the format of yyyy-MM-dd HH:mm:ss

note

Notes when refund was given, only available when notes was passed in during refund API call.

notify_result

Status of this transaction, can be success, null or expired. null implies Non-expired QR Code / No Payment. expired implies Expired QR Code / No Payment received

Example Request

$ curl https://uat.citconpay.com/chop/refund \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d amount=1 \
-d currency="USD" \
-d transaction_id="3bfa17281b2e20c5e3303e045" \
-d reason="test"

Example Response:

{
	"amount": 1,
	"reference": "test1234",
	"type": "payment",
	"currency": "USD",
	"payment_method": "alipay",
	"notify_result": "success"
}

Refund

This API allows our merchants to make full or partial refunds on successfully paid transactions in the same currency as the original transaction. Merchants may make multiple partial refunds on an original transaction. However, the total refund(s) amount cannot exceed the amount of the original transaction. Refunds are available anytime but there are considerations. Same-day refund transactions tend to be more successful because if you sold something for $1000, you then have $1000 of cash in your till. Therefore, if someone comes and asks for a $350 refund, you have enough cash to refund. However, if that same person wants an $1100 refund, that would not work as you’re still missing $100. The point being the funds from the original transaction are still in your Citcon account therefore you have sufficient funds to perform the refund.

Refunds submitted on subsequent days may fail due to insufficient funds in your Citcon account. For example, When you start your day, you have zero $ in your till. If a customer comes and asks for a refund, you have no cash to give, therefore a refund cannot happen.

Your Citcon account holds funds from payment method(s) transactions settled next day T1 or subsequent days usually T2-T3. Successfully charged transactions are + and refunds are – from your account. Merchants may apply for an exemption when there’s insufficient funds in your Citcon account to refund by submitting a request through support@citcon-inc.com. Merchants may also apply to support@citcon-inc.com to enable refunds within the Citcon Dashboard. Merchants may also submit to support@citcon-inc.com requesting Citcon enable refunds even when their Citcon account balance has insufficient funds.

ARGUMENTS

authorization

REQUIRED

The merchant-specific token distributed by Citcon at the time of merchant onboarding. Please keep the token secure, as this is used for authenticating merchant API calls. Note this is passed in the header.

transaction_id

or

trans_reference

ONLY ONE IS REQUIRED

The transaction ID to refund.

Mechant’s reference number for payment, such as order ID, transaction ID, etc.

amount

or

trans_amount

ONLY ONE IS REQUIRED

The amount the customers are going to refund for. It’s an integer with no decimal places or thousand separators, rounded to cents. For example, if the price for an item is 9.99, the amount passed in should be 999.

currency

or

trans_currency

ONLY ONE IS REQUIRED

3-character ISO currency code

Please use a combination of amount and currency or another combination of trans_amount and trans_currency

reason

Optional

Note or comments for this refund

Example Request

Refund by transaction_id

$ curl https://uat.citconpay.com/chop/refund \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d amount=1 \
-d currency="USD" \
-d transaction_id="3bfa17281b2e20c5e3303e045" \
-d reason="test"

Example Request

$ curl https://uat.citconpay.com/chop/refund \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d trans_amount=10 \
-d trans_currency="HKD" \
-d transaction_id="20190627182000" \
-d reason="test"

Example Request

Refund by transaction_id

$ curl https://uat.citconpay.com/chop/refund \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d amount=1 \
-d currency="USD" \
-d transaction_reference="test1234" \
-d reason="test"

Example Response

{
   "id":"U0000092892-f84960c2a7e3af7",
   "transaction_id":"U0000092891-fe9c93c42d",
   "refunded":true,
   "status":"success"
}


{
   "code":"4071",
   "refunded":flase,
   "status":"Refund amount greater than allowed."
}

Cancel

This API allows merchants to cancel a payment transaction. The valid cancellation window starts from 15 minutes after payment is created till it’s settled. If the original payment is pending, it will be canceled. If the original payment goes through successfully, it will be refunded in full amount. In general, merchants use this API to manage inventory and payment lifecycle.

If a payment has already been settled, merchants should use refund API, instead of cancel API, to return payment funds to consumers.

If a payment has already been canceled, merchants will receive an error message which is “Duplicate cancellation“.

If a cancel request is out of cancellation windows, the merchant will receive an error message which is “Not in cancellation window“.

The parameters are:

ARGUMENTS

authorization

REQUIRED

The merchant-specific token distributed by Citcon at the time of merchant onboarding. Please keep the token secure, as this is used for authenticating merchant API calls. Note this is passed in the header.

transaction_id

or

trans_reference

ONLY ONE IS REQUIRED

The transaction ID to cancel.

Mechant’s reference number for payment, such as order ID, transaction ID, etc.

reason

Optional

Note or comments for this refund

Example Request

Cancel by transaction_id

$ curl https://uat.citconpay.com/chop/cancel \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d transaction_id="3bfa17281b2e20c5e3303e045" \
-d reason="test"
 

Example Request

Cancel by transaction_reference

$ curl https://uat.citconpay.com/chop/cancel \
-H "Authorization: Bearer 1234567890abcdef1234567890abcdeq" \
-d transaction_reference="72f73528a4e90898123" \
-d reason="test"

Example Response

{
   "transaction_id":"81e0172f73528a4e16b726aaf",
   "transaction_reference":"72f73528a4e90898123",
   "cancelled":true,
   "status":"Order cancelled"
}


{
   "transaction_id":"81e0172f73528a4e16b726aaf",
   "transaction_reference":"72f73528a4e90898123",
   "cancelled":false,
   "status":"Cancellation failed"
}

Mobile App Integration

Citcon recommends use of webview to add CHOP to native apps. Because the integration of CHOP in webview is the same familiar method as in web integration, it dramatically saves development effort.

Our forms are mobile-optimized and designed to reduce friction in your customer experience. You can use CHOP’s payment form template technology to create a brand-consistent, seamless checkout experience for your shoppers.

For mobile SDK integration, please contact Citcon at info@citcon-inc.com.

API Endpoint


	      webView = new WebView(this);
	      webView.getSettings().setJavaScriptEnabled(true);  
	      webView.setWebViewClient(new WebViewClient() {  
	      @Override  
	      public boolean shouldOverrideUrlLoading(WebView view, String url) {  
	      if (url.startsWith("weixin://wap/pay?")) {
	      Intent intent = new Intent();
	      intent.setAction(Intent.ACTION_VIEW);
	      intent.setData(Uri.parse(url));
	      startActivity(intent);
	      return true;
	      }
	      return super.shouldOverrideUrlLoading(view, url);
	      }
	      
	      @Override
	      public void onPageFinished(WebView view, String url) {             
	      super.onPageFinished(view, url);
	      }
	      
	      @Override
	      public void onReceivedError(WebView view, int errorCode,
	      String description, String failingUrl) {            
	      super.onReceivedError(view, errorCode, description, failingUrl);
	      }            
	      });
	      
webView.loadUrl("https://uat.citconpay.com/chop");