Adyen

Forward API can be used to interact with the following Adyen APIs:
1.Payments using adyen_payments config 2.Authorise using adyen_authorise config

UsageAnchorIcon

The shared config also supports both Basic auth and API key based authentication. Here is a sample request using Basic auth:

  1. bash
curl https://forwarding.sandbox.braintreegateway.com/ \
    -H "Content-Type: application/json" \
    -X POST \
    -u "$\{BRAINTREE_PUBLIC_KEY}:$\{BRAINTREE_PRIVATE_KEY}" \
    -d '{
        "merchant_id": "'$BRAINTREE_MERCHANT_ID'", 
        "payment_method_nonce": "fake-valid-nonce", 
        "name": "adyen_payments", 
        "url": "https://checkout-test.adyen.com/v70/payments", 
        "method": "POST", 
        "data": { 
            "number": "4242424242424242", 
            "expiration_month": "8", 
            "expiration_year": "2024", 
            "cvv": "314", 
            "currency": "USD", 
            "value": "1000", 
            "reference": "Your order number" 
        }, 
        "sensitive_data": { 
            "basic_auth_token": "'$AUTH_TOKEN'" 
        } 
    }'
Here is a sample request using x-API-key header.
  1. bash
curl https://forwarding.sandbox.braintreegateway.com/ \
    -H "Content-Type: application/json" \
    -X POST \
    -u "$\{BRAINTREE_PUBLIC_KEY}:$\{BRAINTREE_PRIVATE_KEY}" \
    -d '{
        "merchant_id": "'$BRAINTREE_MERCHANT_ID'", 
        "payment_method_nonce": "fake-valid-nonce", 
        "name": "adyen_payments", 
        "url": "https://checkout-test.adyen.com/v70/payments", 
        "method": "POST", 
        "data": { 
            "number": "4242424242424242", 
            "expiration_month": "8", 
            "expiration_year": "2024", 
            "cvv": "314", 
            "currency": "USD", 
            "value": "1000", 
            "reference": "Your order number" 
        }, 
        "sensitive_data": { 
            "api_key": "'$API_KEY'" 
        } 
    }'
However, a user will likely send additional non-mandatory fields as part of their request. To do so, they should populate the override attribute with a body attribute, where the value of the body attribute is a JSON or XML string containing the optional attributes to be sent and their values. Override Documentation


Next Page: Worldpay