DCC Development – Getting Started

Elavon will provide the following key elements required in order for you to develop and provide the DCC Service on the Point of Interaction solution:

  • The full set of specifications outlining how DCC should be performed. This includes:
    • Elavon DCC Integration Guide
    • Elavon Card Account Range Definition File Specification which shows the BIN File format (only provided if non-default Device Conversion using the DCC BIN File method is chosen)
    • Authorisation Protocol Specification
    • Settlement Protocol Specification
      The authorisation and settlement protocol specifications outline the exact format for DCC messages; such as, sales, refunds, voids and the details of the format of the exchange rate request messages.
  • A BIN file containing all of the Card BINs and corresponding currency codes which are eligible for DCC. The BIN file is updated on a weekly basis. It is made available via an SFTP account. (only provided if non-default Device Based DCC method is chosen).
  • Exchange rates, updated daily, that are amended with the mark-up agreed with the individual customer. The exchange rates are available by completing an exchange rate request message via the authorisation host. The exchange rate message contains the marked-up rates for the list of supported currencies and the actual % mark-up applied.

The Payment Service Provider (PSP) must maintain the details of both the BIN file (only required if the non-default Device Based DCC method is being used) and the exchanges rates at the POI solution. The BIN File and rates can be held centrally or distributed directly to the POI solution. The PSP must ensure that the BIN files and Exchange rate files can be updated frequently. Best practise is that the BIN files are updated weekly. The exchange rates must be updated for each POI solution daily. Due to the fact that different mark–up % will be agreed with different customers, the PSP must be able to support rates with different mark-ups at a customer level.

The DCC service must be supported and configurable at a TID level. The customer may have multiple TID’s associated to a MID but may only want to support DCC on specific TIDs.

Prior to performing DCC in a production environment the below items must have been completed:

  • The PSP must be certified with Elavon – See certification section for details
  • During the certification process the PSP is assigned an “Application ID”. The Application ID must be loaded to the Production Authorisation Host and also provided in the Authorisation request messages. The Application ID is constructed from the following elements:
    • The Authorisation Specification Version
    • The Software Version
    • The Device Type
    • The Market Segment
    • The Capture Type
    • The Communications method used
  • The customer account must be enabled for DCC on the Elavon boarding and processing systems.
  • The customer details must be registered with Visa for them to participate with the DCC Service.
  • The POI solution must contain the details of the most up to date DCC BIN files (only if the non-default Device Based DCC method is being used.
  • The POI solution must contain the details of the most up to date exchange rates.
  • The authorisation and settlement formats must adhere to the message protocols provided by Elavon.