checkout-example

Adyen online payment integration demos - Sessions Flow

This sample shows the sessions flow, if you want to integrate a more complex flow, have a look at the checkout-example-advanced folder.

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.

This demo leverages Adyen's API Library for .NET (GitHub | Docs).

Run integration on localhost using a proxy

You will need .NET Core SDK 6.x. to run this application locally.

1. Clone this repository

git clone https://github.com/adyen-examples/adyen-dotnet-online-payments.git

2. Open your Adyen Test Account and create a set of API keys.

   • ADYEN_API_KEY
   • ADYEN_CLIENT_KEY
   • ADYEN_MERCHANT_ACCOUNT

3. To allow the Adyen Drop-In and Components to load, add https://localhost:5001 as allowed origin by going to your ADYEN_MERCHANT_ACCOUNT in the Customer Area: Developers → API credentials → Find your ws_user → Client settings → Add Allowed origins.

Warning You should only allow wild card (*) domains in the test environment. In a live environment, you should specify the exact URL of the application.

This demo provides a simple webhook integration at /api/webhooks/notifications. For it to work, you need to provide a way for Adyen's servers to reach your running application and add a standard webhook in the Customer Area. To expose this endpoint locally, we have highlighted two options in step 4 or 5. Choose one or consider alternative tunneling software.

4. Expose your localhost with Visual Studio using dev tunnels.
   • Add https://*.devtunnels.ms to your allowed origins
   • Create your public (temporary/persistent) dev tunnel by following this guide

If you use Visual Studio 17.4 or higher, the webhook URL will be the generated URL (i.e. https://xd1r2txt-5001.euw.devtunnels.ms).

5. Expose your localhost with tunneling software (i.e. ngrok).
   • Add https://*.ngrok.io to your allowed origins

If you use a tunneling service like ngrok, the webhook URL will be the generated URL (i.e. https://c991-80-113-16-28.ngrok.io/api/webhooks/notifications/).

  $ 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           

6. To receive notifications asynchronously, add a webhook:

   • In the Customer Area go to Developers → Webhooks and add a new Standard notification webhook
   • Define username and password (Basic Authentication) to protect your endpoint - Basic authentication only guarantees that the notification was sent by Adyen, not that it wasn't modified during transmission
   • Generate the HMAC Key - This key is used to verify whether the HMAC signature that is included in the notification, was sent by Adyen and not modified during transmission
   • See script below that allows you to easily set your environmental variables
   • For the URL, enter https://ngrok.io for now - We will need to update this webhook URL in step 10
   • Make sure the webhook is Enabled to send notifications

7. Set the following environment variables in your terminal environment: ADYEN_API_KEY, ADYEN_CLIENT_KEY, ADYEN_MERCHANT_ACCOUNT and ADYEN_HMAC_KEY. Note that some IDEs will have to be restarted for environmental variables to be injected properly.

export ADYEN_API_KEY=yourAdyenApiKey
export ADYEN_MERCHANT_ACCOUNT=yourAdyenMerchantAccount
export ADYEN_CLIENT_KEY=yourAdyenClientKey
export ADYEN_HMAC_KEY=yourAdyenHmacKey

On Windows CMD you can use this command instead.

set ADYEN_API_KEY=yourAdyenApiKey
set ADYEN_MERCHANT_ACCOUNT=yourAdyenMerchantAccount
set ADYEN_CLIENT_KEY=yourAdyenClientKey
set ADYEN_HMAC_KEY=yourAdyenHmacKey

8. In the Customer Area, go to Developers → Additional Settings → Under Acquirer enable Payment Account Reference to receive the Payment Account Reference.

9. Start the application and visit localhost.

dotnet run --project checkout-example 

10. Update your webhook in your Customer Area with the public url that is generated.

• In the Customer Area go to Developers → Webhooks → Select your Webhook that is created in step 6 → Server Configuration
• Update the URL of your application/endpoint (e.g. https://c991-80-113-16-28.ngrok.io/api/webhooks/notifications/ or https://xd1r2txt-5001.euw.devtunnels.ms)
• Hit Apply → Save changes

Note When exiting ngrok or Visual Studio a new URL is generated, make sure to update the Webhook URL in the Customer Area as described in the final step. You can find more information about webhooks in this detailed blog post.

Supported Integrations

Online payments ASP.NET demos of the following client-side integrations are currently available in this repository:

• Drop-in
• Components
  • ACH
  • Card (3DS2)
  • Dotpay
  • giropay
  • iDEAL
  • Klarna (Pay now, Pay later, Slice it)
  • SOFORT

Before testing, please make sure to add the payment methods to your Adyen Account.

Usage

To try out this application with test card numbers, visit Test card numbers. We recommend saving some test cards in your browser so you can test your integration faster in the future.

1. Visit the main page, pick a payment method, follow the instructions to make a payment request.

2. Visit the Customer Area Developers → API logs to view your logs.