0. Document Information

• Scope: Paid credit-based NEXI SMS verification service
• Coverage: payment request, transfer verification, manual top-up, deduction, recovery, refund/settlement, support handling
• Timezone: KST (UTC+9)
• Unspecified matters follow the Terms of Service, Privacy Policy, and applicable laws.

1. Definitions

• Credit: Paid unit used for Discord/Gmail/Microsoft verification
• Top-up: Manual credit charging after operator verifies bank transfer
• Deduction: Reduction of credit or uses according to service rules
• Recovery: Restoration of deducted amount when failure criteria are met
• Order ID: Identifier independently managed by each server administrator
• Server-bound allocation: Credits belong to a specific guild and are managed separately per server
• Wrong transfer: Transfer with mismatch in amount/name/time/target server information
• Others: Non-Discord/Gmail/Microsoft flow where guild-specific uses rules may apply

2. Payment/Top-up Procedure

2.1 Basic flow

1. User requests payment in the official support server.
2. User makes a bank transfer to the designated account.
3. Operator verifies transfer details.
4. Operator manually charges credits after verification.

2.2 Request template (copy/paste)

[NEXI SMS Payment/Top-up Request]
- Server ID:
- Server Name:
- Credit Package:
- Depositor Name (displayed):
- Transfer Amount:
- Transfer Date/Time (KST):
- Contact Method (Discord ID or email):
- Evidence (optional: transfer receipt/screenshot):

2.3 Data minimization

Only minimum information required for verification/top-up is processed. Sensitive financial data such as account passwords, full card numbers, CVC, resident registration numbers, or OTP codes is not requested, collected, or stored.

2.4 Processing time (SLA)

Target manual top-up time is about one business day. Delays may occur due to bank maintenance, mismatch of transfer information, request spikes, internal maintenance, or force majeure.

3. Credit Policy

3.1 Server-bound allocation

Credits are bound to each server and managed separately. Transfer, assignment, or merge between servers is not supported.

3.2 Deduction rules

• Discord/Gmail/Microsoft: 1 number issuance = 1 credit deduction
• Others: no regular guild credit deduction; guild-specific uses rules may apply

3.3 Mistake handling (wrong target server)

• Before charging: correction is possible after verification.
• After charging: changes are restricted under server-bound allocation.
• However, if operator fault is objectively verified, correction or exceptional settlement may be reviewed to the extent permitted by applicable law.

4. Failure/Automatic Recovery Policy

4.1 Recovery criteria

1. Number issuance itself fails
2. Verification code not received within 20 minutes after number issuance

4.2 Start point of 20-minute timer

The timer follows the original API timeline (number issuance completion timestamp or successful issuance response timestamp).

4.3 Exclusion

No recovery applies when both number issuance and code delivery are confirmed as normal.

4.4 How to verify

• Via panel/commands, operational logs, or support inquiry
• Minimum inquiry info: server ID, request time (KST), target platform, brief issue description, optional evidence

5. Wrong Transfer/Duplicate Transfer/Name Mismatch Handling

5.1 Case handling principles

• Amount mismatch: may be held, partially reflected, or additionally reviewed per policy.
• Name mismatch: additional evidence may be requested before processing.
• Missing identification details: may be held until transfer is clearly identified.
• Duplicate transfer: settlement or future credit reflection may be reviewed per policy and law.
• Wrong-server claim: no transfer/merge processing before verification.

5.2 Evidence deadline

If extra evidence is requested, non-submission within 30 days from request date may result in hold or closure under policy. Re-submitted cases may follow re-verification.

6. Refund/Cancellation Policy

6.1 Principle

Credits are non-refundable in principle due to digital service characteristics.

6.2 Limited exceptions

• Where refund is legally required
• Where material operator fault is confirmed (e.g., duplicate/mischarge)
• Where service provision did not form (e.g., top-up not completed)

6.3 Minimum process

1. Submission via official support server or email
2. Minimum evidence check (server ID, transfer info, reason, evidence)
3. Fact review (logs/records cross-check)
4. Decision notice and settlement execution

6.4 Response timeline

Target first response is within 7-14 business days, subject to factual complexity.

6.5 Transfer fee allocation

If settlement is approved, fee allocation is case-based. Operator-fault cases prioritize operator-side fee burden.

6.6 Exceptional settlement basis

Even where an exception is approved, settlement remains limited and is calculated mainly on objectively verifiable unused paid credits, to the extent permitted by applicable law and this policy.

7. Policy Change/Notice

For key changes (price, deduction, refund, recovery), prior notice of 14 days is provided where feasible. For urgent legal/security reasons, immediate application may occur to the extent permitted by applicable law with post-notice.

8. Contact/Dispute Prevention

• Support server: discord.gg/9gaNYtDHdK
• Email: support@nexiott.shop

Order ID note: Order IDs are server-admin-managed identifiers and may not be accepted as payment proof by this service. The service scope is limited to authentication request identification, error handling, and audit operations.