This guide explains how RASEDI tracks a payment from the moment it is created until the money is paid out to you. Knowing what each status means helps you answer customer questions, choose the right next action and reconcile your payouts.

---

1. Core payment statuses #

Pending

• What it means: The payment has been created, but the final result is not known yet. This can include cases where the customer is still on the checkout page, 3‑D Secure verification is in progress, or the acquirer has not yet responded.
• What you should do: Wait. Do not ship goods or deliver services until the status changes to Success or Failed. If a payment stays Pending for longer than your normal processing time, you can contact support or ask the customer to try again.

Success

• What it means: The payment was authorized and captured successfully by the gateway. The customer has been charged and the amount is now part of your available or upcoming balance (depending on settlement rules).
• What you should do: It is safe to fulfill the order or deliver the service. You can also issue refunds later if needed.

Failed

• What it means: The payment could not be completed. This may be due to card declines, insufficient funds, authentication failure, risk checks or technical errors. No money is captured.
• What you should do: Do not fulfill the order. Review the failure reason shown in the payment details and, if appropriate, ask the customer to try a different payment method or contact their bank.

Voided

• What it means: An authorization was cancelled before capture. This usually happens when you explicitly void a payment, or when an authorization expires. The customer will not be charged (or their bank will release the hold).
• What you should do: Treat it like a failed payment for fulfillment purposes. If you still need to collect payment, create a new payment or Payment Link.

Refunded

• What it means: Some or all of a previously successful payment has been returned to the customer. The refund amount and date are recorded in the payment details and ledger.
• What you should do: Confirm that the refund amount is correct and inform the customer of any expected time for the funds to appear in their account (this depends on the card or bank). Remember that refunds reduce your net income and may affect upcoming payouts.

---

2. Eligibility, settlement and withdrawal statuses #

In addition to the core payment status, RASEDI shows three settlement‑related states. These describe where the money is in the journey from customer to your bank account.

Eligibility status

• Indicates whether a successful payment is ready to be included in a payout batch.
• Common values:
  • Eligible – The payment meets all criteria (for example, past the risk delay period) and can be settled.
  • Not eligible – The payment is too new, under review or otherwise held.
• Action: If a payment stays “Not eligible” longer than expected, check for disputes, risk flags or compliance requirements.

Settlement status

• Describes whether the payment has been grouped into a settlement batch.
• Common values:
  • Not settled – The payment is still in your processing balance.
  • Settled – The payment has been included in a settlement batch that will move funds toward your payout balance.
• Action: Use this to match payments with settlement reports when reconciling against your acquirer or internal ledger.

Withdrawal status

• Reflects whether the settled funds have actually been paid out to your bank or wallet.
• Common values:
  • Pending – Included in a payout that has been created but not yet completed.
  • Processing – The payout is in progress at the bank.
  • Paid – Funds have been successfully sent to your bank account.
  • Blocked / Failed – The payout could not be completed (for example, invalid bank details).
• Action: For “Paid,” you should be able to see the amount on your bank statement. For “Blocked” or “Failed,” update your payout details or contact support before attempting another withdrawal.

---

3. Typical payment lifecycle #

Below is a high‑level lifecycle you can map to a simple diagram in your docs:

1. Payment created → Status: Pending
2. Authorized & captured → Status: Success
3. Becomes eligible → Eligibility: Eligible
4. Added to settlement batch → Settlement: Settled
5. Included in payout → Withdrawal: Pending / Processing
6. Funds arrive in your bank → Withdrawal: Paid

Alternative paths:

• If the authorization fails → Status: Failed, no eligibility or settlement.
• If you cancel before capture → Status: Voided.
• If you refund after success → Status: Refunded (full or partial), with updated settlement and withdrawal calculations.

---

4. Recommended actions by state #

You can summarize recommended behavior in your documentation as:

• Pending – Wait; do not fulfill. If stuck, investigate or ask the customer to retry.
• Success + Eligible – Safe to fulfill; expect it to appear in the next settlement/payout cycle.
• Success but Not eligible – Monitor; check for risk review or compliance holds.
• Settled, Withdrawal Pending/Processing – Can be matched in settlement reports; wait for the bank.
• Withdrawal Paid – Consider the payment fully completed from your perspective.
• Failed / Voided – No charge; offer another payment attempt.
• Refunded – Customer has been (or will be) credited; reflect this in your internal systems and communication.

Use these statuses together—payment, eligibility, settlement, withdrawal—to understand exactly where each transaction stands and to keep your operations, finance and support teams aligned.