I'm not sure if there is already a guide for this out there, but i have noticed that many people on sythe attempt "unauthorized chargebacks" With the use of a vpn, after seeing a $300 total loss due to this type of chargebacks within one day on sunday, my partner and i have decided to conduct hours and hours upon research and brainstorming on all ways possible to prevent this major issue from happening. We have found many things relating to this topic and would like to share them with you all, as i'm sure this happens to more than half of you. By the way, credit for all this info to google search, and others.
1 - Didn't Receive my Item
Simply put, a chargeback is when Paypal reverses a transaction. The most common reason for a chargeback is that the buyer never received the good. However, Paypal has a policy that it does not offer chargebacks for virtual items, because there is no actual way of proving if it was sent or not. The note included in a selling line, "This is payment for virtual goods which I have received," is always good at assuring PayPal realizes this. Honestly, people have a really hard time accepting any payment except for gifts because gifts cannot be claimed using this type of chargeback, but we shouldn't be worrying about this type at all on Sythe. I've won a fair deal of disputes just by saying that I was selling a virtual item.
2 - Unauthorized Transaction
This is the WORST type of chargeback. If this type of chargeback comes up, you are nearly defenseless. Nothing you can say will be of much help. This chargeback is technically supposed to prevent stolen PayPal accounts, but on Sythe 99% of the unauthorized claims are faked. This happens by a person using a Virtual Private Network to fake their IP address, and they claim from their normal IP that it was stolen. Yes, this is incredibly illegal, but doesn't stop scammers from attempting it.
Just because you are defenseless against this once it is claimed doesn't mean you can't prevent it. There are many clues to tell if a person will commit an unauthorized transaction fraud. Firstly, if they are offering to pay an absurd amount, it's almost surely a scam. Secondly, if they immediately say "I'll go first" or seem to know more about Sythe than a Newcommer should, it's almost surely a scam. Thirdly, anything else suspicious can clue you off: look at their address on PayPal (if they sent Payment for Goods). If it says Massachusetts and they have broken English, it's probably not really true. Even the most vigilant can still get scammed by this, so limit your transactions on PayPal very low. Almost every single high-ball offer for PayPal only is a scam.
3 - Limited PayPal
If a buyer's person gets limited, then most of his transactions will be refunded to him. There's nothing to do to avoid this except trading with verified PayPal members who trade safely. Read the next section for how to avoid getting limited.
PayPal Limitations
PayPal will limit an account that it decides violates their terms or is abusing some sort of power. On Sythe, a lot of limitations have been popping up, and for two reasons. Firstly, if you're under 18 and cannot verify your PayPal with a bank account, it is almost certainly going to be limited in the future. This limitation is easy to fix if you're 18+, as you can just send them a scan of your drivers license. If you're less than 18, you'll need your parents to contact them and convince them to put you on a student account. In any case, post on the forums if your account is limited and people with experience will be able to help your individual case.
The second reason for limitations is abusing PayPal charge features--namely gifts.
Explanation of why PayPal hates gifts.
These are an interesting phenomenon on Sythe, and I honestly don't understand why it's such a big deal. People think gifts are the only secure way of PayPal, but 90% of chargebacks are because an unauthorized claim anyway.Gifts do not reduce your risk of an unauthorized account chargeback! They also don't help much in a "did-not-receive" claim because virtual goods are not covered in PayPal's buyer protection policies. So, always use the appropriate payment type for what you are selling. If you're skilling, make them pay Payment for Services. If you're selling goods, make them pay Payment for Goods. It's always good to take screenshots of your trades as evidence, but really all you need to prove is that the person paid for virtual items and you'll win the claim.
If your PayPal is limited because you abused gift payments, you're in a much deeper pit. Some of the highest traders on Sythe have been limited because of this, and I still see many of them limited to this day. You have to verify with them extensively that you own your account, etc. etc. etc. Definitely post on the forums for help, as these limitations do need to dealt with on a case-by-case basis.
Now to better understand what a VPN is
A virtual private network (VPN) extends a private network and the resources contained in the network across public networks like the Internet. It enables a host computer to send and receive data across shared or public networks as if it were a private network with all the functionality, security and management policies of the private network.
This is done by establishing a virtual point-to-point connection through the use of dedicated connections, encryption, or a combination of the two.
The VPN connection across the Internet is technically a wide area network (WAN) link between the sites but appears to the user as a private network link—hence the name "virtual private network".
Early data networks allowed VPN-style remote connectivity through dial-up modems or through leased line connections utilizing Frame Relay and Asynchronous Transfer Mode (ATM) virtual circuits provisioned through a network owned and operated by telecommunication carriers such as AT&T or Verizon. These networks are not considered true VPNs because they passively secure the data being transmitted by the creation of logical data streams. They have given way to VPNs based on IP and IP/Multiprotocol Label Switching Networks (MPLS) based VPNs due to significant cost-reductions and increased bandwidth provided by new technologies such as Digital Subscriber Line (DSL)and fiber-optic networks.
VPNs can be either remote-access (connecting an individual computer to a network) or site-to-site (connecting two networks together). In a corporate setting, remote-access VPNs allow employees to access their company's intranet from home or while traveling outside the office, and site-to-site VPNs allow employees in geographically separated offices to share one cohesive virtual network. A VPN can also be used to interconnect two similar networks over a dissimilar middle network; for example, two IPv6 networks over an IPv4 network.
VPN systems can be classified by:
the protocols used to tunnel the traffic
the tunnel's termination point, i.e., customer edge or network-provider edge
whether they offer site-to-site or remote-access connectivity
the levels of security provided
the OSI layer they present to the connecting network, such as Layer 2 circuits or Layer 3 network connectivity
Example use of a VPN Tunnel
The following steps illustrate the principles of a VPN client-server interaction in simple terms.
Assume a remote host with public IP address 1.2.3.4 wishes to connect to a server found inside a company network. The server has internal address 192.168.1.10 and is not reachable publicly. Before the client can reach this server, it needs to go through a VPN server / firewall device that has public IP address 5.6.7.8 and an internal address of 192.168.1.1. All data between the client and the server will need to be kept confidential, hence a secure VPN is used.
The VPN client connects to a VPN server via an external network interface.
The VPN server assigns an IP address to the VPN client from the VPN server's subnet. The client gets internal IP address 192.168.1.50, for example, and creates a virtual network interface through which it will send encrypted packets to the other tunnel endpoint (the device at the other end of the tunnel).(This interface also gets the address 192.168.1.50.)
When the VPN client wishes to communicate with the company server, it prepares a packet addressed to 192.168.1.10, encrypts it and encapsulates it in an outer VPN packet, say an IPSec packet. This packet is then sent to the VPN server at IP address 5.6.7.8 over the public Internet. The inner packet is encrypted so that even if someone intercepts the packet over the Internet, they cannot get any information from it. They can see that the remote host is communicating with a server/firewall, but none of the contents of the communication. The inner encrypted packet has source address 192.168.1.50 and destination address 192.168.1.10. The outer packet has source address 1.2.3.4 and destination address 5.6.7.8.
When the packet reaches the VPN server from the Internet, the VPN server decapsulates the inner packet, decrypts it, finds the destination address to be 192.168.1.10, and forwards it to the intended server at 192.168.1.10.
After some time, the VPN server receives a reply packet from 192.168.1.10, intended for 192.168.1.50. The VPN server consults its routing table, and sees this packet is intended for a remote host that must go through VPN.
The VPN server encrypts this reply packet, encapsulates it in a VPN packet and sends it out over the Internet. The inner encrypted packet has source address 192.168.1.10 and destination address 192.168.1.50. The outer VPN packet has source address 5.6.7.8 and destination address 1.2.3.4.
The remote host receives the packet. The VPN client decapsulates the inner packet, decrypts it, and passes it to the appropriate software at upper layers.
Overall, it is as if the remote computer and company server are on the same 192.168.1.0/24 network.
Tunneling protocols can operate in a point-to-point network topology that would theoretically not be considered a VPN, because a VPN by definition is expected to support arbitrary and changing sets of network nodes. But since most router implementations support a software-defined tunnel interface, customer-provisioned VPNs often are simply defined tunnels running conventional routing protocols.
OSI Layer 2 services
Virtual LAN
A Layer 2 technique that allows for the coexistence of multiple LAN broadcast domains, interconnected via trunks using the IEEE 802.1Q trunking protocol. Other trunking protocols have been used but have become obsolete, including Inter-Switch Link (ISL), IEEE 802.10 (originally a security protocol but a subset was introduced for trunking), and ATM LAN Emulation (LANE).
Virtual private LAN service (VPLS)
Developed by IEEE, VLANs allow multiple tagged LANs to share common trunking. VLANs frequently comprise only customer-owned facilities. Whereas VPLS as described in the above section (OSI Layer 1 services) supports emulation of both point-to-point and point-to-multipoint topologies, the method discussed here extends Layer 2 technologies such as 802.1d and 802.1q LAN trunking to run over transports such as Metro Ethernet.
As used in this context, a VPLS is a Layer 2 PPVPN, rather than a private line, emulating the full functionality of a traditional local area network (LAN). From a user standpoint, a VPLS makes it possible to interconnect several LAN segments over a packet-switched, or optical, provider core; a core transparent to the user, making the remote LAN segments behave as one single LAN.[16]
In a VPLS, the provider network emulates a learning bridge, which optionally may include VLAN service.
Pseudo wire (PW)
PW is similar to VPWS, but it can provide different L2 protocols at both ends. Typically, its interface is a WAN protocol such as Asynchronous Transfer Mode or Frame Relay. In contrast, when aiming to provide the appearance of a LAN contiguous between two or more locations, the Virtual Private LAN service or IPLS would be appropriate.
IP-only LAN-like service (IPLS)
A subset of VPLS, the CE devices must have L3 capabilities; the IPLS presents packets rather than frames. It may support IPv4 or IPv6.
[edit]OSI Layer 3 PPVPN architectures
This section discusses the main architectures for PPVPNs, one where the PE disambiguates duplicate addresses in a single routing instance, and the other, virtual router, in which the PE contains a virtual router instance per VPN. The former approach, and its variants, have gained the most attention.
One of the challenges of PPVPNs involves different customers using the same address space, especially the IPv4 private address space.[17] The provider must be able to disambiguate overlapping addresses in the multiple customers' PPVPNs.
BGP/MPLS PPVPN
In the method defined by RFC 2547, BGP extensions advertise routes in the IPv4 VPN address family, which are of the form of 12-byte strings, beginning with an 8-byte Route Distinguisher (RD) and ending with a 4-byte IPv4 address. RDs disambiguate otherwise duplicate addresses in the same PE.
PEs understand the topology of each VPN, which are interconnected with MPLS tunnels, either directly or via P routers. In MPLS terminology, the P routers are Label Switch Routers without awareness of VPNs.
Virtual router PPVPN
The Virtual Router architecture, as opposed to BGP/MPLS techniques, requires no modification to existing routing protocols such as BGP. By the provisioning of logically independent routing domains, the customer operating a VPN is completely responsible for the address space. In the various MPLS tunnels, the different PPVPNs are disambiguated by their label, but do not need routing distinguishers.
Plaintext tunnels
Main article: Tunneling protocol
Some virtual networks may not use encryption to protect the data contents. While VPNs often provide security, an unencrypted overlay network does not neatly fit within the secure or trusted categorization. For example a tunnel set up between two hosts that used Generic Routing Encapsulation (GRE) would in fact be a virtual private network, but neither secure nor trusted.
Besides the GRE example above, native plaintext tunneling protocols include Layer 2 Tunneling Protocol (L2TP) when it is set up without IPsec and Point-to-Point Tunneling Protocol (PPTP) or Microsoft Point-to-Point Encryption (MPPE).
hoping this guide has helped some of you in avoiding money losses due to chargebacks.
1 - Didn't Receive my Item
Simply put, a chargeback is when Paypal reverses a transaction. The most common reason for a chargeback is that the buyer never received the good. However, Paypal has a policy that it does not offer chargebacks for virtual items, because there is no actual way of proving if it was sent or not. The note included in a selling line, "This is payment for virtual goods which I have received," is always good at assuring PayPal realizes this. Honestly, people have a really hard time accepting any payment except for gifts because gifts cannot be claimed using this type of chargeback, but we shouldn't be worrying about this type at all on Sythe. I've won a fair deal of disputes just by saying that I was selling a virtual item.
2 - Unauthorized Transaction
This is the WORST type of chargeback. If this type of chargeback comes up, you are nearly defenseless. Nothing you can say will be of much help. This chargeback is technically supposed to prevent stolen PayPal accounts, but on Sythe 99% of the unauthorized claims are faked. This happens by a person using a Virtual Private Network to fake their IP address, and they claim from their normal IP that it was stolen. Yes, this is incredibly illegal, but doesn't stop scammers from attempting it.
Just because you are defenseless against this once it is claimed doesn't mean you can't prevent it. There are many clues to tell if a person will commit an unauthorized transaction fraud. Firstly, if they are offering to pay an absurd amount, it's almost surely a scam. Secondly, if they immediately say "I'll go first" or seem to know more about Sythe than a Newcommer should, it's almost surely a scam. Thirdly, anything else suspicious can clue you off: look at their address on PayPal (if they sent Payment for Goods). If it says Massachusetts and they have broken English, it's probably not really true. Even the most vigilant can still get scammed by this, so limit your transactions on PayPal very low. Almost every single high-ball offer for PayPal only is a scam.
3 - Limited PayPal
If a buyer's person gets limited, then most of his transactions will be refunded to him. There's nothing to do to avoid this except trading with verified PayPal members who trade safely. Read the next section for how to avoid getting limited.
PayPal Limitations
PayPal will limit an account that it decides violates their terms or is abusing some sort of power. On Sythe, a lot of limitations have been popping up, and for two reasons. Firstly, if you're under 18 and cannot verify your PayPal with a bank account, it is almost certainly going to be limited in the future. This limitation is easy to fix if you're 18+, as you can just send them a scan of your drivers license. If you're less than 18, you'll need your parents to contact them and convince them to put you on a student account. In any case, post on the forums if your account is limited and people with experience will be able to help your individual case.
The second reason for limitations is abusing PayPal charge features--namely gifts.
Explanation of why PayPal hates gifts.
These are an interesting phenomenon on Sythe, and I honestly don't understand why it's such a big deal. People think gifts are the only secure way of PayPal, but 90% of chargebacks are because an unauthorized claim anyway.Gifts do not reduce your risk of an unauthorized account chargeback! They also don't help much in a "did-not-receive" claim because virtual goods are not covered in PayPal's buyer protection policies. So, always use the appropriate payment type for what you are selling. If you're skilling, make them pay Payment for Services. If you're selling goods, make them pay Payment for Goods. It's always good to take screenshots of your trades as evidence, but really all you need to prove is that the person paid for virtual items and you'll win the claim.
If your PayPal is limited because you abused gift payments, you're in a much deeper pit. Some of the highest traders on Sythe have been limited because of this, and I still see many of them limited to this day. You have to verify with them extensively that you own your account, etc. etc. etc. Definitely post on the forums for help, as these limitations do need to dealt with on a case-by-case basis.
Now to better understand what a VPN is
A virtual private network (VPN) extends a private network and the resources contained in the network across public networks like the Internet. It enables a host computer to send and receive data across shared or public networks as if it were a private network with all the functionality, security and management policies of the private network.
This is done by establishing a virtual point-to-point connection through the use of dedicated connections, encryption, or a combination of the two.
The VPN connection across the Internet is technically a wide area network (WAN) link between the sites but appears to the user as a private network link—hence the name "virtual private network".
Early data networks allowed VPN-style remote connectivity through dial-up modems or through leased line connections utilizing Frame Relay and Asynchronous Transfer Mode (ATM) virtual circuits provisioned through a network owned and operated by telecommunication carriers such as AT&T or Verizon. These networks are not considered true VPNs because they passively secure the data being transmitted by the creation of logical data streams. They have given way to VPNs based on IP and IP/Multiprotocol Label Switching Networks (MPLS) based VPNs due to significant cost-reductions and increased bandwidth provided by new technologies such as Digital Subscriber Line (DSL)and fiber-optic networks.
VPNs can be either remote-access (connecting an individual computer to a network) or site-to-site (connecting two networks together). In a corporate setting, remote-access VPNs allow employees to access their company's intranet from home or while traveling outside the office, and site-to-site VPNs allow employees in geographically separated offices to share one cohesive virtual network. A VPN can also be used to interconnect two similar networks over a dissimilar middle network; for example, two IPv6 networks over an IPv4 network.
VPN systems can be classified by:
the protocols used to tunnel the traffic
the tunnel's termination point, i.e., customer edge or network-provider edge
whether they offer site-to-site or remote-access connectivity
the levels of security provided
the OSI layer they present to the connecting network, such as Layer 2 circuits or Layer 3 network connectivity
Example use of a VPN Tunnel
The following steps illustrate the principles of a VPN client-server interaction in simple terms.
Assume a remote host with public IP address 1.2.3.4 wishes to connect to a server found inside a company network. The server has internal address 192.168.1.10 and is not reachable publicly. Before the client can reach this server, it needs to go through a VPN server / firewall device that has public IP address 5.6.7.8 and an internal address of 192.168.1.1. All data between the client and the server will need to be kept confidential, hence a secure VPN is used.
The VPN client connects to a VPN server via an external network interface.
The VPN server assigns an IP address to the VPN client from the VPN server's subnet. The client gets internal IP address 192.168.1.50, for example, and creates a virtual network interface through which it will send encrypted packets to the other tunnel endpoint (the device at the other end of the tunnel).(This interface also gets the address 192.168.1.50.)
When the VPN client wishes to communicate with the company server, it prepares a packet addressed to 192.168.1.10, encrypts it and encapsulates it in an outer VPN packet, say an IPSec packet. This packet is then sent to the VPN server at IP address 5.6.7.8 over the public Internet. The inner packet is encrypted so that even if someone intercepts the packet over the Internet, they cannot get any information from it. They can see that the remote host is communicating with a server/firewall, but none of the contents of the communication. The inner encrypted packet has source address 192.168.1.50 and destination address 192.168.1.10. The outer packet has source address 1.2.3.4 and destination address 5.6.7.8.
When the packet reaches the VPN server from the Internet, the VPN server decapsulates the inner packet, decrypts it, finds the destination address to be 192.168.1.10, and forwards it to the intended server at 192.168.1.10.
After some time, the VPN server receives a reply packet from 192.168.1.10, intended for 192.168.1.50. The VPN server consults its routing table, and sees this packet is intended for a remote host that must go through VPN.
The VPN server encrypts this reply packet, encapsulates it in a VPN packet and sends it out over the Internet. The inner encrypted packet has source address 192.168.1.10 and destination address 192.168.1.50. The outer VPN packet has source address 5.6.7.8 and destination address 1.2.3.4.
The remote host receives the packet. The VPN client decapsulates the inner packet, decrypts it, and passes it to the appropriate software at upper layers.
Overall, it is as if the remote computer and company server are on the same 192.168.1.0/24 network.
Tunneling protocols can operate in a point-to-point network topology that would theoretically not be considered a VPN, because a VPN by definition is expected to support arbitrary and changing sets of network nodes. But since most router implementations support a software-defined tunnel interface, customer-provisioned VPNs often are simply defined tunnels running conventional routing protocols.
OSI Layer 2 services
Virtual LAN
A Layer 2 technique that allows for the coexistence of multiple LAN broadcast domains, interconnected via trunks using the IEEE 802.1Q trunking protocol. Other trunking protocols have been used but have become obsolete, including Inter-Switch Link (ISL), IEEE 802.10 (originally a security protocol but a subset was introduced for trunking), and ATM LAN Emulation (LANE).
Virtual private LAN service (VPLS)
Developed by IEEE, VLANs allow multiple tagged LANs to share common trunking. VLANs frequently comprise only customer-owned facilities. Whereas VPLS as described in the above section (OSI Layer 1 services) supports emulation of both point-to-point and point-to-multipoint topologies, the method discussed here extends Layer 2 technologies such as 802.1d and 802.1q LAN trunking to run over transports such as Metro Ethernet.
As used in this context, a VPLS is a Layer 2 PPVPN, rather than a private line, emulating the full functionality of a traditional local area network (LAN). From a user standpoint, a VPLS makes it possible to interconnect several LAN segments over a packet-switched, or optical, provider core; a core transparent to the user, making the remote LAN segments behave as one single LAN.[16]
In a VPLS, the provider network emulates a learning bridge, which optionally may include VLAN service.
Pseudo wire (PW)
PW is similar to VPWS, but it can provide different L2 protocols at both ends. Typically, its interface is a WAN protocol such as Asynchronous Transfer Mode or Frame Relay. In contrast, when aiming to provide the appearance of a LAN contiguous between two or more locations, the Virtual Private LAN service or IPLS would be appropriate.
IP-only LAN-like service (IPLS)
A subset of VPLS, the CE devices must have L3 capabilities; the IPLS presents packets rather than frames. It may support IPv4 or IPv6.
[edit]OSI Layer 3 PPVPN architectures
This section discusses the main architectures for PPVPNs, one where the PE disambiguates duplicate addresses in a single routing instance, and the other, virtual router, in which the PE contains a virtual router instance per VPN. The former approach, and its variants, have gained the most attention.
One of the challenges of PPVPNs involves different customers using the same address space, especially the IPv4 private address space.[17] The provider must be able to disambiguate overlapping addresses in the multiple customers' PPVPNs.
BGP/MPLS PPVPN
In the method defined by RFC 2547, BGP extensions advertise routes in the IPv4 VPN address family, which are of the form of 12-byte strings, beginning with an 8-byte Route Distinguisher (RD) and ending with a 4-byte IPv4 address. RDs disambiguate otherwise duplicate addresses in the same PE.
PEs understand the topology of each VPN, which are interconnected with MPLS tunnels, either directly or via P routers. In MPLS terminology, the P routers are Label Switch Routers without awareness of VPNs.
Virtual router PPVPN
The Virtual Router architecture, as opposed to BGP/MPLS techniques, requires no modification to existing routing protocols such as BGP. By the provisioning of logically independent routing domains, the customer operating a VPN is completely responsible for the address space. In the various MPLS tunnels, the different PPVPNs are disambiguated by their label, but do not need routing distinguishers.
Plaintext tunnels
Main article: Tunneling protocol
Some virtual networks may not use encryption to protect the data contents. While VPNs often provide security, an unencrypted overlay network does not neatly fit within the secure or trusted categorization. For example a tunnel set up between two hosts that used Generic Routing Encapsulation (GRE) would in fact be a virtual private network, but neither secure nor trusted.
Besides the GRE example above, native plaintext tunneling protocols include Layer 2 Tunneling Protocol (L2TP) when it is set up without IPsec and Point-to-Point Tunneling Protocol (PPTP) or Microsoft Point-to-Point Encryption (MPPE).
hoping this guide has helped some of you in avoiding money losses due to chargebacks.
