Skip to content

Latest commit

 

History

History
55 lines (35 loc) · 2.44 KB

Setup.md

File metadata and controls

55 lines (35 loc) · 2.44 KB

Setup

Getting Started With The Cybersource-Commercetools Extension

The following section contains steps to get started with a generic integration between Commercetools and Cybersource using the typescript extension.

Extension Upgradation

If you are using old version of extension, replace your module with the latest version.

Prerequisites

  • An installation of node JS is required before running the application.

1. Create Access Keys

To allow access to both Commercetools and Cybersource, authorization is enabled via access keys supplied by the associative provider.

  • Commercetools API Keys can be created from within the Commercetools Merchant Center. See Key Creation for more details
  • The Cybersource integration supports Card Tokenization and Payment processing. For more detail about how to setup these, see Key Creation for more details.
    • Card Tokenization & Payment Process: REST Shared Secret

2. Application Setup

Configuration of the Extension allows you to set the properties required for access to both Commercetools and Cybersource. This includes properties such as the Commercetools project key and the Cybersource merchant Id. For more information about what properties need to be set and how they can be configured, see API Extension Setup for more details.

3. Extend Commercetools

Commercetools needs to be extended to support the interactions between Commercetools and Cybersource. The customizations are as follows:

  • API Extensions:
    • Create Payment Event
    • Update Payment Event
    • Update Customer Event
  • Data Model Changes:
    • Payment Interactions

The details of the specific customizations listed above is documented here: Commercetools Setup.

4. Front-end Setup

The bulk of integration works when using the Cybersource-Commercetools Extension is within the user-interface. This is because Commercetools does not come with a user-interface and therefore all implementations will be different.

For setting up client-side application on any of the payment methods, use the following guide: