Depends on how you write the code<p>(generally - theres a lot of coding specifics involved) Authorize.net via their API absolutely requires PCI compliance and an SSL certificate on your site. Stripe recommends an SSL certificate with their basic JS code. And unless your sending a user directly to Paypal&#x27;s website to login via Paypal, if you use their API, you should have an SSL certificate and be PCI compliant.<p>IE: if the CC info is entered on a page you built, on your server, yes - SSL and PCI. If your sending the user to another site (ie: Paypal or using Stripes JS code) - no, it&#x27;s on them.<p>Most programmers should at least read the parts of OWASP that pertain to their language (<a href="https:&#x2F;&#x2F;www.owasp.org" rel="nofollow">https:&#x2F;&#x2F;www.owasp.org</a>). If it gets entered into a form and stored in some sort of DB, you should at least code with basic precautions.