DOCSEARCHbyAlgolia
Submit Docs

ePay Documentation

website·Indexed 35 days ago

https://docs.epay.dk

Technical documentation for ePay, a Payment Service Provider (PSP). Includes integration guides for the payment window and web services (Payment and Subscription), batch processing, and MD5 security checks. Provides installation and configuration manuals for payment modules including WooCommerce, Shopify, PrestaShop, and Magento 2.

Tokens
32.9K
Snippets
79
Records
252
Agent score
64%

What's inside ePay

  1. Overview of the ePay Payment web service

    The ePay Payment web service is a SOAP-based API used to manage payments after authorization. The service endpoint is located at https://ssl.ditonlinebetalingssystem.dk/remote/payment.asmx.

    General Data Types:

    • Integer, Long, String, Enum, Boolean, and Datetime.
    • Datetime Format: Must be yyyy-MM-dd HH:mm:ss.

    Response Handling: All functions return a boolean indicating success. If the result is false, developers must check the epayresponse and pbsresponse integer values to determine the source of the error.

  2. Activate Fraud Fighter and configure alarm recipients

    To begin monitoring payments and setting up fraud rules, you must first activate Fraud Fighter in the ePay administration menu under Fraud Fighter -> Overview. Once activated, you can specify email addresses or mobile phone numbers to receive alarms when suspicious payments are detected by entering the contact detail and clicking Add recipient of Fraud Fighter alarms.

  3. Understand how Fraud Fighter detects and prevents fraud

    Fraud Fighter protects businesses using three primary mechanisms:

    1. Country Matching: It compares the country that issued the payment card with the country of the purchase (determined by IP address). A mismatch may indicate fraud.
    2. Rule-based Monitoring: Payments are monitored based on user-defined rules. Suspicious payments trigger email alarms, allowing the merchant to decide whether to capture the amount and ship the product.
    3. IP Blocking: Specific IP addresses can be blocked to prevent repeated fraudulent attempts from the same source.

  4. Retrieve subscription details using getsubscriptions

    The getsubscriptions operation allows you to retrieve information about one or all subscriptions associated with a merchant.

    Input Parameters:

    • merchantnumber (Integer, Mandatory): Your 7-digit unique merchant number.
    • subscriptionid (Long, Mandatory): The unique identifier for the subscriber. Set this to 0 to return all created subscriptions, or provide a specific ID (> 0) to return only that matching subscription.
    // Example: Get all subscriptions
{
  "merchantnumber": 1234567,
  "subscriptionid": 0
}

// Example: Get a specific subscription
{
  "merchantnumber": 1234567,
  "subscriptionid": 987654321
}

  5. Payment web service response fields reference

    The Payment web service returns the following fields in its response objects to provide details about the transaction status, fraud detection, and card information:
    {
  "msc": "Boolean - Indicates if the payment was completed with 3D Secure",
  "fraudStatus": "Integer - Indicator of potential fraud (0 = false, 1 = true)",
  "FraudMessage": "String - Textual description of possible fraud reasons",
  "payerCountryCode": "String - The country the payer is from",
  "issuedCountryCode": "String - The country where the card was issued",
  "fee": "Integer - The fee charged to the customer (in minor units)",
  "Insplitpayment": "Boolean - Indicates if the payment can be split into multiple transactions",
  "tcardno": "String - Truncated card number"
}

  6. Understand 3D Secure functionality and risk shift

    3D Secure is a security standard (including Verified by Visa and MasterCard SecureCode) that adds a verification step to the payment process, typically via a one-time password sent via SMS.

    Key technical and business considerations:

    • Risk Shift: When 3D Secure is used, the card-issuing bank generally assumes the risk of fraud, meaning chargebacks are typically not permitted if the merchant complies with the acquirer's legal requirements.
    • Compatibility: It applies only to international payment cards. It cannot be used with Dankort payments.
    • Acquirer Requirements: Some acquirers may mandate the use of 3D Secure.

  7. Create and manage payment groups

    Groups allow you to categorize payments (e.g., by company department) and limit user access to specific domains. There are two ways to create groups:

    1. Via Administration: Go to Settings -> Groups, enter the group name, and click Create group.
    2. Via API/Parameter: Use the group parameter during a transaction. If the group does not already exist, ePay will automatically create it upon first use.

  8. Manage and identify suspicious payments in ePay administration

    Suspicious and blocked payments can be managed within the ePay administration panel:

    • Identifying Suspicious Payments: These are marked with a red stop sign in the administration view. Clicking 'Info' on the right will reveal the specific reason for the suspicion in the 'Fraud Fighter' field.
    • Viewing Blocked Payments: Payments explicitly blocked by Fraud Fighter are located under the menu: Fraud Fighter -> Declined payments.
    • Checking Costs: The price per transaction is available under: Fraud Fighter -> Overview.

  9. Cancel an ePay subscription

    To terminate your subscription, log into the ePay administration panel and navigate to Invoices -> Terminate subscription.

  10. Migrate from another payment gateway to ePay

    You can switch to ePay using your existing acquirer agreement. To migrate, create an ePay account and specify that you are shifting from another payment gateway, including the name of the previous provider. It is permissible to use two payment gateways simultaneously during a transitional period.

  11. Create and send a payment request in PrestaShop

    Payment requests are used to charge customers for amounts exceeding the original authorized amount (e.g., when adding products to an order).

    1. Navigate to Orders in the left menu and select a specific order.
    2. Refresh the page (F5) to ensure the option is available.
    3. Locate the Create payment request section near the top of the page.
    4. Review or edit the requester name, comments, receiver details, and sender details. Note: The amount is fixed to the remaining balance of the order and cannot be changed.
    5. Click Send payment request to email the link to the customer.

    Once paid, the transaction number will appear under the Messages section on the order page, and the request will automatically close.

  12. Install the ePay payment module in PrestaShop

    To install the ePay payment module in PrestaShop, first download the latest module zip file from the official GitHub releases. Before proceeding, it is recommended to create a backup of your website.

    1. Log in to the PrestaShop administration panel.
    2. Navigate to the Modules menu.
    3. Click Upload a module at the top of the screen.
    4. Select the downloaded ePay zip file to upload and install it.
    # Download the latest release from:
https://github.com/epay-technology/prestashop-payment-module/releases/latest