Duplicate Payment
If the same payment is charged more than once for the same transaction, the duplicate charge may be eligible for a refund after verification.
This Refund Policy explains when payments made for Midiawave Auth services may be eligible for review, correction or refund.
Midiawave Auth charges according to service usage. Once an OTP, verification message or other billable authentication request has been successfully processed, the related charge is considered consumed service usage.
Refund eligibility depends on the circumstances of the payment and whether the affected service was successfully delivered or consumed.
If the same payment is charged more than once for the same transaction, the duplicate charge may be eligible for a refund after verification.
If your payment is debited but the corresponding balance, credit or service access is not provided, you may contact us for review.
If an incorrect amount is charged because of a confirmed billing or system error, the affected transaction may be corrected or refunded.
If a paid service could not be provided because of a confirmed Midiawave Auth platform issue, the affected usage may be reviewed.
Refunds are not automatically provided for every payment. A transaction may be reviewed when there is a reasonable indication that a payment was duplicated, incorrectly charged, not credited or affected by a confirmed Midiawave Auth service issue.
Eligibility will depend on transaction records, account activity, service usage and the circumstances surrounding the request.
Midiawave Auth provides usage-based authentication services. Charges associated with services that have already been successfully processed or consumed are generally non-refundable.
OTP requests that have been successfully processed and billed are considered consumed usage.
Successfully processed verification link messages or other billable messages are generally non-refundable.
Charges resulting from an incorrect mobile number or other information supplied by the customer are generally not eligible for refund when the request has already been processed.
Multiple authentication or resend requests initiated by the customer, application or end user are treated as separate usage when successfully processed.
If a payment is deducted from your payment method but Midiawave Auth does not receive or credit the payment, the transaction may initially remain pending while the payment provider or banking network completes reconciliation.
If the amount is not automatically reversed or credited after reconciliation, you may contact support with the relevant transaction details so the payment can be reviewed.
Providing the payment reference, transaction date and amount helps us investigate billing issues more efficiently.
If you believe a payment qualifies for review, contact Midiawave Auth support and provide enough information for us to identify the transaction.
Registered users should submit billing and refund requests through the support section inside the Midiawave Auth console whenever available.
Refund requests may be reviewed against payment records, account activity, authentication usage, message processing information and other relevant service records.
We may request additional information where necessary to verify the transaction or confirm that the person requesting the refund is authorised to act for the relevant account.
Approval or rejection of a refund will depend on the circumstances of the transaction and whether the corresponding service was consumed.
When a refund is approved, it will normally be returned through an appropriate payment method or handled through another suitable billing adjustment where applicable.
The time required for an approved refund to appear may depend on the payment provider, bank, card network or other financial institution involved in the original transaction.
Midiawave Auth may refuse a refund request where there is evidence of misuse, fraudulent activity, manipulation of service usage, repeated abusive refund requests or violation of applicable service terms.
Accounts associated with suspected fraudulent or abusive activity may also be subject to review, restriction or other appropriate action.
Midiawave Auth is owned and operated by Midiawave Communication Private Limited.
Non-registered users may contact the public support address below. Registered users should use the support section inside their Midiawave Auth console for faster account-specific assistance.