Pingback New IP Subnet - November 2018
Paymentwall has added a new IP range 126.96.36.199/24 for sending pingbacks - payment notifications. This document describes how merchants can support this new range.
This message is relevant for you if you accept pingbacks only from a whitelisted range of IP addresses.
Please note that Paymentwall libraries (PHP, Ruby, Python, Node.js, Java, .NET) and Paymentwall modules (Magento, WHMCS, WooCommerce etc.) have built-in pingback IP validation against a whitelist. If you use a Paymentwall library or a Paymentwall module, you need to update it to the most recent version. Libraries can be updated using Paymentwall GitHub page, modules (Magento, WHMCS, WooCommerce, etc.) can be updated using Paymentwall Integration Modules page.
Do you need IP whitelisting?
IP whitelisting is an optional technique used for verifying pingbacks that may require maintenance should the IPs ever change. Paymentwall sends a signature along with every pingback. Veryfing the signature is sufficient. If you would like to keep using the whitelist, please follow the steps below. If maintaining a whitelist in future may be challenging for you, you are welcome to remove the IP whitelist check. If you need assistnce - please feel free to contact email@example.com.
Step 1: Adding new IP range.
Please add the following NEW IP range into whitelist by November 16th, 2018, 12:00 PM GMT:
which is a subnet involving all addresses from .0 to .255. View full list of new IPs.
If your application uses firewalls, proxy services, and/or load balancers, these can also restrict server communication with Paymentwall. Here, we kindly request you to update the configurations and whitelist the aforementioned IP addresses.
If you are using a Paymentwall module or library, please update it to the most recent version following the links above.
Please note that the new IP address range will be in effect from November 16th, 2018 at 12:00 PM GMT.
Step 2: Testing.
You can test the new IP addresses inside your Merchant Area under Project Settings and then Test Pingback Tool. Here you have a checkbox to test notifications from new IP range:
Step 3: Activating new IP range.
Once you have confirmed your server supports the updated IP range please activate it immediately inside of Paymentwall. You can do this by switching the “New IP subnet supported” toggle on inside Project Settings inside your Merchant Area:
Step 4: Removing old IP range.
Once you switch your project to New IP Subnet support, you should remove the previously used range of IP addresses supported by Paymentwall: 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124.
If you have any issues and/or inquiries please do not hesitate to contact our team at firstname.lastname@example.org or email@example.com.