As discussed in Supported payment methods and transaction types, the payment and transaction types are specified in the gateway.json file. For a credit card gateway that supports 3D-Secure, the gateway.json file should be similar to the following:

{
  "provider": "Generic Card 3DS Provider",
  "paymentMethodTypes": ["card"],
  "transactionTypes": {
    "card": ["authorization", "void", "refund"]
  },
  "processors" : {
    "card": "card3ds"
  }

}

Note that the card3ds processor is needed to provide 3D-Secure support.

In addition to configuring user interface controls, the config.json file must include a shared secret key specified by the merchant. The key is used to generate a signature that the POST /ccstore endpoint uses for authentication:

...
    {
      "id": "secretKey3DS",
      "type": "passwordType",
      "name": "secretKey",
      "helpTextResourceId": "secretKeyHelpText",
      "labelResourceId": "secretKeyLabel",
      "defaultValue": "5ad0f437X6af6X4d4eXb08cX729a310843ce",
      "required": true,
      "public": true
    },
...

See Generate the signature for more information about how the secret key is used.


Copyright © 1997, 2017 Oracle and/or its affiliates. All rights reserved. Legal Notices