# QuickPay

<figure><img src="/files/ZfLSz8eEGwksjsAVNq6x" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Disclaimers:**

CheckoutChamp does not store any card details for merchants using QuickPay’s Payment Gateway

QuickPay will work for One-time purchases and subscriptions. If using subscriptions you must uncheck the box on the Gateway setup. Also any upsells on QuickPay will redirect to QuickPay again. **QuickPay does not support 1-click upsells.**

QuickPay will work with landers that connect to CheckoutChamp via the funnel builder, Direct API and/or Form-code. This will NOT work with Order Entry.
{% endhint %}

**STEP 1**

Go to **Gateways** > **Gateway Integrations**

**STEP 2**

Scroll down to **QuickPay**

<figure><img src="/files/BkSAQb0rqUedc41Ms07Y" alt=""><figcaption></figcaption></figure>

**STEP 3**

Click the green **Activate** button to activate **QuickPay**

<figure><img src="/files/VmIHGktgxhdnGl8PyrW2" alt=""><figcaption></figcaption></figure>

**STEP 4**

Enter **Apikey** and **MerchantId** in the General Details Section of the Mid Creation Screen. Also choose to enable native 3D Secure processing (**Secure3DS**). If processing only straight-sale products (no subscriptions/rebills) then check the **StraightSaleOnly** box.

**Apikey** and **MerchantId** will be obtained from your QuickPay account.

**Reference:** [**https://quickpay.net**](https://quickpay.net/)

<br>

**STEP 5**

Click the green **Create Gateway** button to save your changes and create the gateway.

<figure><img src="/files/BlE3n14OvJtSuyPYeZPr" alt=""><figcaption></figcaption></figure>

**STEP 6**&#x20;

**CheckoutChamp Builder**

1. Setup the gateway as described in Steps 1-5
2. On the checkout page, edit your checkout button.  Set Title=QuickPay and Action=Submit + Route.  Also set Product if the page is a single-product checkout.
3. Save the page and exit the page builder
4. Draw an arrow leaving the checkout page, if it does not already exist
5. On the arrow settings, choose the QuickPay button
6. Publish

{% hint style="danger" %}
If QuickPay is your only payment option then Card Number should not be on your checkout page.  QuickPay will handle card entry.
{% endhint %}

{% hint style="success" %}
If you are using QuickPay as a separate payment option in addition to standard credit card payments:

* Set your campaign offers to your credit card gateways.
* Your page should have at least 1 “Submit+Route” button for credit card payments and at least one button for QuickPay payments.
* Make the credit card field NOT required on the checkout page.
  * If CC is entered and the customer clicks the CC checkout button, it will run against the credit card gateway set on the offer(s).
  * If no CC is entered and the customer clicks the CC checkout button, then the CRM will respond with “Credit Card is Required”.
  * Whether CC is entered or not and the customer clicks the QuickPay button, the customer will be redirected to QuickPay for payment.
    {% endhint %}

**API Checkout page setup**

Checkout page should be secure HTTPS. A non-secured call to the QuickPay gateway will be rejected.

Pass paySource=PREPAID and prepaidType=QUICKPAY on the import order API call from your checkout page

One option is to use hidden input fields on the page

```
<input type="hidden" name='paySource' value="PREPAID">
```

```
<input type='hidden' name='prepaidType' value='QUICKPAY'>
```

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/quickpay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.