Tech WARNING: If you are using NetBilling for proceccing, you are losing 50% of sales - GoFuckYourself.com

Lichen · 01-15-2020, 05:16 AM

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.

BigFurry · 01-15-2020, 05:38 AM

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?

Lichen · 01-15-2020, 05:38 AM

IPV6 not getting thru:

2020, HELLO ?

elmy · 01-15-2020, 07:11 AM

uf, it is not a good business strategy

k0nr4d · 01-15-2020, 07:30 AM

Quote:

Originally Posted by Lichen

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.

May I ask where you are getting statistic that 50% of porn consumers are running on IPV6?
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

Konda · 01-15-2020, 07:33 AM

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

Lichen · 01-15-2020, 08:13 AM

Quote:

Originally Posted by Konda

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

NetBilling support themselves comfirmed that they do not support ipv6.

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.

celandina · 01-15-2020, 08:28 AM

NETbilling is a member here

Hopefully he notices this thread and makes a comment ?

247mg · 01-15-2020, 11:48 AM

Quote:

Originally Posted by Lichen

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.

This is very interesting and alraming and need a quick response from MITCH!

baddog · 01-15-2020, 12:06 PM

Mitch paged.

Lichen · 01-15-2020, 12:51 PM

Mitch is MIA.

NETbilling · 01-15-2020, 05:26 PM

Quote:

Originally Posted by Lichen

Mitch is MIA.

Definitely not MIA. Was just alerted of this post. You certainly are not losing 50% sales. I am having engineering tackle this and will reply once I have details, This is the first complaint we have received and we processing thousands of transactions daily.

Thanks, Mitch

Lichen · 01-15-2020, 05:34 PM

Quote:

Originally Posted by NETbilling

Definitely not MIA. Was just alerted of this post. You certainly are not losing 50% sales. I am having engineering tackle this and will reply once I have details, This is the first complaint we have received and we processing thousands of transactions daily.

Thanks, Mitch

You still dont support ipv6 (facts), and we have NATS stats to back it up that it's about ~50% of sales. Good thing we got a backup processor in the cascade. Just update your stuff, it's 2020 already.

klinton · 01-15-2020, 08:06 PM

Quote:

Originally Posted by Lichen

You still dont support ipv6 (facts), and we have NATS stats to back it up that it's about ~50% of sales. Good thing we got a backup processor in the cascade. Just update your stuff, it's 2020 already.

SleepWalker · 01-15-2020, 09:15 PM

Quote:

Originally Posted by Konda

Everyone that has an IPV6 address also has a IPV4 address as fallback

That's what I was thinking.

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...

Lichen · 01-15-2020, 10:23 PM

Quote:

Originally Posted by SleepWalker

That's what I was thinking.

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...

That's not what NATS is showing. We are seeing a lot of these declines.

bean-aid · 01-15-2020, 11:36 PM

Quote:

Originally Posted by Lichen

That's not what NATS is showing. We are seeing a lot of these declines.

I'm sure you have legit point... i'm sure Nats showing only 1.5% has legit point... I'm sure the loss of sales is likely between the 2 and nobody will ever tell the truth

Konda · 01-16-2020, 05:40 AM

Quote:

Originally Posted by Lichen

That's not what NATS is showing. We are seeing a lot of these declines.

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.

Lichen · 01-16-2020, 08:37 AM

Quote:

Originally Posted by beaner

I'm sure you have legit point... i'm sure Nats showing only 1.5% has legit point... I'm sure the loss of sales is likely between the 2 and nobody will ever tell the truth

If it was just a few sales, i wouldnt sweat it.

Lichen · 01-16-2020, 08:38 AM

Quote:

Originally Posted by Konda

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.

Our second cascade is picking them up. Why lose them?

I just posted a heads up for people with only one gateway.

Quote:

Originally Posted by Konda

Many major products don't support IPV6 yet, not just Netbilling.

That's not true at all.

tobedeleted · 01-16-2020, 03:21 PM

Bump for those that use NB

RyuLion · 01-16-2020, 06:44 PM

Quote:

Originally Posted by Lichen

Mitch is MIA.

He's not MIA I ran into him this morning while at xbizshow.com

Konda · 01-17-2020, 12:06 AM

Quote:

Originally Posted by Lichen

Our second cascade is picking them up. Why lose them?

I just posted a heads up for people with only one gateway.

That's not true at all.

Lose them? I don't think you understand how it works.
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.

InfoGuy · 01-17-2020, 08:02 PM

Quote:

Originally Posted by Lichen

NetBilling support themselves comfirmed that they do not support ipv6.

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.

Are the number of your Netbilling transactions about equal to the number of your Vendo transactions?

Google Expert · 01-18-2020, 12:54 AM

Quote:

Originally Posted by InfoGuy

Are the number of your Netbilling transactions about equal to the number of your Vendo transactions?

Yes. About 50/50 lately.

01-15-2020, 05:16 AM	#1
Lichen Tube Master Industry Role: Join Date: May 2004 Posts: 1,639	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.

01-15-2020, 07:11 AM	#4
elmy Confirmed User Join Date: Jan 2005 Posts: 2,287	uf, it is not a good business strategy __________________ The Most Effective Software For Porn Video Upload! Over 370 adult tube sites ready for upload! + Free Virtual Private Server! COME TO UPLOADERS COMMUNITY

01-15-2020, 05:38 AM	#2
BigFurry Confirmed User Industry Role: Join Date: Nov 2003 Posts: 1,520	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?

01-15-2020, 05:38 AM	#3
Lichen Tube Master Industry Role: Join Date: May 2004 Posts: 1,639	IPV6 not getting thru: 2020, HELLO ?

01-15-2020, 07:33 AM	#6
Konda ... Industry Role: Join Date: Apr 2003 Posts: 2,280	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

01-15-2020, 08:28 AM	#8
celandina Too lazy to set a custom title Industry Role: Join Date: Jun 2006 Posts: 10,972	NETbilling is a member here Hopefully he notices this thread and makes a comment ?

01-15-2020, 12:06 PM	#10
baddog So Fucking Banned Industry Role: Join Date: Apr 2001 Location: the beach, SoCal Posts: 107,090	Mitch paged.

01-15-2020, 12:51 PM	#11
Lichen Tube Master Industry Role: Join Date: May 2004 Posts: 1,639	Mitch is MIA.

01-16-2020, 03:21 PM	#21
tobedeleted Pay Per Minute Products Industry Role: Join Date: Nov 2015 Posts: 299	Bump for those that use NB