Paysafe deposits held or reserve set. We answer the risk review, and the bank behind it.
Paysafe card processing runs with a sponsor bank. When Paysafe holds deposits, builds a reserve fund, or terminates, both parties are behind the call. We rebuild the risk read from your statements, answer it with documents the Paysafe Risk Department can check, and push for a reserve tied to real exposure.
Pick what you are seeing. The bar splits one deposit into what reached your bank and what Paysafe kept, and we show which desk to answer.
Processing, the reserve fund, and your deposits. One file.
A termination stops processing, a reserve fund holds your money after it, and a MATCH listing follows you to the next processor. We work each with the party that controls it.
What changesThe review closes with the model disclosed, the descriptor fixed, and a plan the sponsor bank accepted.
What changesThe reserve fund is resized to rebill exposure and earlier months release as disputes age out.
What changesHeld deposits fund once the review has transaction proof and the trigger is answered.
How Paysafe and its sponsor bank decide to release funds.
Paysafe names its Risk Department. The rest we describe by what each function does, and we write to the one that owns your hold.
Held funds are released when each party below has what it needs and signs off.
A Paysafe release needs more than one yes. Open a block to see what that party checks before it signs.
Every suspension has a different pathway. Pick yours.
Paysafe names its suspensions its own way. Each one is owned by a different desk, triggered by different signals, and reinstated by a different route. Pick the one on your notice.
Deposits held
Owned by Paysafe Risk Department
Typical grade: ModerateWhat sets it off
- Unusual activity in a batch
- A dispute spike
What they can prove
- The held transactions
- The agreement’s hold terms
What they infer
- That some sales may not be real or delivered
Our pathway
- 1Pull every held transaction
- 2Attach order and delivery proof
- 3Answer the trigger
- 4Request funding
Held deposits release with transaction level proof.
Reserve fund
Owned by Paysafe Risk Department
Typical grade: DifficultWhat sets it off
- A chargeback ratio above internal limits
- A billing model with delayed disputes
What they can prove
- Chargebacks by cycle
- The reserve fund terms
What they infer
- That all volume carries rebill risk
Our pathway
- 1Split disputes by billing cycle
- 2Fix the descriptor and rebill notice
- 3Model exposure on rebill volume
- 4Request a resized reserve for bank sign off
A reserve fund priced on all volume is too big. We price it on the real risk.
Chargebacks
Owned by Chargebacks and retrievals
Typical grade: DifficultWhat sets it off
- Not recognized disputes
- Canceled recurring disputes
What they can prove
- Dispute counts and reason codes
- Retrieval history
What they infer
- That the merchant cannot control disputes
Our pathway
- 1Answer every retrieval
- 2Fix the descriptor
- 3Add a rebill notice
- 4Show the ratio falling
Descriptor and rebill fixes cut the codes that drive the ratio.
Model change
Owned by Underwriting
Typical grade: ModerateWhat sets it off
- Subscription billing added after boarding
- New products
What they can prove
- What the application said
- What is processed now
What they infer
- That the change was hidden
Our pathway
- 1Disclose in writing
- 2Document the new model
- 3Show cancellation terms
- 4Request an updated profile
Disclosed change reads as growth. Hidden change reads as risk.
Terminated
Owned by Sponsor bank
Typical grade: Hell 1 to 2What sets it off
- Ratios the bank will not carry
- Program breaches
What they can prove
- The processing record
- The termination terms
What they infer
- That the risk cannot be fixed
Our pathway
- 1Get the stated reason
- 2Answer it with records
- 3Claim the reserve separately
- 4Track the release window
Termination ends processing. The reserve still has a release date.
MATCH listing
Owned by Sponsor bank
Typical grade: Hell 3 to 5What sets it off
- A termination reported to the card brands
- A reason code the merchant disputes
What they can prove
- The termination and code entered
What they infer
- That the merchant is a risk to any acquirer
Our pathway
- 1Get the code and reporting party
- 2Gather proof the code is wrong
- 3Request correction
- 4Prepare new applications on the right facts
Only the reporting party can correct a MATCH record.
How long a Paysafe reserve fund should really hold your money.
The agreement sets the outer limit. Your chargeback exposure sets what is actually needed, and that is the number a release request is built on.
Illustrative model. Most card disputes are filed within about 120 days of the sale, and some reason codes allow longer. The one year line reflects the Paysafe agreement version we reviewed. Yours may differ.
After processing ends, chargeback exposure recedes like a tide. The reserve fund does not have to wait for the full hold to start coming back.
Paysafe does not see your request. It sees this.
Behind the notice sits an internal record: your standing on every standard, the identifiers tied to you, and a running log of reviewer notes. This is a generalized view of what the desk is weighing while your case waits in the queue.
Potentially how it looks. A fictitious reconstruction built from our research and quantified only from cases we have handled. It is not a Paysafe screen or tool. Names, IDs, and records are invented or redacted.
Merchant summary
Exposure signals
Paysafe holds deposits and the reserve fund. The sponsor bank and the card brands set the rules behind the call.
Identity
Boarding
Controls
Showing 7 of 12 related records. We explain each one with documents.
The line is an example internal limit, not a card brand threshold. We rebuild this from your statements.
Every flag above is something a reviewer weighs before they read a word of your appeal. Tap one to see what it means and what we do with it.
How to get Paysafe deposits and a reserve fund released, step by step.
Every request passes from us to Paysafe risk and on to the sponsor bank. Each step below shows who talks to whom.
We collect statements and notices
Monthly statements, deposit history, chargeback reports, and every notice.
Monthly statements, deposit history, chargeback reports, and every notice.
- 01Intake
We collect statements and notices
Monthly statements, deposit history, chargeback reports, and every notice.
- Monthly statements
- Deposit history
- Chargeback report
- Risk notices
- 02Trigger
We rebuild the timeline
Volume, disputes, and changes by week until the event that moved the risk is clear.
- Event timeline
- Reason code map
- Descriptor review
- Trigger summary
- 03Grade
We grade the case before you pay
Moderate through Hell case, with funds at risk written down.
- Case grade
- Funds at risk
- Documents still needed
- Working timeline range
- 04Write
We answer the Risk Department
A response and reserve request with an exposure model the bank can approve. Our auditor scores it first.
- Response letter
- Exposure model
- Exhibit index
- Auditor score sheet
- 05Escalate
We keep deposits moving
We track deposits and the reserve balance and escalate only when the record supports it.
- Deposit tracker
- Reply analysis
- Escalation route
- Release log
How a Paysafe case escalates, rung by rung
Risk review response
A complete response to the Paysafe Risk Department.
Most holds are decided here when the records match the question.Reserve reduction request
A written request with an exposure model for Paysafe and the sponsor bank.
Reserves move on data.MATCH correction request
A documented request to the reporting party.
Only that party can correct it.Attorney pre-escalation notice
A letter under the merchant agreement prepared with attorneys, before its dispute step.
The top rung. We prepare the notice with attorneys and hand off to counsel. We do not litigate or arbitrate.Struggling to get it back on your own?
Book a call and we will figure out the path together.
Build your Paysafe case file in four steps.
Answer four questions and see how we would read your case: the desk that owns it, the route, the grade, and what is missing. Nothing is sent until you choose to.
- 1What did you receive
- 2Where does it stand
- 3What applies
- 4What you have
What did Paysafe send you
Where does the case stand today
Tick everything that applies
Which of these can you get
- Desk that owns it
- What they check
- Our route
- Still missing
A preliminary read from four answers. The real grade comes after we read the notice and your file.
Paysafe case, draft
We are the ones merchants come to when every other agency and law firm has already failed.
Every Paysafe case is run against 10,000+ we have already resolved. Its signals are tied to past files, several at a time, until one pattern locks in and the path to a human reviewer shows. We take the files with stacked denials and find the path the last people missed.
We grade every Paysafe case, from Moderate to a deep Hell Case.
Toggle what is true for your account and watch the tier move. We price on difficulty, and we take cases up to Hell 5, where a human path still exists. Levels six and seven we decline before you pay.
- What the desk sees
- How we work it
Moderate
A funding hold on a stable account. Transaction proof and the review answered.
Difficult
Exposure or limit questions without a named cause. Timeline, exposure model, and disclosure.
Hell 1
Ratios or undisclosed changes that raise liability. Source fixed, change disclosed, and the trend shown.
Hell 2
Ratios that pulled in the bank and the card brands. Descriptor fixed, rebill notice live, and the ratio falling.
Hell 3
A terminated account with the reserve held. Reconsideration where supported and a funds claim.
Hell 4
Funds held on the post termination window. An exposure schedule and a dated release request.
Hell 5
A listing that blocks new processing. Correction request with processing history.
Hell 6
Past a human path. We decline before you pay.
Hell 7
No feasible option left. We decline before you pay.
A Paysafe case file, written for Paysafe and its bank.
What the Risk Department and the sponsor bank need to release funds.
The answer to the review with every requested document. Open any column to read it in full. Example content.
Risk response letter
The answer to the review with every requested document.
Event timeline
What changed, when, and what it did to disputes.
Exposure model
Chargeback and refund liability over time.
Chargeback controls
Responses by reason code and the fixes in place.
Release request
The deposit and reserve release request with the schedule asked for.
Open every document in your Paysafe case file.
Each deliverable is built for this platform and this case. Tap one to open it. Contents shown are illustrative.
To: Paysafe Risk Department
Re: Deposits held
1. Root cause
Why funding stopped.
2. Corrective actions taken
Moderate through Hell case, with funds at risk written down.
3. Preventive measures
The answer to the review with every requested document.
Exhibits A to F attached
To: Paysafe Risk Department
Re: Deposits held
1. Root cause
Why funding stopped.
2. Corrective actions taken
Moderate through Hell case, with funds at risk written down.
3. Preventive measures
Chargeback and refund liability over time.
Exhibits A to F attached
To: Paysafe Risk Department
Re: Deposits held
1. Root cause
Why funding stopped.
2. Corrective actions taken
Moderate through Hell case, with funds at risk written down.
3. Preventive measures
The deposit and reserve release request with the schedule asked for.
Exhibits A to F attached
Paysafe Merchant Reserve departments and case types, in plain words.
Pick a category, then open any case to see who reviews it, what triggers it, and what we submit.
Who reviews Paysafe cases
PPaysafe Risk Department
Monitors transaction activity, holds deposits, and sets reserve funds.
Statements and records that explain the flagged activity and show exposure below the reserve.
UUnderwriting
Approves the account and the limits and product mix it was boarded on.
Current business data and a disclosed explanation of any change.
CChargebacks and retrievals
Handles chargebacks and retrieval requests and debits them from deposits.
Evidence by reason code and a falling ratio.
SSponsor bank
The member bank named in your agreement that sponsors processing on the card networks.
Exposure data and controls the bank can rely on.
CCompliance and KYC
Verifies the business, its principals, and its bank account.
Consistent documents for the entity and every principal.
LLegal
Paysafe legal and the sponsor bank for held funds and disputed terms.
A complete record showing funds held past the exposure they cover.
Held deposits and reserve funds
Paysafe noticeHeld depositsHeld deposits
We document transactions for release.
Paysafe Risk Department
Transactions that look out of pattern for the account.
Invoices and delivery records and the review answered.
Paysafe noticeReserve fundReserve fund
We model exposure and request reduction.
Paysafe Risk Department
Exposure from chargebacks or the billing model above what the account supports.
An exposure model by billing cycle from your statements.
Paysafe noticeReserve after terminationReserve after termination
We track exposure to the release date.
Paysafe Risk Department
Open chargeback exposure after processing ended.
An exposure schedule showing when disputes age out and a release request.
Paysafe noticeDelayed fundingDelayed funding
We restore normal timing.
Paysafe Risk Department
Funding timing changed during a review.
A request for the basis and the records that close it.
Paysafe noticeReserve set at boardingReserve set at boarding
A reserve fund required before processing started.
Underwriting
A new merchant or model rated as higher risk.
Processing history from past accounts and a review date.
Termination and closure
Paysafe noticeMerchant account terminatedMerchant account terminated
We pursue reasons and funds.
Sponsor bank
Risk the bank and Paysafe decided not to carry.
The account record and a claim on held funds.
Paysafe noticeTermination without noticeTermination without notice
We secure statements and the balance.
Legal
A termination with little warning.
A request for the reason, statements, and the release schedule.
Paysafe noticeSponsor bank exitSponsor bank exit
We map who holds funds after the exit.
Sponsor bank
A bank relationship ending for a portfolio.
A map of who holds funds after the exit and a release request.
Paysafe noticeISO relationship endedISO relationship ended
The reseller that boarded you stopped working with Paysafe.
Legal
A portfolio moved or closed.
A map of the parties now holding funds and a release request.
MATCH and terminated merchant files
Paysafe noticeMATCH listingMATCH listing
We contest through the reporting party.
Sponsor bank
A terminated merchant reported to the card brands.
A correction request to the reporting party.
Paysafe noticeWrong reason codeWrong reason code
We document why the code does not fit.
Sponsor bank
A reason code that does not fit the facts.
Processing and dispute history supporting the right code.
Paysafe noticePrincipal listed with the businessPrincipal listed with the business
We separate the principal record.
Sponsor bank
A principal named on the termination record.
Records separating the principal’s role.
Paysafe noticeListing found at a new applicationListing found at a new application
A MATCH record discovered when another processor declines.
Sponsor bank
A listing the merchant was not told about.
A request for the record and the basis for it.
Underwriting and risk
Paysafe noticeVolume over approved limitVolume over approved limit
We disclose growth and request new limits.
Underwriting
Volume or ticket above the approval.
Sales data, fulfillment proof, and a limit request.
Paysafe noticeHigh-risk category reviewHigh-risk category review
We document what you really sell.
Underwriting
A product read as higher risk.
Product and fulfillment records that show the real profile.
Paysafe noticeBusiness model changeBusiness model change
We disclose and document the change.
Underwriting
A billing model that differs from boarding.
A written disclosure with supporting records.
Paysafe noticeAverage ticket above approvalAverage ticket above approval
Tickets higher than the application stated.
Underwriting
Transactions above the approved ticket.
Pricing records and a limit update request.
Chargebacks and fraud
Paysafe noticeExcessive chargebacksExcessive chargebacks
We fix the source and represent.
Chargebacks and retrievals
Disputes above internal and card brand levels.
Reason code analysis, representment, and the source fix.
Paysafe noticeCard network monitoringCard network monitoring
We reduce ratios below thresholds.
Sponsor bank
Ratios that place the account in a card brand program.
A month by month plan and data showing the ratio falling.
Paysafe noticeDescriptor confusion disputesDescriptor confusion disputes
We fix the descriptor and answer disputes.
Chargebacks and retrievals
Not recognized disputes from a descriptor customers do not know.
A corrected descriptor and responses with brand proof.
Paysafe noticeRetrieval requests unansweredRetrieval requests unanswered
Copy requests that turned into chargebacks.
Chargebacks and retrievals
Retrievals with no response on file.
Receipts and order records per retrieval.
Verification and escalation
Paysafe noticeKYC reviewKYC review
We align entity and principal documents.
Compliance and KYC
Entity or principal details that need confirming.
Matching entity and principal documents.
Paysafe noticeBank verificationBank verification
We verify the deposit account.
Compliance and KYC
A deposit account not yet verified.
A bank letter or statement in the entity’s name.
Paysafe noticeLegal letterLegal letter
Attorney-reviewed letters under the merchant agreement.
Legal
A complete record showing funds held without basis.
A letter under the merchant agreement prepared with attorneys.
Paysafe noticePrincipal change reviewPrincipal change review
A new principal triggers a review.
Compliance and KYC
A change in ownership on file.
Ownership documents and new principal details.
Your Paysafe case may not be listed here. We have likely seen it.
We have handled far more Paysafe case types than fit on one page, including rare notices, stacked decisions, and cases no one could name. Send it over and we will work out the path with you.
What clients ask us first.
If yours is not here, the fastest answer comes from sending us the notice.
Why is Paysafe holding my deposits?
Usually a risk review after a rise in chargebacks, volume over the approved limit, or unusual activity. We find which one from your statements and answer it.
How long can Paysafe keep my reserve fund?
It depends on your agreement. The version we reviewed allows up to a year after termination or last activity, or longer where reasonably needed. We show when exposure really ends.
Who decides a Paysafe reserve?
The Paysafe Risk Department, inside rules the sponsor bank and card brands apply. We write so both can approve.
Is Paysafe the same as Skrill?
Skrill and NETELLER are Paysafe digital wallets. Card processing merchant accounts run on separate agreements.
Can a MATCH listing be removed?
Only by the party that reported it, when the listing or reason code is wrong. We prepare that request.
Can I open a new merchant account?
We do not help anyone open a new account to get around a closure. That is evasion, and it makes every later request harder.
Do you guarantee release?
No. Paysafe and its bank decide. We commit to the right party, a complete response, and escalation through the right channels.
The operators, brands, and firms that trust us.
Some agreed to be named. Most cannot be. Here is the part of the roster we are allowed to show.
Send us your Paysafe notice. We will find what moved the risk.
The case read is free and confidential.
- A strategist reads your notice before the call
- You leave with the route and the grade in writing
- No fee to talk, no obligation after