I would like to model a blockchain in UML. Here are the requirements that I came up with:
User can transfer money
Money can be transferred from a bank account to a digital wallet
Money can be transferred from a digital wallet to a bank account
Money can be transferred to a user (from the contact list)
User can consult the balance of his portfolio
Here my UML class diagram:
Since I am new to the blockchain technology, I would like to know: is this diagram correct? Did I miss something?
Related
Is it possible to transfer from the customer account to our own account?
Note: This is not a fee of transaction, but it's simply withdrawing from customer's account.
Here is a scenario: We introduce a user to the shopping center. Then the user pays in the shopping center (physically and not online payment). Then we get the invoices from the shopping center and at the end of the month, we should transfer some money from the shopping center. So, no online transaction, no fee. Just simply transferring money from the user's account to our account. (maybe there should be verification process from the shopping center, which is ok)
You'll need to decide how to model the relationship you have with the Shopping Center and the Shopper with Stripe, but one suggestion would be to consider the Shopping Center as your Customer, who then pays you based on referred Shoppers etc. This could be done many different ways, using Invoices, or saved payment methods and off-session payments, or with a usage-based Subscription.
Alternatively, if you were facilitating payments from Shoppers to the Shopping Centers, you might use Connect and set up the Shopping Centers as Connected Accounts and the Shoppers as Customers. You would collect application fees for the payments you facilitate online. For offline payments, you could charge your connected accounts fees using account debits.
I have business problem where sellers sells some goods with their different buyers. in every purchase, seller is recording the transaction in their owne ledger and also recording the same transaction in a passbook that keeps with buyer only. So here buyer/seller anyone can manipulate the transaction and end of the day those ledgers will be out of sync. Eventually seller has to loose the money or buyer has to pay more money.
In this business transactions between seller & their different buyers, in order to avoid this kind of mutable ledger of transactions and to avoid loss of trust between buyer & seller, i am planning for an application that enforces the trust between the participant in the business network and also the ledger transactions immutable and the ledger itself is distributed.
This ledger is just to record the transactions in immutable way. Whenever seller is inserting a new transaction, it should be approved by buyer. Buyer should just have only the read access. Any buyer should not be able to see other buyers transactions.
As this is my business transaction, Hyper ledger came into my mind to implement it as blockchain network.
i am identifying Buyer & seller are two types of participants and recordEntry is the transaction in this network.
As buyers should cannot see other buyer's transactions, every buyer should be in one channel.
as buyers count increases with new customers coming to seller organization, how can a channel be created with dynamic participants?
how to identify the asset in this network?
Also please give me some references to kickstart this application
Thanks
Satya
For the usecase of a market place where users buy and sell stocks, which kind of nodejs architecture for hyperledger-composer should be adopted
for hyperledger Fabric where users dont trust the system. I read many blogs where they said to maintain the cards of user in their
local system.
If i follow UI + Middleware + FabricRuntime. where should the card management be provided and which part/layer should be exposed to user.
Could you please suggest how the design of application must be for such kind of usecases?
OK, I am a little confused on the best way to setup Stripe for customer to customer direct bank transfer. Here's what I want to do.
I am building a rental platform where a tenant and landlord can enter their bank information (routing and account) and then on a monthly basis transfer money from the tenant to pay the landlord directly (ie, bank to bank transfer) for that months rent.
I think Stripe Connected account makes the most sense to make this happen. But I guess I am not fully understanding the flow, even after reading the docs. Any insight will be greatly appreciated.
You need to use Stripe Connect to accept payments on behalf of others. In your scenario, you'd create customers for the tenants and connected accounts for the landlords, then create charges to move funds from a tenant to a landlord, with your platform optionally taking a cut out of the transaction.
Since you want the tenant to pay via bank transfer, you'd need to use ACH rather than cards.
I want to know, can i use google wallet with braintree payment gateway in android application. To be more technical clear, take MASKEDWallet from google wallet and fetch all useful information from it and send it to braintree payment gateway for completing the purchase.
Please help.
I'm a couple of days into working on same, so this is devoid of technical specifics (more conceptual). Also I'm doing so on the "web" side of Wallet Instant Buy (not Android), though the concept of sending payment details through, and meeting (PCI) requirements, to your (any) credit card payment gateway should be the same.
Unless I'm corrected by a Googler:
You'll need to make a FullWalletRequest to obtain the "full wallet" which means the actual card details that you need to send to your gateway (card no, cvc/cvv, expiration, billing address etc.).
At which point, it wouldn't differ from any other/existing (gateway type) credit card processing.
At the end of the day, what Google Wallet Instant Buy does:
provide a merchant application (droid/ios/web) a "Virtual Onetime Card", which,
represents a Google Wallet user's real card stored in his/her Google Wallet account, therefore securing actual card details and scoping the transaction (because it's one-time)
I would think the only possible caveat is whether or not a gateway accepts such type of of card (" a MasterCard-branded virtual prepaid debit card")..unlikely that would be an issue (in US, which is where the API is limited to at this time...)....
Digressing a bit. The other caveat that comes to mind is if you employ some fraud screening service. You're given a "virtual card" (not the real card of a cardholder), so if your service uses/needs that information to come up with a risk score, then its something you need to account for...
Hth....