[bisq-network/payment-methods] Add payment method: moneygram (#11)

alfsbs notifications at github.com
Wed May 16 14:02:13 UTC 2018

@ManfredKarrer commented on [Mon Dec 04 2017](https://github.com/bisq-network/bisq-desktop/issues/1050)

Investigate and if it fulfills our requirements integrate it as new payment method. 


@alfsbs commented on [Thu Apr 26 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-380742108)

Moneygram requirements (completed from payment methods doc):	


Web: http://www.moneygram.com 
Chargeback risk: Low
Privacy protection to other peer: Low
Mandatory data for a transaction: Name of receiver, reference Number
Duration: About 10 minutes
Region: Global
Fees: Medium to High
Verifiable: https / with Authorisation # and Receiver Last Name
Fraud risk: Low
Conclusion: Considered to be included


MoneyGram never recommends sending money to a stranger. Any monies received by a stranger cannot be recovered and unfortunately you will not get your money refunded back to you. "MoneyGram is very safe and secure when sending to someone you know and trust.


**Receiving options:**
1. Pick up at a Moneygram agent
      - Fields required
            + Name
            + Surname
            + Receiver Country  
2. Bank deposit
3. Cash pick up (limited to few countries)


@ripcurlx commented on [Thu Apr 12 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-380784581)

So If I understood it correctly from your details and what I found on the MoneyGram website, following required fields are necessary to send fiat with MoneyGram:
- Name
- Surname
- Country (Is it really the country or a detailed location)?

The problem we have with this is, that for the receiver to pick up the money she needs the 8-digit reference number. At the moment I don't think we had the case so far that a user was able to add a reference string when clicking on `Payment started`. @ManfredKarrer did we have such case already?

You can also use MoneyGram without the need to share the reference number via bank deposit or mobile wallet.

Doing a bank deposit with MoneyGram would hide the sender of the money, which might make it difficult to arbitrate as you don't know the exact sender of the money. Also I don't know if you're able to add the Bisq transaction id to the MoneyGram bankdeposit transaction.

Sending it via mobile wallet I don't know how this would look like on the reciver end.

Do you know if MoneyGram is used mainly for money transfer, where you have to deposit and pick up at physical locations?


@alfsbs commented on [Thu Apr 12 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-380795446)

Regarding to the Country sometimes MoneyGram requires to indicate the State.

I made a transaction and I did not have the option to include any information (e.g. Bisq transaction id).

I believe that it is used mainly for cash transfer indeed:

"Digital's share of the global remittance industry is still fairly small at 6% — but growth is extremely fast at digital-first startups and legacy companies."



@ManfredKarrer commented on [Tue Apr 17 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-382094626)

For Western Union we define the requirement that the BTC buyer sends by email the tracking nr and the photo of the receipt to the peer. That can be done here as well.
<img width="724" alt="screen shot 2018-04-17 at 13 25 38" src="https://user-images.githubusercontent.com/1449498/38889035-054beb22-4243-11e8-896b-13ce9f77605e.png">


@alfsbs commented on [Tue Apr 24 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384057062)

Here I include the required fields for dev:

**Setting up National Currency Account**

Payment Method = “MoneyGram Agent Pick Up”
Country =
State =
Currency = 
Account Owner Full Name = 
Email = or 
Limitations = ***
Salt for account age verification = ***
Account Name = 

**Create offer to buy BTC**

Enable use of MoneyGram method.
No other changes necessary.

**Create offer to sell BTC**

Enable use of MoneyGram method.
No other changes necessary.

**Buying/Selling BTC**

The buyer of BTC (ie MoneyGram sender) only needs to know the name, surname, email (to send the verification), country and State of the seller. All other instructions should be the same as Western Union.
BTC Seller (ie MoneyGram receiver) only needs to know the buyer’s email address, and unique trade ID / MTCN.

For Western Union we define the requirement that the BTC buyer sends by email the tracking nr and the photo of the receipt to the peer. That can be done here as well.

“When using MoneyGram the BTC buyer has to send the MTCN unique tracking number and a photo of the receipt by email to the BTC seller. The receipt must clearly show the seller’s full name, country and the amount. The buyer will get displayed the seller’s email in the trade process.”


@blabno commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384950656)

@alfsbs are there any other payment methods from Money Gram other than "MoneyGram Agent Pick Up"?


@alfsbs commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384974404)

@blabno there are two other: i) bank account deposit (but this one is the same as in the case of regular bank account deposits, just works as another sender bank); and ii) home delivery, but this is limited to very few and not prioritary countries 


@blabno commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384974838)

I've noticed that in case of western union taker must have the same country and currency in order to take the offer. Should it be the same here?
Also, is the city needed?


@ripcurlx commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384980513)

At the moment you have added the country limit right? @alfsbs Do you know if it can be used for international transfer as well - at least I though so. Regarding Western Union @ManfredKarrer do you know why we have the same country limit in place?


@ManfredKarrer commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-384993088)

Good point. That limit should be probably removed, at least I don't see a reason for it.


@ManfredKarrer commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385008950)

Other question: Is MTCN the correct term for moneygram? It was used at WU. 


@alfsbs commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385081122)

Regarding the country there should not be a limit. Ive done international transfer without any problem. The tracking no. Is called Authorisation # in MG


@ManfredKarrer commented on [Fri Apr 27 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385097854)

@alfsbs I assume for WU the country limitation should be lifted as well. 
@blabno Could you fix that in WU as well? Would require to not extend countrybased account....


@blabno commented on [Mon Apr 30 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385362120)

@ManfredKarrer I've added following changes:
- renamed `MTCN` to `Authorisation #`
- MoneyGramPaymentAccount does not extend CountryBasedPaymentAccount any more

With those changes, I was able to complete regtest trade with accounts from 2 different countries.
Only payment method and currency are now required to be the same.

I'll apply those changes to WU in a separate request.


@ManfredKarrer commented on [Tue May 01 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385594799)

@blabno Thanks!
How does it behave with the currency selection? It should take the currency of the selected country. But here we might have an issue: If you setup your account from Japan then your currency is Yen and only other Japanese users with Yen can take that offer. I have not tested that if it behaves like that but I assume so.
What we might need is similar solution as used in OKPay or others which support a wide variety of currencies. 

@alfsbs Does Moneygram (or WU) convert all currencies to any other, or are there some limitations? How are the fees and hidden exchange rate costs?


@blabno commented on [Tue May 01 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385610837)

@ManfredKarrer currency selection is identical with WU.


@ManfredKarrer commented on [Tue May 01 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385717653)

Yes, but I mean normally we support only one currency so the offer is set in the currency of the account, but for WU/Moneygram we likely want to have any supported currency as they are doing the conversion. But we should check out if that has implications (fees, restrictions) and which currencies are supported. As well if it is a simple model like OKPay where all currencies can be exchanges to each other or if there are some more complicated rules. E.g. EUR can be converted to 20 other currencies but some exotic currency can be only converted to USD and EUR not to other currencies.

@alfsbs Could you investigate that a bit? 


@alfsbs commented on [Tue May 01 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-385792764)

@ManfredKarrer There are the transfer fees (which are determined mainly by the transaction amount) and then an exchange rate. The receiver country sets the limitation of receiving currency (e.g. in Cambodia they only accept KHR and USD). There does not seem to be further limitations (e.g. it is possible to send money from Burundi to Buthan). Find here some screenshots for illustration:
![screenshot 2018-05-01 at 23 13 47](https://user-images.githubusercontent.com/36703333/39494131-8472cf44-4d95-11e8-8092-4f08049f3a24.png)
![screenshot 2018-05-01 at 23 00 13](https://user-images.githubusercontent.com/36703333/39494137-8a1ad054-4d95-11e8-9f59-dc79c3f5b5fd.png)
![screenshot 2018-05-01 at 22 59 04](https://user-images.githubusercontent.com/36703333/39494139-8d7ed9f2-4d95-11e8-8052-3e93cf7af218.png)


@blabno commented on [Wed May 09 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-387702454)

This issue should not be closed yet as it requires 2 more PRs to be merged, one in desktop and one in core.


@cbeams commented on [Wed May 09 2018](https://github.com/bisq-network/bisq-desktop/issues/1050#issuecomment-387704773)

Reopening. This was automatically closed due to the "Fixes: ..." comment in the description of bisq-network/bisq-common#21. Where multiple PRs are involved, it's good to use issue references liberally, but hold off on "Fixes" or "Resolves" or "Closes" language in any PR that cannot on its own actually fix the referenced issue.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/github/attachments/20180516/5dea97ac/attachment-0001.html>

More information about the github mailing list