Content pfp
Content
@
0 reply
0 recast
0 reaction

Shashank  pfp
Shashank
@0xshash
this is huuuge! such a novel unlock to bridge web2 and web3 legos kudos to the fabric team on shipping this glad stripe was able to play a role here
3 replies
1 recast
7 reactions

Stephan pfp
Stephan
@stephancill
nice! how does this work? does stripe handle making the fiat amount available onchain?
1 reply
0 recast
0 reaction

Shashank  pfp
Shashank
@0xshash
not really. you open a stripe business account attached to fabric platform. stripe handles identity verification/ tax reporting/ web2 payments fabric is doing the heavy lifting of syncing this state onchain cc: @ds who has the best context on details
1 reply
0 recast
1 reaction

Danny pfp
Danny
@ds
Yep, that’s correct. We have a service layer which binds connect payments to onchain calls. The contract owner grants one of our agents a role which can grant or revoke time for an account on the contract. When a payment is confirmed, the agent extends time. There is a lot more to it, but that’s the gist.
1 reply
0 recast
1 reaction

Stephan pfp
Stephan
@stephancill
how does the conversion from credit card fiat -> paying out in crypto work?
1 reply
0 recast
0 reaction

Danny pfp
Danny
@ds
It doesn’t work that way. A creator who enables credit card payments receives fiat in their stripe account. From there they can get payouts to their bank, or enable USDC payouts if they wish. Hypersub is facilitating the transaction and binding it to an onchain action which grants time periodically to keep the NFT active. A refund revokes time. No onchain liquidity is required (other than agent gas budget).
1 reply
0 recast
1 reaction