@vsf-enterprise/adyen-sfcc-api

3.0.1ri:link

Patch Changesri:link

• c8e5098: Include the payment method ID in the request body when updating an Adyen payment instrument in SFCC to avoid 404 responses. This is an undocumented idiosyncrasy of the API, the method ID seems to be required even though the instrument ID should be enough.

3.0.0ri:link

Major Changesri:link

• 1ea0058: Updated dependency @vue-storefront/middleware to version 4.1.0
  • BREAKING CHANGE: SFCCServiceFactory get method now returns a promise
  
  Migration guide:
  In extended API methods, every call to context.client.sfcc.get() should be updated to handle the promise response.
  Example:

  async function example(context) {
    const { config, client } = context;
    const { sfcc, adyen } = client;
  
  -  const sfccClient = sfcc.get(context);
  +  const sfccClient = await sfcc.get(context);
    // ...
  }
  

2.0.2ri:link

Patch Changesri:link

• FIXED Sending shopperIP field to Adyen if it's derivable, previously we didn't, we introduced it as it is becoming required by Adyen

2.0.1ri:link

Patch Changesri:link

• db6555c: DEPENDENCIES Raised the versions of the @vsf-enterprise/sfcc-api, @vsf-enterprise/sfcc-sdk and @vsf-enterprise/sfcc-types dependencies

2.0.0ri:link

Major Changesri:link

• 437bbaa: - ADDED New custom onOrderSuccess callback added to the SDK, which is triggered automatically at the end of the /payment /paymentDetails calls.
  • CHANGED The returnUrl configuration option has been changed to baseUrl to reflect updated functionality and can no longer be a function.

1.0.0ri:link

Major Changesri:link

• Stable version of Adyen SFCC integration, based on the SDK pattern.