# Paymentwall
### Widget (payment window) payment
{% hint style="info" %}
**What is Paymentwall widget?**
Paymentwall is an overseas PG with a different payment environment than domestic PGs. Unlike the domestic environment where authenticated payments are common, non-authenticated payments are more common overseas. Non-authenticated payments are made in the Paymentwall payment window called a widget.
{% endhint %}
{% tabs %}
{% tab title="Test" %}
### **Test environment setup**
1. [i'mport Admin console](https://admin.iamport.kr)→ **Payment integration** → **Test settings** → Select PG (**Paymentwall**) → **Paymentwall** -> **Add**
2. Check the auto-generated test MID value and click **Save**
> * Test payments incur **real payment on the actual credit card number**, and you must **cancel the transaction** afterwards.
> * Depending on each country's payment method policy, there may be countries/payment methods that **cannot be cancelled (refunded)**.
> {% endtab %}
{% tab title="Live" %}
### Live environment setup
1. **Payment integration -> Live settings**
2. Select PG (**Paymentwall**) → **Paymentwall** -> **Add**
3. Enter the **Project Key/Secret Key** issued by Paymentwall upon contract signing.
**After setting Test mode to OFF**, enter the information for the live account issued by Paymentwall after passing inspection.
> You must apply via the following **sign up page for i'mport**:
>
> * [**https://api.paymentwall.com/pwaccount?source=import**](https://api.paymentwall.com/pwaccount?source=import)
>
> (Signing up via other routes will cause **payment integration issues.**)
> {% endtab %}
> {% endtabs %}
{% hint style="info" %}
**Note - Paymentwall payment integration flow**
Result response for all payment requests through Paymentwall must be processed through i'mport **webhook** because **Paymentwall transaction flow is different from domestic PGs**. In the payment flow, the final result response for all transactions requested to Paymentwall is sent to i'mport via pingback (webhook), and i'mport sends it to the merchant via webhook.
The cancellation request **processing flow is also different from domestic PGs** due to Paymentwall's unique cancellation processing logic. The flow is identical to that of direct integration with Paymentwall without using i'mport. Unlike domestic PGs, Paymentwall does not immediately send the result of the cancellation request. It first creates a cancellation ticket for the request and processes each ticket one by one. Once processed, the result is sent to i'mport via pingback and i'mports sends it to the merchant via webhook.
Even if you integrate Paymentwall directly by registering a cancellation ticket in Paymentwall, you must process the final result received via pingback (webhook) from Paymentwall.
When using i'mport, you must update the "**Waiting for cancellation**" payment status in your database when you receive the final result via webhook notification.
{% endhint %}
### API Payment
{% tabs %}
{% tab title="Key-in" %}
**Preparing for service**
{% endtab %}
{% tab title="Subscription" %}
**Preparing for service**
{% endtab %}
{% endtabs %}
---
# 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://portone.gitbook.io/docs-en/ready/2.-pg/payment-gateway-settings/undefined-1.md?ask=
```
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.