Giter VIP home page Giter VIP logo

adyen-rails-online-payments's Introduction

Adyen online payment integration demos

Run this integration in seconds using Gitpod

Open in Gitpod

NOTE: To allow the Adyen Drop-In and Components to load, you have to add https://*.gitpod.io as allowed origin for your chosen set of API Credentials

Details

This repository includes examples of PCI-compliant UI integrations for online payments with Adyen. Within this demo app, you'll find a simplified version of an e-commerce website, complete with commented code to highlight key features and concepts of Adyen's API. Check out the underlying code to see how you can integrate Adyen to give your shoppers the option to pay with their preferred payment methods, all in a seamless checkout experience.

Card checkout demo

Supported Integrations

Online payments Ruby on Rails demos of the following client-side integrations are currently available in this repository:

  • Drop-in
  • Components
    • ACH
    • Alipay
    • Card (3DS2)
    • iDEAL
    • Dotpay
    • giropay
    • SEPA Direct Debit
    • SOFORT

Each demo leverages Adyen's API Library for Ruby (GitHub | Docs). See app/models/checkout.rb for payment methods.

Requirements

Ruby 3.1.1+

Installation

  1. Clone this repo:
git clone https://github.com/adyen-examples/adyen-rails-online-payments.git
  1. Navigate to the root directory and install dependencies:
bundle install

Usage

  1. Update /config/local_env.yml with your API key, Client Key - Remember to add http://localhost:8080 as an origin for client key, and merchant account name (all credentials are in string format):
PORT: "8080"
ADYEN_HMAC_KEY: "YOUR_HMAC_KEY_HERE"
ADYEN_API_KEY: "YOUR_API_KEY_HERE"
ADYEN_MERCHANT_ACCOUNT: "YOUR_MERCHANT_ACCOUNT_HERE"
ADYEN_CLIENT_KEY: "YOUR_CLIENT_KEY_HERE"
  1. Start the rails server (and run any migrations if prompted):
bundle exec rails s
  1. Visit http://localhost:8080/ (app/views/checkouts/index.html.erb) to select an integration type.

To try out integrations with test card numbers and payment method details, see Test card numbers.

Testing webhooks

Webhooks deliver asynchronous notifications and it is important to test them during the setup of your integration. You can find more information about webhooks in this detailed blog post.

This sample application provides a simple webhook integration exposed at /api/webhooks/notifications. For it to work, you need to:

  1. Provide a way for the Adyen platform to reach your running application
  2. Add a Standard webhook in your Customer Area

Making your server reachable

Your endpoint that will consume the incoming webhook must be publicly accessible.

There are typically 3 options:

  • deploy on your own cloud provider
  • deploy on Gitpod
  • expose your localhost with tunneling software (i.e. ngrok)

Option 1: cloud deployment

If you deploy on your cloud provider (or your own public server) the webhook URL will be the URL of the server

  https://{cloud-provider}/api/webhooks/notifications

Option 2: Gitpod

If you use Gitpod the webhook URL will be the host assigned by Gitpod

  https://myorg-myrepo-y8ad7pso0w5.ws-eu75.gitpod.io/api/webhooks/notifications

Note: when starting a new Gitpod workspace the host changes, make sure to update the Webhook URL in the Customer Area

Option 3: localhost via tunneling software

If you use a tunneling service like ngrok the webhook URL will be the generated URL (ie https://c991-80-113-16-28.ngrok.io)

  $ ngrok http 8080
  
  Session Status                online                                                                                           
  Account                       ############                                                                      
  Version                       #########                                                                                          
  Region                        United States (us)                                                                                 
  Forwarding                    http://c991-80-113-16-28.ngrok.io -> http://localhost:8080                                       
  Forwarding                    https://c991-80-113-16-28.ngrok.io -> http://localhost:8080           

Note: when restarting ngrok a new URL is generated, make sure to update the Webhook URL in the Customer Area

Set up a webhook

  • In the Customer Area go to Developers -> Webhooks and create a new 'Standard notification' webhook.
  • Enter the URL of your application/endpoint (see options above)
  • Define username and password for Basic Authentication
  • Generate the HMAC Key
  • Optionally, in Additional Settings, add the data you want to receive. A good example is 'Payment Account Reference'.
  • Make sure the webhook is Enabled (therefore it can receive the notifications)

That's it! Every time you perform a new payment, your application will receive a notification from the Adyen platform.

Contributing

We commit all our new features directly into our GitHub repository. Feel free to request or suggest new features or code changes yourself as well!

License

MIT license. For more information, see the LICENSE file in the root directory.

Find out more in our Contributing guidelines.

adyen-rails-online-payments's People

Contributors

bravegrape avatar deepu105 avatar dependabot[bot] avatar gcatanese avatar hbkwong avatar jillingk avatar jlengrand avatar kwok-he-chu avatar lucasbledsoe avatar reddish-purple-ocelot avatar taylorbrooks avatar tokyodaruma avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

adyen-rails-online-payments's Issues

checkout.rb calls incomplete method path for adyen_client

Problem:

Initiating a drop-in session returns a NoMethodError due to the following code under checkout.rb:
response = adyen_client.checkout.sessions(req)

Reviewing the adyen-ruby-api-library gem reveals that there is another path needed in between checkout and sessions called: "payments_api".

Solution:
response = adyen_client.checkout.payments_api.sessions(req)

I'll submit a pull request shortly.

Environmental variables are not injected properly into Gitpod

Description
When opening gitpod, the environmental variables ADYEN_xxx(etc.) are not injected properly into the environment.

Investigate

  • Create an .env file automatically in the environment upon start-up of the gitpod-instance
    It's a good temporary solution, but it would be nicer to inject them without the .env-file (if possible)
  • Investigate whether the environmental variables ADYEN_xxx (etc.) are not injected in a different terminal, hence why gem isn't able to read from ["ADYEN_xxx"] (for example)
  • Investigate if dotenv is the cause

403 Adyen::PermissionError...

Hey there!

First off, thanks for building this example application -- it's been really helpful to see how it interacts with the Adyen API.

I'm not sure if this is the best medium for support or if I should contact support, but I'm getting an error when hitting localhost:8080/checkout/dropin.

raise Adyen::PermissionError.new("Missing user permissions; https://docs.adyen.com/user-management/user-roles", request_data)

From what I can tell, I've properly setup the API_KEY, MERCHANT_ACCOUNT, and ORIGIN_KEY AND my user has the correct permissions and roles (see below).
image

Any ideas on what could be causing the 403?

Set redirectUrl using hostname

The redirectUrl is hardcoded http://localhost:8080 therefore it doesn't work when the app is deployed on Gitpod (or other cloud providers). Refactor to use the hostname header.

NameError: validationItem not used in checkout.rb

notification = notifications.first()["NotificationRequestItem"] is set but not used again.

notification should be used in place of validationItem otherwise a NameError is thrown on validationItem since it was not previously set.

current:

if validator.valid_notification_hmac?(validationItem, hmacKey)
  puts validationItem["eventCode"]
  puts validationItem["merchantReference"]
  "[accepted]"
else

solution:

if validator.valid_notification_hmac?(notification, hmacKey)
  puts notification["eventCode"]
  puts notification["merchantReference"]
  "[accepted]"
else

Submitting new PR shortly.

Expected to find a manifest file in `app/assets/config/manifest.js`

I was getting this error below when was trying to start the server:

➜  adyen-rails-online-payments git:(main) ✗ bundle exec rails s

=> Booting Puma
=> Rails 7.0.3.1 application starting in development
=> Run `bin/rails server --help` for more startup options
Exiting
bundler: failed to load command: rails (/Users/konstantinosbariotis/projects/adyen-rails-online-payments/bin/rails)
/Users/konstantinosbariotis/projects/adyen-rails-online-payments/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:110:in `block in <class:Railtie>': Expected to find a manifest file in `app/assets/config/manifest.js` (Sprockets::Railtie::ManifestNeededError)
But did not, please create this file and use it to link any assets that need
to be rendered by your app:

Example:
  //= link_tree ../images
  //= link_directory ../javascripts .js
  //= link_directory ../stylesheets .css
and restart your server

For more information see: https://github.com/rails/sprockets/blob/070fc01947c111d35bb4c836e9bb71962a8e0595/UPGRADING.md#manifestjs
	from /Users/konstantinosbariotis/projects/adyen-rails-online-payments/gems/railties-7.0.3.1/lib/rails/initializable.rb:32:in `instance_exec'
...
...
...

and I managed to fix it by using this answer from SO

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.