iDeal would be suitable as well, it's being used only in the Netherlands, but it is the most commonly used method here for all online payments.
It's basically like internet banking, pretty convenient and easy for the end-user, and chargebacks are not possible.
Topic: Payment methods database for P2P Bitcoin exchanges (Read 1583 times)
Please share your experiences about iPay.eu and LeuPay.eu so we can discuss the possibility to use these methods to trade Bitcoins effectively and grow their network if this is a good idea at all - https://bitcointalk.org/index.php?topic=1141625.new#new
Thanks for the recommendation. Do you know how the chargeback risks are?
All "chargeback" occurrences in LeuPay website:
Quote
3. Funding of account and Receipt of money:
Client may purchase or receive e-money in the following ways, as allowed by the Service.
3.8 Client agrees that Client cannot make a successful Chargeback after a funding transaction, on the ground "goods not delivered or similar", as the purchased e-money (purchased goods) is issued (delivered) by iPay upon receipt of funds.
8. Refusal, reversal of unauthorized transaction and reversal of incorrect payment orders:
8.5 Client agrees that iPay may not be always able to reverse the amount of unauthorized transaction or incorrect payment order, in cases, where the deadlines for chargeback or reversal procedures before the Card Organizations have expired or in other cases according to the rules of the respective Card Organization, in which cases iPay shall not owe Reversal or compensation to Client.
8.6 When Client receives a payment, Client is liable to iPay for the full amount of the payment plus any Fees if the payment is later invalidated for any reason. In addition to any other liability, if there is a Reversal, or if Client loses a Chargeback or Claim, Client will owe to iPay an amount equal to the Reversal, Chargeback or Claim and applicable fee as per the Tariff and other charges related to the Reversal, Chargeback or Claim. iPay may debit Client's account to recover any amounts and fees, due by Client in connection to Reversal, or Chargeback or Claim or Reserve, immediately and without prior notice.
11. iPay Acceptance Policy and permissible transactions:
11.2. It is strictly forbidden to use the Service in violation of the Agreement, or for any illegal purposes including but not limited fraud, money laundering, tax evasion or other illegal activities. In particular, Client shall under no circumstances use the Service for activities or execution of transactions, which without limitation involve or may involve any of the following:
(c) Abuse by him of the reversal or chargeback process provided by Client's bank or credit card company; or
(d) Use of the Service in a manner that results in or may result in complaints, disputes, claims, reversals, chargebacks, fees, fines, penalties and other liability to iPay, Branch or Agent of iPay; or
14. Termination of Agreement
14.3. In case of any risk of Damages for iPay, resulting from reversals, chargebacks, claims, fees, fines, penalties, Client's non-compliance with AML/FT or other regulations and other similar liabilities arising from Client's use of the Service, iPay may hold the Client's funds for up to 180 Days even after Termination of Agreement or shorter or longer period, as required by the law, including laws in favor of the consumer. Client will remain liable for all obligations arising under this Agreement even after Termination of Agreement and/or closing of account.
Client may purchase or receive e-money in the following ways, as allowed by the Service.
3.8 Client agrees that Client cannot make a successful Chargeback after a funding transaction, on the ground "goods not delivered or similar", as the purchased e-money (purchased goods) is issued (delivered) by iPay upon receipt of funds.
8. Refusal, reversal of unauthorized transaction and reversal of incorrect payment orders:
8.5 Client agrees that iPay may not be always able to reverse the amount of unauthorized transaction or incorrect payment order, in cases, where the deadlines for chargeback or reversal procedures before the Card Organizations have expired or in other cases according to the rules of the respective Card Organization, in which cases iPay shall not owe Reversal or compensation to Client.
8.6 When Client receives a payment, Client is liable to iPay for the full amount of the payment plus any Fees if the payment is later invalidated for any reason. In addition to any other liability, if there is a Reversal, or if Client loses a Chargeback or Claim, Client will owe to iPay an amount equal to the Reversal, Chargeback or Claim and applicable fee as per the Tariff and other charges related to the Reversal, Chargeback or Claim. iPay may debit Client's account to recover any amounts and fees, due by Client in connection to Reversal, or Chargeback or Claim or Reserve, immediately and without prior notice.
11. iPay Acceptance Policy and permissible transactions:
11.2. It is strictly forbidden to use the Service in violation of the Agreement, or for any illegal purposes including but not limited fraud, money laundering, tax evasion or other illegal activities. In particular, Client shall under no circumstances use the Service for activities or execution of transactions, which without limitation involve or may involve any of the following:
(c) Abuse by him of the reversal or chargeback process provided by Client's bank or credit card company; or
(d) Use of the Service in a manner that results in or may result in complaints, disputes, claims, reversals, chargebacks, fees, fines, penalties and other liability to iPay, Branch or Agent of iPay; or
14. Termination of Agreement
14.3. In case of any risk of Damages for iPay, resulting from reversals, chargebacks, claims, fees, fines, penalties, Client's non-compliance with AML/FT or other regulations and other similar liabilities arising from Client's use of the Service, iPay may hold the Client's funds for up to 180 Days even after Termination of Agreement or shorter or longer period, as required by the law, including laws in favor of the consumer. Client will remain liable for all obligations arising under this Agreement even after Termination of Agreement and/or closing of account.
Source: https://leupay.eu/bgr/en/legal
No, I'm sorry.
https://leupay.eu
They have an internal system to move money, like paypal:
https://bitcointalksearch.org/topic/leupay-free-online-sepa-account-in-malta-978329
it's very cheap, only 0.10 euro cent.
They have an internal system to move money, like paypal:
https://bitcointalksearch.org/topic/leupay-free-online-sepa-account-in-malta-978329
it's very cheap, only 0.10 euro cent.
Thanks for the recommendation. Do you know how the chargeback risks are?
https://leupay.eu
They have an internal system to move money, like paypal:
https://bitcointalksearch.org/topic/leupay-free-online-sepa-account-in-malta-978329
it's very cheap, only 0.10 euro cent.
They have an internal system to move money, like paypal:
https://bitcointalksearch.org/topic/leupay-free-online-sepa-account-in-malta-978329
it's very cheap, only 0.10 euro cent.
LocalBitcoins have already studied it in depth. Just take it from them...
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
Hmm, interesting list/read.
Thanks, I didn't know that even existed.
I do now
Take a look at multisigna. It seems like a great idea. Haven't used it yet but seems solid, and a reasonably anonymously way to trade bitcoin, definitely better than the average exchange if you want some extra privacy.
Security is the most important criteria, so especially the risk for bank charge-backs needs to be investigated very profoundly.
We will use TLSNotary (a cryptographic proof of a https webpage) as primary verification tool in case of disputes, so payment methods where we can use TSLNotary will be preferred (proof of the Fiat transaction is visible on a https webpage - so mobile solutions where there is a webpage with payment history is fine as well).
We will use TLSNotary (a cryptographic proof of a https webpage) as primary verification tool in case of disputes, so payment methods where we can use TSLNotary will be preferred (proof of the Fiat transaction is visible on a https webpage - so mobile solutions where there is a webpage with payment history is fine as well).
Loving the spreadsheet (of course lots of work still to do).
PageSigner is the easier way for people to use TLSNotary; it works on Chrome as well as Firefox now (although we need more testers as usual
) LocalBitcoins have already studied it in depth. Just take it from them...
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
I know that link. We aim to get more details....
LocalBitcoins have already studied it in depth. Just take it from them...
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
Here you go: https://localbitcoins.com/guides/how-to-sell-bitcoins-online#toc3
Some:
- moneypolo.com
- payeer.com
- paxum.com
I can't help about security, but maybe moneypolo has a similar security and chargeback risk as Okpay.
- moneypolo.com
- payeer.com
- paxum.com
I can't help about security, but maybe moneypolo has a similar security and chargeback risk as Okpay.
We would like to ask the community to help us to build up a database for payment methods suited for P2P Bitcoin exchanges (like Bitsquare but it should be valuable information for others as well).
We started collecting information and laid out a template with the most important criteria used to decide if a particular payment method will be supported in Bitsquare.
Here is an overview spreadsheet and a document with more detail information.
Bitsquare is designed as a global exchange and as a community project, so we hope we get enough support to build up that database also for payment methods outside of the regions where we have experience (specially China).
Security is the most important criteria, so especially the risk for bank charge-backs needs to be investigated very profoundly.
We will use TLSNotary (a cryptographic proof of a https webpage) as primary verification tool in case of disputes, so payment methods where we can use TSLNotary will be preferred (proof of the Fiat transaction is visible on a https webpage - so mobile solutions where there is a webpage with payment history is fine as well).
We want to keep that forum as the primary discussion platform for collecting information and then give selective write access to the spreadsheet and document for contributors who provide quality input.
Thanks in advance!
The Bitsquare team
We started collecting information and laid out a template with the most important criteria used to decide if a particular payment method will be supported in Bitsquare.
Here is an overview spreadsheet and a document with more detail information.
Bitsquare is designed as a global exchange and as a community project, so we hope we get enough support to build up that database also for payment methods outside of the regions where we have experience (specially China).
Security is the most important criteria, so especially the risk for bank charge-backs needs to be investigated very profoundly.
We will use TLSNotary (a cryptographic proof of a https webpage) as primary verification tool in case of disputes, so payment methods where we can use TSLNotary will be preferred (proof of the Fiat transaction is visible on a https webpage - so mobile solutions where there is a webpage with payment history is fine as well).
We want to keep that forum as the primary discussion platform for collecting information and then give selective write access to the spreadsheet and document for contributors who provide quality input.
Thanks in advance!
The Bitsquare team
Jump to: