You can contact support through the contact page or by using the official support email made available by the platform.

Response times may vary depending on the type of request, current workload, and technical complexity.

Availability of priority support may depend on your plan or service arrangement.

Yes. Merchants should report suspicious behavior or platform misuse through the support channel.

Yes. Service feedback and merchant suggestions play an important role in shaping future improvements to the platform. Valuable contributions that lead to meaningful enhancements may be recognized and rewarded.

DPD may offer different plans based on usage needs, access levels, and integration requirements. Plan availability may evolve over time.

Availability of a free plan or trial depends on the platform offer at the time of signup.

Plan changes may be available depending on your subscription structure and billing status.

Whether usage rolls over depends on your plan structure. If this feature is not explicitly included in your subscription terms, unused capacity should not be assumed to carry forward.

Payments are generally non-refundable once paid access to digital service functionality has started, unless otherwise stated in the refund policy or required by law.

Cancellation may be available according to your billing setup. Cancellation usually stops future renewal but does not automatically create a right to a refund.

To track the status of your refund, kindly refer to your confirmation email that you have received from us.

A common workflow is: receive the order, check risk before shipment, review the signals, and then decide whether to proceed, verify, or hold the order for manual review.

Yes. DPD is intended to help merchants reduce costly COD outcomes such as failed deliveries, refusals, and fraud-related losses by improving pre-shipment decisions.

The risk score reflects behavioral and operational signals associated with a phone number or order context. It is intended to help merchants estimate risk, not to provide certainty.

DPD analyzes available risk-relevant signals such as phone history, order outcomes, fraud indicators, and merchant feedback. The exact scoring logic is internal, but the output is designed to support practical decision-making.

No. DPD does not block, approve, or reject orders automatically. The final decision always belongs to the merchant.

No system can guarantee perfect accuracy. The DPD score is a decision-support signal and should be used together with merchant judgment and internal review processes.

A high-risk score generally means the order shows stronger warning signals or behavioral patterns associated with failed deliveries, fraud, or abuse. The merchant should review the order more carefully before shipping.

You may decide to verify the customer, request confirmation, review the order manually, or apply stricter internal checks before shipment. DPD is there to support that decision, not to make it for you.

Yes. Risk scores are based on signals and patterns, not on identity or certainty. A high score does not prove fraud, which is why merchant judgment remains essential.

A high score may result from one or more risk-related signals such as previous failed delivery behavior, suspicious patterns, or feedback associated with the available data. The platform is designed to provide risk context, not a personal accusation.

Yes. Scores may change as new signals, outcomes, or merchant feedback become available over time.

Signals may include phone-number-related history, previous order outcomes, fraud-related indicators, merchant feedback, and other operational behavior patterns relevant to COD risk.

Merchant feedback may contribute to the quality of future risk intelligence where supported, but merchants should not expect to manually set or control scores directly.

DPD is designed to provide fast operational results based on the data available at the time of the check.

Results are intended to be fast enough for operational use, although response time may vary depending on system status, plan limits, or integration context.

Depending on your workflow and plan, batch or repeated checks may be supported. Availability may vary by feature and integration method.

Usage limits depend on your subscription plan and how access is configured for your account.

If you reach your plan limit, access may be restricted until the next cycle or until you upgrade to a higher plan, depending on your subscription terms.

DPD is designed to support merchant operations without creating unnecessary friction. Integration performance depends on how the platform is connected to your workflow.

Installation depends on the supported platform. In general, you install the plugin, connect your DPD account, and configure the integration according to your store setup.

Store connection depends on the integration method. Supported plugins and APIs are designed to connect merchant systems to DPD so that order checks can be performed within the merchant workflow.

Yes. DPD provides API access for merchants and developers who need custom integrations or workflow automation.

Yes. Custom systems can connect to DPD through the API, subject to the supported integration structure and your plan.

Temporary service interruption may affect API responses. Merchants should use reasonable fallback procedures when external services are unavailable.

Availability of test or sandbox access depends on the integration setup and product stage. Contact support if you need developer-oriented setup guidance.

DPD uses risk-relevant operational data such as phone numbers, order outcomes, behavioral signals, and merchant feedback where applicable.

DPD is designed to focus on behavioral risk signals and operational identifiers rather than exposing unnecessary personal identity information.

No. DPD does not provide direct identity lookup functionality or expose personal identity details as part of the normal service workflow.

DPD does not publicly expose merchant data or personal identity information. Risk intelligence is processed within the scope of the platform’s fraud-prevention purpose.

Merchants remain responsible for the data they submit and for ensuring that they are legally entitled to collect and use that data within their workflows.

DPD is designed with security and controlled data handling in mind. Access controls, secure infrastructure practices, and abuse-prevention measures are part of the platform approach.

Retention depends on operational, security, fraud-prevention, and compliance needs. DPD applies a data-minimization approach and avoids unnecessary exposure of data.

No. DPD reduces risk exposure by providing better signals and decision support, but it does not guarantee fraud prevention.

Yes. Like any risk-scoring system, DPD may produce false positives or false negatives depending on available data and operational context.

DPD is designed to support COD fraud prevention and risk review, but no platform can detect every type of fraud or every edge case across all situations.

No. DPD should be used together with merchant judgment, operational verification, and internal procedures.

No fraud-prevention system is immune to adaptation or evasion. DPD aims to improve merchant decisions, not claim that fraud cannot evolve.

In general, better signal quality and richer operational context can improve the quality of fraud intelligence over time.

Yes. Merchant feedback can support platform improvement where such features are available and used within the intended workflow.

DPD improves through continued analysis of behavioral signals, outcomes, and feedback patterns relevant to fraud prevention.

That is part of the platform’s long-term purpose. Fraud patterns evolve, and the platform is designed to improve as more operational insight becomes available.