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
+33-29Lines changed: 33 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -65,10 +65,10 @@ we prefer to work with the HTTP API directly. Under the hood, we use the popular
65
65
66
66
New gateways can be created by cloning the layout of an existing package. When choosing a
67
67
name for your package, please don't use the `omnipay` vendor prefix, as this implies that
68
-
it is officially supported. You should use your own username as the vendor prefix, and append
69
-
`-omnipay` to the package name to make it clear that your package works with Omnipay.
68
+
it is officially supported. You should use your own username as the vendor prefix, and prepend
69
+
`omnipay-` to the package name to make it clear that your package works with Omnipay.
70
70
For example, if your GitHub username was `santa`, and you were implementing the `giftpay`
71
-
payment library, a good name for your composer package would be `santa/giftpay-omnipay`.
71
+
payment library, a good name for your composer package would be `santa/omnipay-giftpay`.
72
72
73
73
If you want to transfer your gateway to the `omnipay` GitHub organization and add it
74
74
to the list of officially supported gateways, please open a pull request on the
@@ -109,32 +109,36 @@ Next, run composer to update your dependencies:
109
109
All payment gateways must implement [GatewayInterface](https://github.com/omnipay/common/blob/master/src/Omnipay/Common/GatewayInterface.php), and will usually
110
110
extend [AbstractGateway](https://github.com/omnipay/common/blob/master/src/Omnipay/Common/AbstractGateway.php) for basic functionality.
111
111
112
-
The following gateways are available and officially supported:
0 commit comments