<p></p>
<blockquote>
<p>Whats usually caused the friction is that nobody writes up a clear and complete spec (which data are required, is anything special) and clearify the chargeback risk.</p>
</blockquote>
<p>Maybe we just need to specify this needs (at something like <a href="https://bisq.wiki/Request_New_Payment_Methods" rel="nofollow">https://bisq.wiki/Request_New_Payment_Methods</a>) and make Growth team responsible of research people with feet on the ground, necessary data, attending the requests and contacting with devs when previous process is complete to proceed to implement this payment method.<br>
What I mean is that I think that the needs of this role aren't so specific that, without proper guidance, anyone at Growth or Support could proceed take the tasks that a Payment Methods Maintainer should have. From growth we could develop bounties for unknown regions, just like we did for market makers.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/proposals/issues/252#issuecomment-679960486">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNV7C3ZXULK5O65NIY3SCOL5XANCNFSM4QIZUZ3A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNRDNRSKKKBXHYUXNM3SCOL5XA5CNFSM4QIZUZ3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFCDV7JQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/proposals/issues/252#issuecomment-679960486",
"url": "https://github.com/bisq-network/proposals/issues/252#issuecomment-679960486",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>