[bisq-network/roles] Payment Method Maintainer (#38)

Sat Jan 30 05:00:35 CET 2021

# Cycle 21 Report

This is my third cycle as Payment Method Maintainer. I think I am beginning to emerge from the organization / getting to grips with everything stage, and am starting to see a little more progress now in terms of things being delivered.

I am enjoying the role and can see a more clear path of what can be achieved in the coming year.

## Keybase #buy-bitcoin

Following my proposal to [Use Keybase to increase accessibility to Bisq for new traders with no funds for security deposit, trading and mining fees](https://github.com/bisq-network/proposals/issues/283) I have started developing this channel. I have completed two trades as a result of messages there. It is still very much a work in progress and I have started to draft a Wiki to help set out rules: https://bisq.wiki/Keybase-Buy_Bitcoin

The fact these trades rely on trust makes me want to ensure the documentation is on-point to ensure traders are both aware of the risks, and understand how to vet a potential trade partner.

I have not worked out how to pin a message in a Keybase channel so if anyone knows how to achieve this please let me know.

## TransferWise problems and removing Trade IDs

Unfortunately I know of at least 8 Bisq users that had their TransferWise closed over the course of a few days. It is speculated that TransferWise became aware of Bisq usage either through social media or a user contacting TW support. It is assumed they were then able to link the Bisq trades by the associated trade IDs. This is a real shame as TransferWise started off so well. I think it also demonstrates how more careful consideration needs to be given to trades that start and end with the same payment provider (eg Revolut, Uphold, PopMoney, N26 etc). 

To address the Trade ID concerns the discussion that was restarted last month about [Add option to make trade 'reason' less obvious](https://github.com/bisq-network/bisq/issues/2869) became more important and ultimately it was decided that is would be best to remove Trade IDs altogether. Hopefully this will help TransferWise become a viable payment method again, and also reduce the chance of a mass closure of accounts occurring on TW or other platforms.

## Community

I have been active on Keybase, Reddit and Github with regards discussion of all thing payment method related.

## Liaising with Devs

I have worked with a number of Devs to deliver the addition of new payment methods:

- [SWIFT](https://github.com/bisq-network/bisq/issues/1789)
- [Cash by Mail](https://github.com/bisq-network/bisq/issues/1101)

And changes to existing ones where needed:

- [Amazon eGift Cards](https://github.com/bisq-network/bisq/issues/5098)
- [MoneyBeam N26, Uphold, PopMoney](https://github.com/bisq-network/growth/issues/212)
- [SEPA](https://github.com/bisq-network/growth/issues/209)
- [TransferWise](https://github.com/bisq-network/bisq/issues/4931)

All the above, apart from SWIFT, will have been completed and will be delivered with the next release. 

## Liaising with Mediators

No real issues. Many thaks to @Bisq-knight who made me aware of the Amazon eGift Card issue.

## Promote new payment methods on various channels

I held off on this due to the TransferWise issue. I am considering how best to market new payment methods. It seems TransferWise made a comment on one of the Twitter posts about cryptocurrencies being against the terms of service. I think making users aware of new methods, but not the payment provider, would be good. Maybe a news/updates section could be added to the new UI bisq-network/projects#47 I assume a basic Tor html browser  / reader would be possible?

I need to consider how best to market payment methods. It is a work in progress. I have not really got started yet.

## Prioritization of payment methods for addition

I am working on this at present. First job was to produce a list of

- [Proposed payment methods](https://github.com/users/pazza83/projects/1)
- [Payment methods requiring editing](https://github.com/users/pazza83/projects/3)
- [Existing payment methods](https://github.com/users/pazza83/projects/2)

My inital plan was to score the payment methods based on how closed they meet the criteria to be added.

Now I am leaning more to batching payment methods per country / currency. This would make it easier to promote to new users and increase liquidity. I think this will be my preference. I know Colombian, Venezuelan and Brazilian users have been waiting for a long time for more access to their markets. I am keen to address their requirments. I also made a batch of proposals for some more EUR and USD options, as well as three new Indian payment method options.

## Develop a process for payment methods to be added

I am trying to stick to the processes I proposed for editing and adding new payment methods. It seems to be going well and I am hopeful I will meet the estimated timelines.

https://github.com/bisq-network/growth/issues/206
https://github.com/bisq-network/growth/issues/207

The text for the [New payment method' GitHub issue](https://github.com/bisq-network/growth/pull/214) has now been updated so is in keeping with my proposed [requirements to consider when adding new payment methods.](https://github.com/bisq-network/bisq/issues/4757#issuecomment-727711700) 

## Current state of payment methods in numbers

29 payment methods available to Bisq users.
2 payment methods are being added (CBM and SWIFT)
10 payment methods have been discounted
19 payment methods are being discussed on GitHub
15 payment methods are yet to make it to GithHub issue proposal stage.

## Find payment methods to support Bisq's growth.

This month I proposed the following payment methods for addition:

### EUR - Goal to increase liquidity in existing popular markets

- [Add Bizum as a new payment method (popular in Spain)](https://github.com/bisq-network/growth/issues/222) 
- [Add Verse as a payment method (popular European payment app)](https://github.com/bisq-network/growth/issues/223)
- [Add Monese as a payment method (popular mobile bank app in UK and Europe)](https://github.com/bisq-network/growth/issues/227)

### USD - Goal to increase liquidity in existing popular markets

- [Add Venmo as a payment method](https://github.com/bisq-network/growth/issues/221)
- [Add Strike App as a new payment method](https://github.com/bisq-network/growth/issues/220)
- [Add ACH Transfer - USA as payment method](https://github.com/bisq-network/growth/issues/219)
- [Add Domestic Wire Transfer - USA as payment method](https://github.com/bisq-network/growth/issues/218)
- [Add TransferWise-USD as a payment method](https://github.com/bisq-network/growth/issues/217)
- [Add payment method: ATH Móvil (Puerto Rico)](https://github.com/bisq-network/bisq/issues/1868)

### INR - Goal to increase liquidity in less popular popular markets

- [Add Unified Payments Interface (UPI) as a payment method (popular mobile payment service in India)](https://github.com/bisq-network/growth/issues/225)
- [Add Immediate Payment Service (IMPS) as a payment method (popular mobile payment service in India)](https://github.com/bisq-network/growth/issues/224)
- [Add PayTM as a payment method (popular mobile payment service in India)](https://github.com/bisq-network/growth/issues/226)

I also received positive feedback from Reddit users on a post on [r/BitcoinIndia](https://www.reddit.com/r/BitcoinIndia/comments/l3jru5/any_bisq_users_from_india_here/) 

I have also researched many more. Concentrating my efforts for now on multi-currency payment methods.

Next month I will propose more. I understand that for some it might be frustrating to see multiple new payment methods being proposed when others are yet to be actioned.  Fear not, there is a method to the process! I am keen to get everything that could be added onto GitHub for discussion before. It will be another month or so before this is complete. This way I will ensure that payment methods can be prioritized according to region . currency / user demand / feasibility etc. In the long run it will also allow me to cover more ground in less time and therefore result in more and better payment options for current and future Bisq users.

## Wiki

One of my learning from last cycle was to get wikis online in preparation for new payment methods to be added. Therefore, I will try to stay ahead of the new Bisq releases/

This cycle I have completed a draft [wiki for Cash by Mail](https://bisq.wiki/Cash_by_mail) - in preparation of it being added

I have also started the [wiki for using keybase buy-bitcoin](https://bisq.wiki/Keybase-Buy_Bitcoin)

## Payment method volume/ KPIs

I have not started to build this into my process yet.

## Future tasks

These are some of the other things I am yet to action:

-  Action / take ownership of current GitHub issues regarding payment method changes / additions

- Create Wikis for all payment methods. 

- Complete analysis of existing payment methods and can see some are under utilized. I would like to make sure this is not due to lack of understanding / marketing of the specific payment methods.

- Check changes and updates against the proposal I made to [Fix various 'account management' usability issues in the Bisq client to optimize for traders with multiple fiat and altcoin accounts ](https://github.com/bisq-network/bisq/issues/4837)' 

## Other comments

I feel like I have managed to get understanding of the role. It will likely be another cycle before I am fully on it. Apologies to everyone that have made proposals recently and are keen to see some action. I am keen to get everything added once I have taken stock of everything that needs to be done. I am positive the work being done in the first quarter of this year will make things a lot smoother for the rest of 2021.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/38#issuecomment-770152346
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210129/80be2f5e/attachment-0001.htm>