POST /createTestCardRanges

Creates one or more test card ranges.

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
accountCode String Yes

The code of the account, for which the test card ranges should be created.

accountTypeCode String Yes

The type of the account, for which the test card ranges should be created.

Permitted values:

  • Company
  • MerchantAccount

These values are case-sensitive.

testCardRanges[] Array Yes

A list of test card ranges to create.

testCardRanges[].rangeEnd String Yes

The last test card number in the test card range (inclusive):

  • Min 6, max 19 digits
  • BIN compliant Example: 5432 1234 1234 4321
testCardRanges[].cvc String No

The test card range security code.

Example: 123

testCardRanges[].expiryMonth String Yes

Expiry month for the test card range.

Allowed values:

  • JANUARY
  • FEBRUARY
  • MARCH
  • APRIL
  • MAY
  • JUNE
  • JULY
  • AUGUST
  • SEPTEMBER
  • OCTOBER
  • NOVEMBER
  • DECEMBER

Possible values:

  • "DECEMBER"
  • "OCTOBER"
  • "JUNE"
  • "APRIL"
  • "MARCH"
  • "FEBRUARY"
  • "JANUARY"
  • "AUGUST"
  • "NOVEMBER"
  • "SEPTEMBER"
  • "JULY"
  • "MAY"
testCardRanges[].threeDUsername String No

The username used for 3D Secure authentication.

testCardRanges[].rangeStart String Yes

The first test card number in the test card range (inclusive):

  • Min 6, max 19 digits
  • BIN compliant Example: 5432 1234 1234 1234
testCardRanges[].threeDPassword String No

The password used for 3D Secure authentication.

testCardRanges[].address No

Contains the billing address of the card holder. The address details need to be AVS-compliant, which means that you need to provide at least street address.

testCardRanges[].cardHolderName String Yes

The name of the card holder, as it appears on the card, for the test card range.

testCardRanges[].expiryYear Integer Yes

Expiry year for the test card range.

Example: 2020

testCardRanges[].threeDDirectoryServerResponse String No

3D Secure server response. It notifies whether the specified card holder is enrolled in a 3D Secure service. Possible values:

  • Y (Authentication available)
  • N (Card holder not enrolled/not participating)
  • U (Unable to authenticate)

Possible values:

  • "N"
  • "Y"
  • "U"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.