diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100644 index 00000000..14fca11d --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1 @@ +* @crrood @hbkwong @KadoBOT @Aleffio @rikterbeek \ No newline at end of file diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..17a0592c --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, sex characteristics, gender identity and expression, +level of experience, education, socio-economic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or + advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at support@adyen.com. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq diff --git a/Gemfile b/Gemfile index f584db2a..cceca64f 100644 --- a/Gemfile +++ b/Gemfile @@ -2,11 +2,11 @@ source "https://rubygems.org" -ruby "> 2.1.0" +ruby ">= 2.1.0" gem "faraday" gem "bundler", :group => :development gem "webmock", :group => :development gem "rspec", :group => :development -gem "activesupport", :group => :development \ No newline at end of file +gem "activesupport", :group => :development diff --git a/README.md b/README.md index cad5e83d..4b3b924a 100644 --- a/README.md +++ b/README.md @@ -77,6 +77,7 @@ adyen.checkout.version = 50 - payment_methods - payments - payments.details +- payment_links **checkout utility:** - origin_keys diff --git a/docs/checkout.html b/docs/checkout.html index eb7ae450..f0572a2f 100755 --- a/docs/checkout.html +++ b/docs/checkout.html @@ -41,6 +41,8 @@
A successful call to payment_methods will return a list of supported payment methods along with redirect URL's so that you can send your shoppers directly to the issuer's site without losing control of front-end styling / logic.
+ You can also create a link to Adyen's hosted payment form: + +response = adyen.checkout.payment_links('{
+ "amount": {
+ "value": 1500,
+ "currency": "EUR"
+ },
+ "countryCode": "US",
+ "merchantAccount": "YOUR_MERCHANT_ACCOUNT",
+ "reference": "YOUR_REFERENCE"
+}')
+
+ A successful call to payment_links will return a url, which directs a user to Adyen's hosted payment form.
+ +