This Pjok3 deposit and withdrawal page explains the difference between submitting a request, making a payment, having it credited to a balance and the recipient receiving money. A success message at one stage does not establish that every later stage is complete. Account access information helps clarify identity and access questions. Then check which stage a money-related record describes. This page explains general processes and problem checks; it does not promise particular channels, limits, fees or processing times.
Each stage has its own result and record
For a deposit, the payment channel's record and the service's balance record may be separate. For a withdrawal, acceptance, verification, processing and money appearing in the recipient's account are also distinct events. This Pjok3 comparison helps identify the stage concerned. Use the Help page when the meaning of a message or the next action is unclear. Keep the relevant reference, amount, time and status together to make a mismatch easier to identify.

| Stage | Relevant record | What it means | What to compare | Next action | What not to assume |
|---|---|---|---|---|---|
| Preparation check | Recipient details | Preparing to make a payment | Destination and applicable conditions | Match the identity and recipient | Stop if details are unclear |
| Deposit request | Request reference | The service has received a request | Check the amount and status | Follow the same request | This is not a payment |
| Payment authorisation | Channel instructions | You have authorised payment | Check the recipient and amount | Keep the result | Do not assume the balance is credited |
| Channel processing | Channel status | The channel's work is unfinished | Whether it completes or fails | Avoid paying again | Do not assume success |
| Deposit credited | Service transaction record | The deposit is recorded in the balance | Match it with the channel result | If they differ, identify both records | A receipt alone is not enough |
| Withdrawal application | Application reference | A request to receive money | Check recipient and applicable conditions | Follow one application | This is not money sent |
| Verification stage | Verification message | Required details are being compared | What information is requested and why | Reply through the appropriate route | Do not share verification codes |
| Application processing | Current service status | The application is being handled | Identify the stage still pending | Keep the specific reference | Do not assume a fixed duration |
| Money sent | Sending reference | The sender's stage is complete | Match the recipient and channel | Check the recipient's record | Receipt is still a separate stage |
| Receipt confirmed | Recipient transaction record | There is a record of receipt | Match the amount and transaction | Record the final outcome | A refund and a deposit are different |
Key differences between deposits and withdrawals
When reading Pjok3 transaction explanations, separate the direction of money from the type of evidence. A deposit goes from your side towards a service account; a withdrawal requests movement in the opposite direction. Both require the effective conditions and actual transaction records.
Deposit request and payment
A deposit request may only state the amount or process you intend to use. Check the channel's authorisation and result separately. If the request page closes or the connection is lost, inspect the earlier request and channel record before sending money again.

Crediting and balance
A successful channel result does not establish that the money appeared in the service account at the same moment. Compare the amount, recipient and reference. If the balance differs, compare the two sides of the same event rather than refreshing and submitting more requests.
Application and verification
A withdrawal application starts a request for money; it does not guarantee payment. If information is requested to compare identity, recipient details or applicable conditions, understand what is needed and the authorised route for supplying it. Do not send personal documents in public messages or insecure conversations.
Sending and receipt
A sender's record of money sent and a recipient's record of money received are different results. Compare the sending reference, recipient and amount with the channel's record. A reduced balance alone does not confirm receipt, while repeating the same application can complicate enquiries.
Conditions to understand before starting
Reading the applicable conditions before a money-related decision helps explain later results. Pjok3's preparation checklist is separate from an operating service's own conditions; the terms displayed for the particular request need attention.
- Your identity: check that account and recipient details match as required. Do not create inconsistencies by using another person's details.
- Recipient accuracy: confirm the name, identifying details and direction of money. Correcting a wrong recipient is more than reopening a page.
- Amount and currency: match the stated amount and accounting currency. Fees or conversion, where applicable, may make the total paid and amount received different.
- Balance type: deposited, reward and withdrawable amounts may differ. Understand which condition applies to each portion.
- One action at a time: do not repeat an action before knowing the earlier result. Repetition can create two separate transactions.
Useful records when asking for help
A small set of related details can explain where a mismatch arose. Link the references for the same event while leaving out unnecessary personal information. An initial explanation can be clear without exposing a complete receipt or confidential identity details.

- Transaction identity: distinguish the request and channel references where relevant. Do not publish full reference numbers in public.
- Amount and time: state how much money was involved, when the event happened and the time zone. Identify Bangladesh time as Dhaka time.
- Status changes: explain the earlier status, what is shown now and which action preceded the change.
- Exact error wording: do not replace a message with your own assumption. Keep the relevant wording or a screenshot with personal information hidden.
- Leave out secrets: do not send passwords, one-time codes, complete card details or full identity documents by ordinary email. The problem-reporting explanation helps organise symptoms and the sequence of events. Also make clear whether you are asking about an article or an actual money-related request.
A changed status changes the next question
Processing, failed, refunded and completed do not mean the same thing. If one stage fails, check separately what happened to the money. Where a status is unclear, establish the outcome of that particular event before starting another request.
- Processing: the result is not final. Keep the last known status and relevant reference. Bonus conditions may impose separate limits on reward or withdrawable amounts. Eligibility and the technical result of a transaction are different questions.
- Failed: identify which stage failed. Even if a request says failed, check whether the channel deducted money.
- Refunded: check the relevant record to establish whether money returned to its original source. Cancellation of an application alone does not prove a refund.
- Sent but not visible: compare the sending reference, recipient and receiving channel's status. A new application alone does not resolve the earlier one.
- Two requests: identify each reference separately. Do not merge two records merely because their amounts match. Account help helps distinguish an access or verification problem from a question about money status.
Locating the mismatch and the next question
This comparison does not decide liability. It identifies which record and stage need explanation first. Questions about Pjok3 content can be raised here, while an independent service's decisions on sending, refunding or approving money follow that service's own process.

| Symptom | Check first | Explanation needed | What to keep | What to avoid |
|---|---|---|---|---|
| Money deducted, no credit | Channel and balance records | Matching payment with crediting | References from both sides | Sending money again |
| Application held at verification | The specific information request | Which comparison is incomplete | The relevant message passage | Sending documents insecurely |
| Sent, but not received | Sender and recipient records | The receiving stage's outcome | Sending reference and recipient | Blindly applying again |
| Marked refunded, no money | The original payment record | Refund status and destination | The link between original and refund | Decisions based on guessed timing |
Further explanation and contact
The Help centre explains how to arrange details around a particular symptom. Briefly describe the event before asking a service or channel, so the stage whose result you need is clear.


Transaction stages at a glance
Subject
Readers in Bangladesh
Bangla & English
Stages and statuses
Records of the same event
Scope
Read before deciding