|
|
|
|
|
by dpifke
1352 days ago
|
|
TreasuryDirect doesn't have an API, so there's no way to implement this without storing your users' TreasuryDirect passwords. How do you protect those passwords? With reference to https://www.law.cornell.edu/cfr/text/31/363.17, what recourse would I have if I use your service and my TreasuryDirect account is compromised as a result? Your other products include FDIC insurance via Evolve Bank & Trust. I can't imagine the FDIC would cover losses related to this product—i.e. funds are only FDIC-insured up until they're used to purchase an I-Bond. The FDIC recently sent a cease-and-desist to FTX in relation to a similar scheme (in FTX's case, funds are only FDIC-insured at Evolve up until they are used for cryptocurrency purchases); see https://news.ycombinator.com/item?id=32524527. In light of that action, what have you done to clarify the limits of the FDIC insurance to your customers and potential customers? |
|
This implies the bonds are stored on their account, not the end users