QuickWeb Technical Guide
This guide provides technical information about integrating and configuring Paycorps QuickWeb Solution to your website or application. Quick Web is a fast easy way to get processing credit cards.
Features
Very quick and simple API- Very minimal coding knowledge required
Fully customised, responsive payment pages.
Card Tokenization while processing payments
3D Secure Protection
PCI compliant solution
Sample code provided for easy integration
Intended Audience
This document is intended for developers, integrating with their applications or Ecommerce site. It is recommended that someone with web site, HTML and application programming experience reads this guide and implements this solution
General Check List
TLS 1.2 is the minimum HTTPS protocol. Its a MUST to have the TLS 1.2 Protocol. It is strongly recommended that TLS 1.2 with a minimum of sha-265 cipher strength is used as this is now mandatory.
All transaction response codes and responses texts such both approved and declined should be mapped correctly in your Database/Applications
If you are implementing an IFrame , xframe options should be set to allow the paycorp.lk domain
Make sure you log and catch all exceptions within your applications to determine any discrepancies
Transaction Types
Quickweb supports All Visa and MasterCard (Credit/Debits/International Cards). QuickWeb offers the following payment types
Purchase
Purchase and Tokenise- A Token is a string that represents a stored card number. You can use the token to process installment payments and future recurring payments
Preauth- Preauth is a transaction type were the card holders payment is withheld until the merchants completes the payment
Installment Payments
Amount
The "amount" mandatory field is the amount that will be transacted . By default the currency is LKR (Srilanka Rupee). It must be passed in the base unit of the currency. For eg LKR this is cents. For example, $1.00 would be passed as “100”.
Reference Fields
Transaction reference is a unique reference created by Paycorp for all transactions eg Approved, Declined, Time out etc. Client Ref is a unique transaction created by you the client to identify the transaction, eg Invoice number, product number
Credentials to get started
Client ID
Auth token(Please do not share this information in public)
Test Card Details (please click on hyperlink)
Response Code and text Summary- (click on hyperlink)
Console credentials to check your transactions
QuickWeb payment flow
The merchant renders a page in the browser that initialises the payment with data that includes the merchants redirect URL. ....more
Paycorp renders either a hosted payment page or a payment page within an IFRAME on the merchants page.
The payment form is posted to Paycorp.
The browser is redirected to the merchants URL supplied in step 1. This URL will contain a request ID that will be used to confirm the payment. ....more
The merchant posts the payment confirmation request from their server using the request ID.
The payment results are returned to the merchant in response to the payment confirmation request. ....more
Last updated