DCC Certification Process

Each new Payment Service Provider (PSP) solution must be fully certified and approved with Elavon prior to working in a production environment. The certification process ensures that all DCC solutions meet the requirements by both Elavon and the card brands.

The certification process includes the following:

  1. The PSP must confirm what method of DCC they are developing (either Host based or Device Conversion using the DCC BIN File method).
  2. The PSP must provide high-level overview of their solution which outlines its core architecture.
  3. The PSP must confirm how many of the 83 currencies offered will be supported on the POI Solution. Elavon’s expectation is that all currencies should be supported.
  4. The PSP must outline how the Account Range BIN file will be implemented and maintained (only if they are using the device-based method); confirming if the file is held centrally or locally at the POI solution. The process for updating the file must be demonstrated and validated during the certification.
    • It should be possible to determine the BIN file that is currently in use at the POI. This should be available via a function on the POI solution or by printing a debug / configuration receipt.
  5. An error message should be implemented on the POI solution if the solution is activated for DCC processing but no BIN file is present, to inform the merchant that DCC cannot take place until a valid BIN file is loaded.
  6. The PSP must outline how the exchange rates will be implemented and maintained, confirming if the file is held centrally or locally at the POI solution. The process for updating the exchange rates must be demonstrated and validated during the certification.
  7. The PSP must demonstrate that the conversion process adheres to the requirements set out for rounding and truncation
  8. Physical copies of test transaction receipts (sale/refund/pre-auth and completion) must be supplied to Elavon for validation. These will be assessed based on the receipt requirements as outlined
  9. Details of the POI user interface must be provided, demonstrating that the solution adheres to the choice, transparency and disclosure requirements outlined
  10. Elavon will provide a test script that will contain a full list of transactions that must be completed. Once the test script is completed, Elavon will validate the following items:
    • The exchange rate request message is in the correct format.
    • The full list of transactions completed adhere to the correct format as outlined in the Authorization protocol specification.
    • The POI solution can determine the valid currency of the card based on the 6th, 7th, 8th and 9th, and up to 12th digit of the Card PAN.
    • The DCC transactions processed used the correct conversion rate.
    • The DCC transactions processed reflect the correct applied mark-up.
    • The rounding and truncation of the amount is correct.
    • The currency exponents allocated for 0, 2, and 3 decimal place currency is correct.
    • The settlement / data capture file provided for all transactions match the original transactions completed at Authorization.
    • Full details contained on the transaction receipts to ensure that they match the test criteria provided.
    • Ability to provide a Quotation report that adheres to the requirements outlined.
    • Ability to provide an exchange rate report that adheres to the requirements.
  11. The PSP must advise us that multiple Merchant IDs can be setup and maintained with exchange rates that have different mark-up percentages applied.
  12. The PSP must advise us that DCC can be configured at a terminal level, e.g. the ability to enable and disable the DCC functionality on the POI Solution.