You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+27-2Lines changed: 27 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
WePay PHP SDK
1
+
WePay SDK for PHP
2
2
=============
3
3
4
4
WePay's API allows you to easily add payments into your application.
@@ -106,7 +106,32 @@ try {
106
106
}
107
107
```
108
108
109
-
And that's it! For more detail on what API calls are available, their parameters and responses, and what permissions they require, please see [our documentation](https://www.wepay.com/developer/reference). For some more detailed examples, look in the `demoapp` directory and check the README. Dropping the entire directory in a web-accessible location and adding your API keys should allow you to be up and running in just a few seconds.
109
+
For more details on which API calls are available, their parameters and responses, and which permissions they require,
110
+
please see [our documentation](https://www.wepay.com/developer/reference). For some more detailed examples, look in the
111
+
`demoapp` directory and check the README. Dropping the entire directory in a web-accessible location and adding your
112
+
API keys should allow you to be up and running in just a few seconds.
113
+
114
+
Security
115
+
--------
116
+
117
+
### Connections require TLS 1.2 ###
118
+
119
+
According to updated PCI requirements, SSL (v2, v3) and early TLS (1.0, 1.1) are no longer considered “strong
120
+
cryptography” and cannot be used as a security control after 2016-06-30. Because of this, WePay will be updating its API
121
+
endpoints to only allow TLS 1.2 connections over the coming months.
122
+
123
+
WePay SDK for PHP version 0.3.0 is _possibly_ backwards-incompatible depending on how new or old your PHP stack is,
124
+
hence the [Semantic Versioning](http://semver.org) bump.
125
+
126
+
Using the [PHP cURL extension](https://secure.php.net/manual/en/intro.curl.php), PHP will make outbound requests via the
127
+
system’s cURL installation. For licensing reasons, the PHP cURL extension uses NSS instead of OpenSSL.
128
+
129
+
*[PHP (Zend Engine) 5.5.19+ or 5.6.3+ is required](https://secure.php.net/manual/en/curl.constants.php).
130
+
* The PHP cURL extension requires cURL `7.34.0` (or newer) on the underlying system.
131
+
* The PHP cURL extension must be compiled with NSS `3.15.1` (or newer).
132
+
* HHVM 3.0 (or newer) and/or Hacklang (any version) has [the same cURL and cURL extension requirements as for
curl_setopt(self::$ch, CURLOPT_TIMEOUT, 30); // 30-second timeout, adjust to taste
268
271
curl_setopt(self::$ch, CURLOPT_POST, !empty($values)); // WePay's API is not strictly RESTful, so all requests are sent as POST unless there are no request values
thrownewWePayServerException("WePay returned an error response with no error_code, please alert api@wepay.com. Original message: $result->error_description", $httpCode, $result, 0);
0 commit comments