Bitcoin Forum

aaaa

Is this like hassle free if I give you all my public keys or let you hold my money ?

No offence but we get lots of scammers here and you can never be too careful can you now.

Hello Cen
We have posted a detailed announcement about our system here, please give it a look and let us know your questions and suggestions: https://bitcointalk.org/index.php?topic=3077339

So you own the private keys and the cost is about 1% but you will do a call-back to web-servers or page that is running the script.

Both ETH and BTC have priced themselves out of the small payments market due to transaction costs so IOTA sounds good as does Ripple
for taking payments (Cheap as chips) but then use an accumulator maybe and make payments to clients in BTC or better still ETH to keep
external costs down.

Use the notes field in the transaction to add your order number so that the two ends tie up with each other

The idea is that services choose what coins to accept, and with our service they can accept multiple coins without extra effort or multiple API integrations.
We don't keep anyone's money, as soon as it is received it is forwarded to the address provided by the service. We also don't plan to provide currency conversion (accepting in IOTA but receiving in BTC).

We do own the private keys for the temporary addresses created by our system for the payments. But, like I said before, the payments are forwarded almost instantly, there is no user's money sitting there.

When the payment is confirmed our service does a callback to the URL provided.
It is in that URL that the users should provide the indications they will need to verify the payment along with a nonce to verify that the callback is coming from us.

The callback URL should look something like this:

then, when our system makes the request, it will use the URL (with the parameters already provided), and append the rest of the parameters, like value, TXID in, TXID out, number of confirmations, etc

This might work for buying new cars or trading coins but who's going to use it for something worth less than $100 due to the fees
and this is made worse if you don't buffer up the outbound payments because profit could be consumed by mining fees.

Tips or $0.10 to download a .pdf manual and items under $10 must be half the market on the internet and we have not moved quite
just yet into Pay-as-you-go IPTV but this is where I think we are heading and you could use the ShapeShift REST API's to convert the
coins without getting too complicated and having to then argue about conversion rates by using a 3rd party.

We do understand what you're saying, and it surely isn't feasible for payments under $10, atleast for BTC (ETH is OK with payments down to $5, IOTA is OK with any value).

That being said, our system is not meant to buffer the payments since it has no registrations or API keys, so there's no account where to buffer the funds. That's not what we're trying to achieve.

What we want is to give the easiest API possible for websites to implement cryptocurrency payments, hassle-free. Our aim is for e-commerce websites, aswell as digital goods websites ("buy 100 credits for 0.01 ether!", or whatever), who want to add multiple currencies (and receive in multiple currencies) with as little code as possible.

The only thing required is that you implement the logic on your server to handle the callbacks sent to your server when the transaction from the client is confirmed.

Contact the developer

Sent three emails and no reply... ???

How does it work? Could you post the documentation link?

We are very sorry, our email had a typo on the documentation (prontonmail instead of protonmail).
Our email is: cryptapi@protonmail.com

Please re-send your questions and we will reply ASAP.


Interactive documentation is here: https://cryptapi.io/docs/