⌨️Paymentwall

Learn how to set up Paymentwall.

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.

Test environment setup

i'mport Admin console→ Payment integration → Test settings → Select PG (Paymentwall) → Paymentwall -> Add
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).

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.