Bitcoin Forum
May 29, 2024, 03:22:00 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Economy / Service Discussion / Re: Is atlos.io a legitimate payment processor? on: April 27, 2024, 03:33:27 PM
Hi Yamane_Keto,

I'm the head engineer at ATLOS. Thank you for posting about us. You may have misunderstood what our service is all about. In fact, we developed it exactly for people like you, who don't TRUST others (as you should).

As a non-custodial payment processor, ATLOS is 100% trustless. It's also permissionless. This means you don't have to trust it in order to use it. In contrast with other crypto payment gateways, ATLOS never holds your funds, so it can't steal anything. And, it cannot be hacked. All funds flow directly from the buyer to the merchant. There's a demo on our homepage. You can try it with a payment of $1 to see how it works.
2  Other / Bitcoin Wiki / Re: Request edit privileges here on: February 24, 2023, 09:51:28 PM
Hello,

My user name is "Atlos". I would appreciate editing privileges.

https://en.bitcoin.it/wiki/User:Atlos

Thank you!
3  Economy / Service Announcements / Re: [ANN] The Launch of Decentralized Crypto Payment Processor, ATLOS.io on: October 29, 2022, 02:32:24 AM
I see. But the integration instructions on your main page show it depends on sever side library which show centralization. Could you elaborate?
This is correct, we are serving the payment widget from our server for convenience. It can be served from IPFS or locally from the merchant's server if they have one.
4  Economy / Service Announcements / Re: [ANN] The Launch of Decentralized Crypto Payment Processor, ATLOS.io on: October 27, 2022, 06:19:47 PM
Thank you for your feedback!

Can we see source code for Altos? Is it open or closed source code?
It is closed source for now. We may be opening it and posting on GitHub in the future. The reason for the closed source is we don't hold any funds in the contract, so no risk or losing them. All funds are passed through immediately to the merchant. There's no need, for now at least, to audit the source code.

I am not even sure you are supporting Bitcoin for payments.
We do not accept bitcoin at this time. Our focus is mainly stablecoins on EVM-compatible blockchains. But, bitcoin and other non-EVM compatible coins are on the roadmap.

If merchant need to open an account at your website, that means your payment processor is centralized.
Actually, the website only contains the integration instructions. It's not necessary to open an account there.

There are much better open source payments processors like Btcpayserver, CypherpunkPay and few others.
Sure, for people who want to run their own Linux daemon and only accept bitcoin Wink
5  Economy / Service Announcements / [ANN] The Launch of Decentralized Crypto Payment Processor, ATLOS.io on: October 24, 2022, 09:01:10 PM
Introducing ATLOS

ATLOS is a decentralized, permissionless, non-custodial crypto payment processor.

What Is It?

ATLOS allows websites and apps to accept payments in cryptocurrency, such as stablecoins, UCDC, USDT, DAI or other crypto.

Why Decentralized Payment Processor?

Most existing payment processors are built with web2 technologies. Many maintain relationships with banks for converting crypto into fiat. As a result, they are severely restricted in types of industries they can service. They require an approval and KYC prior to onboarding, and they can ban a merchant's account or freeze merchant's funds at their discretion.

ATLOS is a permissionless payment processor. No approval is required to sign up. To open an account, a merchant only needs to connect a wallet, no other information is required.

ATLOS is also non-custodial. It does not hold merchants' funds and cannot freeze them.

Integration

ATLOS can be easily integrated with any website or app by adding only two lines of JavaScript code.

Links

Visit ATLOS at https://atlos.io
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!