![]() |
WARNING: If you are using NetBilling for proceccing, you are losing 50% of sales
If you process or sell through NetBilling, you are losing 50% of sales, because NetBilling is outdated and doesn't support IPV6 protocol (customer IP)
All IPV6 members (about 50%) are getting "hard declined". So if you are an affiliate program or a regular webmaster, you are losing money. :2 cents: |
Wow that's pretty bad if true.
People with IPv6 addresses should also have an IPv4. But I guess what you're saying is that the web server supports IPv6, but the NetBilling backend system has a bug that rejects all IPv6 joins? |
https://clip2net.com/clip/m84465/65200-clip-44kb.png
IPV6 not getting thru: https://clip2net.com/clip/m84465/cd87d-clip-29kb.png 2020, HELLO ? |
uf, it is not a good business strategy
|
Quote:
The vast majority are behind NAT on mobile networks with IPv4 IPs... They may be using IPV6 within the internal network but are still displaying IPv4 ips. Even google isn't getting 50%... https://www.google.com/intl/en/ipv6/statistics.html |
Seems more of a Nats issue than Netbilling. Many applications don't support IPV6 yet. If Netbilling doesn't support IPV6 yet, Nats shouldn't sent the IPV6 address.
You (Nats) should just send the surfer's IPV4 address to Netbilling instead of their IPV6 address and there won't be any issue? Everyone that has an IPV6 address also has a IPV4 address as fallback Edit. or just ask your host to only use their IPV4 address and ignore the IPV6 address Edit 2. I do agree that Netbilling is pretty outdated and should support it, but at this time there is no reason to not send the IPV4 address instead of the IPV6 address, and your host and can easily fix that, just ignore the ipv6 and use the ipv4 instead |
Quote:
We are looking at the sales stats, and 50% of our Netbilling MIDs are not coming thru (Hard Decline). Our secondary prodessor Vendo is picking them up. |
NETbilling is a member here:thumbsup Hopefully he notices this thread and makes a comment ?:helpme
|
Quote:
|
Mitch paged.
|
Mitch is MIA.
|
Quote:
Thanks, Mitch |
Quote:
|
Quote:
|
Quote:
I just looked at the log of a US campaign I have running on Google traffic. For yesterday, out of 840 ips logged only 13 are IPV6! This number sounds pretty low so I suppose that only traffic NOT SUPPORTING v4 are actually showing as V6 ?? This would mean you are losing are 1.5% of your sales and not 50... |
Quote:
|
Quote:
|
Quote:
But why not disable IPV6 for now until Netbilling supports it? Many major products don't support IPV6 yet, not just Netbilling. It's nice that Nats supports it, but if it's not compatible with your biller just ask you host to disable IPV6 and you won't lose any sales anymore. |
Quote:
|
Quote:
I just posted a heads up for people with only one gateway. Quote:
|
Bump for those that use NB
|
Quote:
|
Quote:
Your host can just disable IPV6 and it will use the visitors IPV4 address instead and problem is solved. IPV6 is not yet fully supported by so many web applications and devices, there is still always a IPV4 fallback for every IPV6 user. |
Quote:
|
Quote:
|
All times are GMT -7. The time now is 03:24 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc