Closed sergfeldman closed 2 months ago
/start
Skipping /start
since no time labels are set to calculate the timeline
/help
- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why.
example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address.
ex1: /wallet 0x0000000000000000000000000000000000000000
ex2: /wallet vitalik.eth
Skipping
/start
since no time labels are set to calculate the timeline
Excuse me, I forgot that the bounty needs to be approved first
Status on 11/13/2023
After the calls with Unlimit and Striga I got information that they require an entity in the EU. They are fine that we are a crypto startup with a small number of users. Both of them have API.
They are interested in continuing communication. Unlimit can at least offer an off-ramp service. More negotiations need to be held to explore cooperation with Striga.
Disrupttech API https://cefi.disrupttech.io/about/api
Disrupttech API https://cefi.disrupttech.io/about/api
@pavlovcik Can you please review this API?
Potentially, it will be possible to use a solution with immediate issuing prepaid cards with really lightweight KYC. An example of immediately issued prepaid cards with lightweight KYC is https://pst.net/ which I reviewed before. This stream requires relatively long negotiations as a solution is planned to be released by the end of 2023.
I estimate the pure time spent for 1 new provider as 2-3 weeks.
You claim that you're fully saturated with this project and perhaps I underestimate the work involved, but my hesitation is that I am a bit skeptical that meetings, reading etc will take 80-120 hours. Perhaps you can confirm a time estimate in hours, of time that you will be actively working on the project? Waiting for replies from them etc I would not consider as part of the "active work time" estimate on the project.
Disrupttech API https://cefi.disrupttech.io/about/api
This seems like a suitable API.
I think that it is essential from a UX perspective to allow us to modify the user's balance on the card. Then, in the near future, we should be able to figure a flow that will automatically collect payment permits on behalf of users, and topping up their card balance) making the earning-to-spending pipeline seamless.
Do prepaid cards allow this? If so, then this can be a practical solution.
I do not fully understand the technical differences as they relate to end-user experience between prepaid, debit, and credit cards. But it surely appears that there are different levels of requirements with these (pre-paid apparently being the most lax for rules, while credit seems to be the most difficult to issue.)
Establishing contact with providers and obtaining offers is a non-standard and sometimes not straightforward task. Each provider has its own flow of interaction with potential partners, as well as its own opportunities and risks. Since we are talking about new providers with which we have no experience yet, it is extremely difficult to correctly predict the time spent.
Time spent on experience with Paymentology and Vault ist:
The total time spent with Paymentology was more than 200 hours, including preparation and performing of about 10 meetings, filling out their forms, signing documents, extensive research of BIN sponsors, studying their documentation, answering questions, and so on.
Total time spent with Vault ist was more than 80 hours, including preparing and conducting 6 calls, studying their documentation and their parent company documentation, trying to reduce prices for us using their referral program, and so on.
The providers I talk to in the scope of this task have already led to unexpected time spending
Sometimes an unexpected time spent is necessary simply to communicate with a provider
I did not include in the estimate for this task time spent waiting for answers from providers, and also significant unexpected time spent.
One of the important things that Mercuryo was interested in was for me to share knowledge about all the providers I had studied. This can significantly save their efforts on competitor research.
Very cool.
PST White Label is offered only for teams and businesses from 200K cards or with a card turnover of 1M USD per year.
If we want to test not white-label card issuing via API then the subscription starts from 179 USD per month. https://pst.net/private https://app.pst.net/app/settings/api
Disrupttech API https://cefi.disrupttech.io/about/api
Disrupttech terms are not attractive for us.
Disrupttech API https://cefi.disrupttech.io/about/api
Disrupttech terms are not attractive for us.
Insane how greedy card issuers are.
Vault ist added the API info to the offer
@Hodlatoor Can you please review the offer from a legal standpoint?
Hi Ser- I would definitely suggest negotiating the onboarding and ongoing / minimum fees as those can become prohibitive rather quickly especially in the early stages When there is not a lot of volume / users. I think there is quite a bit of room to negotiate down on most of their proposed numbers.
On Fri, Nov 24, 2023, 10:23 AM Ser Feldman @.***> wrote:
Vault ist added the API info to the offer https://drive.google.com/file/d/1iJS1rF-ZAKmCk7cfK8AV6Q_Regybugb6/view
@Hodlatoor https://github.com/Hodlatoor Can you please review the offer from a legal standpoint?
— Reply to this email directly, view it on GitHub https://github.com/ubiquity/card-issuance/issues/26#issuecomment-1825559890, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5CGQTB3ZII3P7DUMEJZPGDYGC3WHAVCNFSM6AAAAAA7JYWOACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGU2TSOBZGA . You are receiving this because you were mentioned.Message ID: @.***>
@Hodlatoor Thank you for the input! I've already tried to reduce the Vault ist fees, even explored using their referral program to decrease our costs. I will try again.
Per information obtained on the calls, the initial setup costs with Unlimit will be about 100K, so there is no point in continuing communication for now.
Due to costs, do you think it makes sense to focus on launching with (reloadable) prepaid cards? This seems like the most straightforward answer, particularly if we do not plan to immediate support traditional fiat bank accounts.
The "bank accounts" instead would be in the form of holding Ubiquity Dollars. These represent the "checking account balance"
Behind the scenes of course, we can make money on the underlying collateral.
It's important to have a bridge to real world utility. as long as the costs are not prohibitive and can be swallowed I think it can be considered a significant milestone.
On Sun, Nov 26, 2023, 2:45 AM アレクサンダー.eth @.***> wrote:
Due to costs, do you think it makes sense to focus on launching with (reloadable) prepaid cards?
— Reply to this email directly, view it on GitHub https://github.com/ubiquity/card-issuance/issues/26#issuecomment-1826713430, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5CGQTASOGI734AKLEDH6T3YGLXRHAVCNFSM6AAAAAA7JYWOACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWG4YTGNBTGA . You are receiving this because you were mentioned.Message ID: @.***>
As far as I know, we have long-term plans to develop a Metaverse Bank. To implement these plans, we will need a partner with the appropriate licenses and services. Additionally, partnering with a well-known provider can be beneficial for getting series A funding.
For the initial launch of cards, I am focused on finding an option with the lowest cost. If I don’t find an acceptable option, then we should be ready for compromises, such as prepaid/gift cards.
During the previous rounds, HyperBC was not selected due to the very high initial fee. We are currently discussing the possibility of partnering in other areas in the future (Metaverse bank), as well as attracting other companies (for example, Chainrewardz), which should significantly reduce our initial costs.
They proposed to download their app and try the USD preferred card (details in the doc below). If needed, they can provide a coupon code. There will be a 15.5 usdt initial deposit required to open 1 card.
https://doc-api.hyperpay.io/en/ API https://doc-sdk.hyperpay.io/en/ SDK
Docs https://hyperpayhelp.zendesk.com/hc/en-us/articles/360001107536-User-Guide-for-HyperPay-Download
How_to_add_HyperPay_USD_Preferred_Card_to_Apple_Pay_and_Google_Pay.pdf
The term "Metaverse bank" can be an issue in the future, because it meets the high-risk definition in the financial industry:
Any activity involving the use of shell banks (entities that have no physical existence in the country in which it is incorporated and licensed) or banks with no physical presence in any country that are not licensed by any banking authority
If we want to test not white-label card issuing via API then the subscription starts from 179 USD per month. https://pst.net/private https://app.pst.net/app/settings/api
@pavlovcik Can you please check whether this API meets the requirements for the testing of prepaid cards.
I think again, just check if we can manipulate the card balance
@pavlovcik pst.net Support confirmed that the following operations can be performed via their API triggered by our platform:
It is not possible to review API references before purchasing a Private subscription. The Support replied that the API documentation is available only after activation of the appropriate subscription. I know that the API documentation was available for review previously.
API access lifetime costs 500 USD. For free API access, we need at least a Private Medium plan The first month is 149 USD (regular is 269 USD per month)
As for other providers
We can try to issue free cards from https://combo.cards/ There is a 3% deposit fee It will allow us to test the top-up flow but not the card issuing flow.
There are still some meetings and contacts already planned with other providers.
# Comment event received without a recognized user command.
@@ No latest assign event found. @@
The Support replied that the API documentation is available only after activation of the appropriate subscription.
Seems very sketchy.
They have a lot of typos on their website which also seems pretty sketchy. Check out their KYC/AML policy regarding the Unity States of America https://combo.cards/privacy/
I think my primary concern with these types of businesses is that they are intended for a team to give spending cards to team members. I think this all runs through the business KYC. Although this may be appropriate for a prototype, we certainly would not be able to assume responsibility of every user of our platform. They should probably need to KYC.
# Comment event received without a recognized user command.
@@ No latest assign event found. @@
/start
Warning! | This task was created over 112 days ago. Please confirm that this issue specification is accurate before starting. |
Registered Wallet | 0x16B2433b9CF5FF87dE03dDaEea627C9106Ee117a |
/wallet 0x0000...0000
if you want to update your registered payment wallet address.! action has an uncaught error
+ Evaluating results. Please wait...
Can credit for the research but I think we will stick with reloadly.
I guess we will need to regenerate when we migrate to the new architecture that supports private repos. I always forget.
! action has an uncaught error
@pavlovcik This task was aimed at finding additional options in accordance with the requirements for white-label global crypto card issuance. The full list of requirements is in the report on card issuance that can be found in the folder Reloadly does not fully meet the requirements, as it only provides gift prepaid cards.
As part of this task, negotiations were held and offers were received from a number of providers, the offers can be found in the same folder. For example, Striga among these providers, which you liked as a developer-focused solution.
The task is not yet closed, because I am still negotiating with some providers in order to get lower prices for launching a white-label global crypto card. If we do not plan the white-label global crypto card issuance in the near future, then let's close the task as completed because we got additional options for it. If required, I can create a PR with the results of contacting each provider listed in the task description.
! action has an uncaught error
If we do not plan the white-label global crypto card issuance in the near future,
Yes but its already been a year without results so I think we should just focus on launching the prepaid cards and then eventually go "fully legit" post Series A, which means paying a crazy amount of money to launch a card program. We can get our initial customers with the prepaid cards so I think its fine.
! action has an uncaught error
! action has an uncaught error
I'm happy that a solution with gift prepaid cards is acceptable for the start.
Yes, the prices for launching a card program are high. You can find the updated information from one of the providers HyperBC on global white-label cards. https://drive.google.com/file/d/1bCPr5oHzcazIlmdWMEwGmypgRrnOYunA/view?usp=drive_link https://drive.google.com/file/d/1-Huth5UgHa0f298QWG_XVt1c15izgkzk/view?usp=drive_link
As this task is closed, please clarify whether it will be paid or not.
Yes for all the closed as complete tasks, when we migrate over to the new bot architecture, we can regenerate all the permits in this private repo.
@0x4007 Hey, the project of the cards integration is completed, and this bounty was done several months ago. Please clarify how to receive payment for this bounty.
If the issue is that permits are not generated in private repositories, you might be able to temporarily make this repository open, generate permits, and then make the repository private again.
+ Evaluating results. Please wait...
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Task | 1 | 1800 |
Issue | Specification | 1 | 3.64 |
Issue | Comment | 19 | 210.08 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
### Intro At the moment, we have 1 offer on card issuing from Pa… | 18.2content: h3: count: 182 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.2 | 3.64 |
Excuse me, I forgot that the bounty needs to be approved first | 2.4content: p: count: 12 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.2 | 0.48 |
Status on 11/13/2023 After the calls with Unlimit and Striga I g… | 13.2content: p: count: 66 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 1 | 13.2 |
Disrupttech API https://cefi.disrupttech.io/about/api | 0.6content: p: count: 3 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.8 | 0.48 |
@pavlovcik Can you please review this API? | 1.4content: p: count: 7 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.5 | 0.7 |
Potentially, it will be possible to use a solution with immediat… | 10.6content: p: count: 53 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.3 | 3.18 |
Establishing contact with providers and obtaining offers is a no… | 70.4content: p: count: 352 score: 1 strong: count: 40 score: 0 wordValue: 0.2 formattingMultiplier: 1 | 1 | 70.4 |
PST White Label is offered only for teams and businesses from 20… | 9content: p: count: 45 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.7 | 6.3 |
Disrupttech [terms](https://drive.google.com/file/d/1hhveSolBz-J… | 1.6content: p: count: 7 score: 1 a: count: 1 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.3 | 0.48 |
Vault ist added the API info to the [offer](https://drive.google… | 4.2content: p: count: 20 score: 1 a: count: 1 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.8 | 3.36 |
@Hodlatoor Thank you for the input! I've already tried to reduce… | 5.8content: p: count: 29 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.4 | 2.32 |
Per information obtained on the calls, the initial setup costs w… | 5.2content: p: count: 26 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.6 | 3.12 |
As far as I know, we have long-term plans to develop a Metaverse… | 15.6content: p: count: 78 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.9 | 14.04 |
During the previous rounds, HyperBC was not selected due to the … | 18.6content: p: count: 92 score: 1 a: count: 1 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.8 | 14.88 |
The term "Metaverse bank" can be an issue in the future, because… | 4.2content: p: count: 21 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 1 | 4.2 |
@pavlovcik Can you please check whether this API meets the requi… | 3.4content: p: count: 17 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.7 | 2.38 |
@pavlovcik **pst.net Support confirmed that the following operat… | 35.6content: p: count: 178 score: 1 strong: count: 21 score: 0 wordValue: 0.2 formattingMultiplier: 1 | 1 | 35.6 |
@pavlovcik This task was aimed at finding additional options in … | 33.6content: p: count: 167 score: 1 a: count: 1 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.5 | 16.8 |
I'm happy that a solution with gift prepaid cards is acceptable … | 11.2content: p: count: 56 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 1 | 11.2 |
@0x4007 Hey, the project of the cards integration is completed, … | 11.6content: p: count: 58 score: 1 wordValue: 0.2 formattingMultiplier: 1 | 0.6 | 6.96 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 9 | 31.3 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
You claim that you're fully saturated with this project and perh… | 26.8content: p: count: 268 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.8 | 21.44 |
Very cool. | 0.2content: p: count: 2 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.7 | 0.14 |
Insane how greedy card issuers are. | 0.6content: p: count: 6 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.1 | 0.06 |
Due to costs, do you think it makes sense to focus on launching … | 6.9content: p: count: 69 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.4 | 2.76 |
I think again, just check if we can manipulate the card balance | 1.2content: p: count: 12 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.5 | 0.6 |
Seems very sketchy. They have a lot of typos on their website wh… | 9.2content: p: count: 92 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.3 | 2.76 |
Can credit for the research but I think we will stick with reloa… | 3.4content: p: count: 34 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.2 | 0.68 |
Yes but its already been a year without results so I think we sh… | 5.8content: p: count: 58 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.4 | 2.32 |
Yes for all the closed as complete tasks, when we migrate over t… | 2.7content: p: count: 27 score: 1 wordValue: 0.1 formattingMultiplier: 1 | 0.2 | 0.54 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 1.12 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Hi Ser- I would definitely suggest negotiating the onboarding an… | 1.625content: p: count: 65 score: 1 em: count: 1 score: 0 strong: count: 1 score: 0 wordValue: 0.1 formattingMultiplier: 0.25 | 0.5 | 0.8125 |
It's important to have a bridge to real world utility. as long a… | 1.025content: p: count: 41 score: 1 em: count: 1 score: 0 strong: count: 1 score: 0 wordValue: 0.1 formattingMultiplier: 0.25 | 0.3 | 0.3075 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 9 | 61.5 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
> I estimate the pure time spent for 1 new provider as 2-3 we... | 30.1li: count: 3 score: "3" words: 63 | - | 30.1 |
> One of the important things that Mercuryo was interested in... | 0.2 | - | 0.2 |
> > Disrupttech API https://cefi.disrupttech.io/about/api ... | 1.6a: count: 1 score: "1" words: 1 | - | 1.6 |
Due to costs, do you think it makes sense to focus on launching ... | 6.9 | - | 6.9 |
I think again, just check if we can manipulate the card balance ... | 1.2 | - | 1.2 |
> The Support replied that the API documentation is available... | 9.6 | - | 9.6 |
Can credit for the research but I think we will stick with reloa... | 3.4 | - | 3.4 |
> If we do not plan the white-label global crypto card issuan... | 5.8 | - | 5.8 |
Yes for all the closed as complete tasks, when we migrate over t... | 2.7 | - | 2.7 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Specification | 1 | 47.8 |
Issue | Task | 1 | 1800 |
Issue | Comment | 19 | 276.6 |
Issue | Comment | 19 | 0 |
View | Contribution | Count | Reward |
---|---|---|---|
Issue | Comment | 2 | 12 |
Comment | Formatting | Relevance | Reward |
---|---|---|---|
Hi Ser- I would definitely suggest negotiating the onboarding a... | 7.3a: count: 4 score: "1" words: 30 | - | 7.3 |
It's important to have a bridge to real world utility. as long a... | 4.7a: count: 2 score: "0.5" words: 17 | - | 4.7 |
! action has an uncaught error
Intro
At the moment, we have 1 offer on card issuing from Paymentology that has an API. There are chances that we will get a relevant offer from Vault ist which is building its API.
We need at least 1 more offer with API to compare prices and conditions. Also, I hope to find a more technology-driven provider with lower prices.
Currently, I`m negotiating with providers that claim to have an API Unlimit Striga Mercuryo Disrupttech Pst.net And looking for more
@pavlovcik Please, review this bounty.
Goal
Get one more card issuing option with API in addition to Paymentology and Vault ist.
Activity
Time estimate
Based on experience with Paymentology and Vault ist, it takes 4-6 weeks to get an offer from a provider. As I already started, I estimate the pure time spent for 1 new provider as 2-3 weeks.