- Browser-only Proposal Analyzer
- Local Deal Spec builder
- Portable Provider Review Pack
- Provider Review Room and response export
- Local response matching and buyer decision export
Trust architecture
Trust should be designed into the deal.
Ratly32’s current beta helps define the agreement. The roadmap connects evidence, decisions, and payment state only after the required product, operating, legal, and partner controls exist.
Honest product status
Use what is live. See what still has to be built.
- Live invitations and verified accounts
- Shared two-sided deal records
- Evidence and acceptance records
- Versioned change history
- Electronic signatures
- Funded milestones and payouts
- Operational dispute handling
Ratly32 does not currently hold deal funds, provide escrow, execute signatures, or decide disputes. Any future payment service will disclose the licensed provider, countries, fees, and exact safeguarding model before use.
A trustworthy service transaction defines acceptance and evidence before delivery, separates AI assistance from human judgment, and discloses the actual payment structure. Ratly32 currently supports the planning layer, not custody or dispute operations.
Mutual terms
Neither side should discover the rules after work begins.
Evidence over impressions
Milestones use the proof both sides chose to demonstrate delivery.
No hidden acceptance rule
Ratly32 does not interpret silence as substantive acceptance. Any provider deadline or automatic release rule must be disclosed separately.
Human case review
AI may organize a case, but only a person or institution authorized by the contract, provider rules, or law can make a binding decision.
AI organizes, not judges
AI can structure a timeline and surface contradictions. It does not decide the dispute.
Minimum necessary data
Sensitive proposal material should be redacted and access-controlled.
Proof follows the agreement.
Files, code, project records, messages, tests, and metrics matter only in the context both sides accepted.
Payment path · staged
Money follows proof—not the roadmap.
Each stage must name the party that holds funds and the rules that release them. A payout delay is not automatically legal escrow.
| Stage | Who holds the money | Ratly32’s role | Accurate customer language |
|---|---|---|---|
| Live now | No deal funds in Ratly32 | Proposal analysis and Deal Spec only | “Payment happens outside Ratly32.” |
| Validation step | The seller’s named payment provider | Record a transaction reference and visible status; no custody | “Paid through [named provider].” |
| Candidate pilot | Escrow.com, only if the service and both parties are approved | Create a milestone transaction and mirror provider status | “Escrow is provided by Escrow.com under its terms.” |
| Later corridors | A named licensed or regulated provider for each corridor | Orchestrate onboarding, reconciliation, evidence, and status | Describe holder, fees, release, refunds, and chargeback exposure exactly. |
Stripe Connect and Adyen for Platforms can control payout timing, but their public documentation does not make either product a neutral escrow service. Escrow.com documents milestone transactions and lists Israel as supported; eligibility still depends on the parties, service, payment method, commercial approval, and legal structure. Stripe manual payouts · Adyen custom payouts · Escrow.com milestone API · Escrow.com supported countries
Escrow.com’s documented inspection period can end in release if the buyer does not act. A pilot would therefore require an explicit countdown, reminders, contract language, and a deliberate decision on whether that rule fits the service. Escrow.com inspection-period rules
Operating design · not live
A visible dispute path.
The planned system should reduce ambiguity before work begins. Any later review process must be consistent, documented, and human.
Pause
A future flow may request or reflect a provider-supported pause, where available and before release. Ratly32 cannot freeze funds it does not hold.
Assemble
The planned record would organize scope, changes, messages, submissions, and evidence into one timeline.
Review
A trained person—not an automated score—would examine the record against the agreed criteria and identify the authority for the next decision.
Route
The case would be routed to the buyer, provider, payment partner, mediator, or court that is actually authorized to act.
Payment language matters. If launched, Ratly32 will name the actual provider and explain who holds funds, when release occurs, what happens after rejection, and where chargeback or legal rights remain. It will not describe payout control as escrow or imply that a provider’s license automatically covers Ratly32.
Israel’s Regulation of Payment Services and Payment Initiation Law took effect on June 6, 2024. Any operating model that participates in money movement needs corridor-specific legal review; using a regulated partner is necessary in many structures but is not an automatic exemption. Knesset legislation record
Next move
Clarity is the first layer of protection.
Start by finding the ambiguity in the proposal already in front of you.