Skip to content

Commit a38c26d

Browse files
authored
Remove instructions to make a gateway official
Because making gateways official isn't a thing anymore
1 parent fa3af65 commit a38c26d

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

README.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -72,12 +72,6 @@ it is officially supported. You should use your own username as the vendor prefi
7272
For example, if your GitHub username was `santa`, and you were implementing the `giftpay`
7373
payment library, a good name for your composer package would be `santa/omnipay-giftpay`.
7474

75-
If you want to transfer your gateway to the `omnipay` GitHub organization and add it
76-
to the list of officially supported gateways, please open a pull request on the
77-
[omnipay/common](https://github.com/thephpleague/omnipay-common) package. Before new gateways will
78-
be accepted, they must have 100% unit test code coverage, and follow the conventions
79-
and code style used in other Omnipay gateways.
80-
8175
## Installation
8276

8377
Omnipay is installed via [Composer](https://getcomposer.org/). For most uses, you will need to require an individual gateway:

0 commit comments

Comments
 (0)