If you are creating a new Stripe account (as of October 2017), please review this article for important information.

As of October 2017, Stripe started giving a "warning" to those using Stripe's API to send payment information (rather than integrating with Stripe directly), stating that this method of sending credit card data may be "unsafe." At the same time, Stripe started requiring everyone who wanted to continue processing payment information via the Stripe API to agree that "Sending credit card numbers directly to the Stripe API is generally unsafe." Stripe also began sending notices to existing customers who have processed payments via Stripe's API: "It looks like you've been sending un-tokenized credit cards to our API."

From this link, click "Show Advanced Options" > "Integration" and enable "Process payments unsafely." If this step is not completed, users will receive this error message when trying to make payment on your SilkStart website:

Although this may sound concerning, we are confident that your payments are secure and encrypted. Enabling this setting simply indicates that the integration has not moved over to the Stripe's tokenization system for payments. Instead, the Stripe integration is currently passing payments through Stripe's API. In other words, Stripe has chosen to improve the security of their API integration - they have not stopped supporting it. While SilkStart has not adopted the tokenization system yet, we're confident that our API-based integration is safe, and is encrypting payments successfully using SSL (Secure Sockets Layer).

For the full set of instructions to integrate SilkStart with your Stripe account, see this article.

If you feel that Stripe falls short of your security requirements, we encourage you to consider one of our other payment gateways: PayPal, Bambora or Authorize.net. Please contact us if you have questions regarding transitioning to one of these gateways.