Plain answers for organizations.

From a financial source the person the proof is about authorized for that request, reached through an approved, authenticated channel. RunPayway™ establishes the fact from that evidence; it does not ask anyone to state a figure and it does not accept one. Where a provider supplies the evidence, the provider supplies evidence and RunPayway™ establishes the fact. The proof semantics are RunPayway’s, and no provider is named here because none is in use: nothing in this release reaches a financial source at all.

No, and no design change would make it possible. A VERIFIED proof rests on evidence from an approved financial source. A number somebody types, a screenshot, an editable PDF, or an email from anybody saying the money is there cannot produce VERIFIED, because none of them is evidence about an account. Weaker evidence channels, if they are ever offered, are treated as what they are rather than promoted to the top assurance state.

Because connecting is not owning, and the two are established separately. Signing in shows that somebody operated a session and that an institution accepted a credential. It does not show whose account was read, or that the account holder is the person this proof is about. RunPayway™ has to establish the required ownership or control relationship between the proof subject and the source, and that relationship is a kind rather than a yes or no: sole, joint, trust, business, authorized control and other governed relationships are not weaker versions of each other. Where the required relationship is not established, the result is NEEDS ATTENTION and no automatic VERIFIED is issued.

The proof continues to say what it always said: that the requested fact was established from the authorized evidence at the stated time. It does not update itself, and it does not become false. It becomes old. That is what the freshness fields and the proof status are for, and it is why a recipient who needs a current answer asks for a refresh rather than rereading an old proof.

No. VERIFIED is a statement about authorized evidence at a stated time, and never a statement about the future. It does not mean the funds will still be there at closing, that they are unencumbered, that the person is creditworthy, or that your organization should proceed. RunPayway™ establishes the requested fact at the stated time, and nothing more.

Each proof carries three times rather than a claim: when the source says the evidence applied, when RunPayway™ evaluated it, and when another check is required. There is no single freshness period and RunPayway™ does not publish one, because how recent evidence must be depends on the proof type, the request, your policy, the source, the asset and the method version in force.

Its result does not change and its status does. A proof can legitimately read VERIFIED and EXPIRED at the same time, which means the fact was established when it was established and the proof is no longer fresh enough for the requirement in front of you. The result and the status are separate axes on purpose, and a surface that collapses them is defective.

A PDF or a screenshot can be altered, which is why neither is the authority. The authority is the RunPayway™ verification record, and a recipient checks the proof against that record rather than against the document in front of them. Issuance and the verification record are being built. No proof is issued today, so there is nothing yet to alter or to check.

By checking it, not by looking at it. Each issued proof is designed to have a verification record showing the proof reference, who it is about, the fact and threshold requested, when it was verified, and whether it is current, superseded, expired, revoked or disputed. The record never exposes the financial evidence behind the proof. None of it is live yet: nothing is issued today, and this answer will say so until that changes.

A proof is bound to the subject it is about, to the request it answers, to the method that established it and to the time the evidence applied. Presenting somebody else's proof as your own is presenting a document about a different person, and the verification record is what makes that checkable rather than a matter of trust.

RunPayway™ does not conclude from evidence it cannot rely on. Where the evidence is stale, incomplete, contradicted or anomalous, the result is NEEDS ATTENTION and a specific issue is named. A human reviewer may resolve an ambiguity, ask for more evidence, or settle how a piece of evidence should be classified. A reviewer may never type in a figure, invent an ownership relationship, or issue VERIFIED because a transaction matters.

Nothing is estimated. RunPayway™ does not add every balance it can see: where the same account appears through two sources, where a transfer could be counted twice, or where sources disagree about ownership or about what is true, the result is NEEDS ATTENTION. Conflict does not produce a best guess.

Then it is not counted twice, and it does not quietly become VERIFIED either. RunPayway™ does not simply add up every balance it can see: money in flight can legitimately appear in two places at once, and the same account can be reached through two sources. Where the evidence could materially count the same funds twice and the duplication is not resolved, the result is NEEDS ATTENTION rather than an estimate.

That RunPayway™ could not establish the requested fact from the authorized evidence. It is a statement about what the evidence supported, not a denial, not a decline, and not a judgment about anybody. It does not mean the person lacks the funds; it means this request, on this evidence, did not establish the fact that was asked about. What your organization does with that is your decision, as it would be with any other result.

No, and it is built so that it cannot. RunPayway™ establishes the requested fact. Which funds your organization counts, how recent it needs them to be and what it excludes are your policy; whether to proceed is your decision. No result carries an approval, a decline, a score or a recommendation, and none of that vocabulary exists anywhere in the proof domain.

No. No proof does, and one that implied it would be making a claim about the future from evidence about the past. If a current answer is needed at closing, the proof is refreshed at that point: RunPayway™ rechecks the authorized evidence and issues a new proof, marking the previous one superseded rather than rewriting it.

It is not a replacement for it. A lender underwriting a loan may need detailed asset evidence, and RunPayway™ neither performs that work nor substitutes for it. RunPayway™ answers the narrower question: when a specific financial fact is what is actually needed, it establishes that fact from authorized evidence and returns a proof instead of the underlying financial file. The lender retains the underwriting decision. Prove the requested fact; do not disclose the file.

Statements disclose everything and answer one question. A proof answers the question and discloses nothing else: the result, the threshold, who it is about, when the evidence applied and when it was verified. What changes is what is exchanged, not who decides.

No, and there is nothing in the product that could. RunPayway™ establishes what is true about money; it never holds, moves, directs or takes custody of the funds a proof is about, and it initiates no transfer and no payment. A proof is a statement of fact, not an instruction to anybody. RunPayway™ is the truth layer around money, not the movement of it.

Underwriting asks whether the lender should lend, and weighs everything that bears on it. RunPayway™ establishes one requested financial fact from authorized evidence. It does not replace underwriting, does not stand in for asset verification, and produces no approval. The lender retains the lending decision.

No. RunPayway™ does not approve a borrower, recommend or compare lenders, price anything, or originate anything. It reports what the authorized evidence established against the fact that was requested.

No. A proof is an input to the organization's process, not the outcome of it. The organization retains full authority over what it does next, and remains responsible for the action it takes.

VERIFIED means qualifying authorized evidence established the requested fact. NEEDS ATTENTION means something specific has to be resolved before RunPayway™ can determine the result. NOT VERIFIED means the requested fact could not be established from the authorized evidence. There is no fourth result and there is no score.

No. VERIFIED is not an approval, a guarantee, an underwriting decision, or a recommendation to proceed. It means the requested fact was established from the authorized evidence at the stated time, and nothing beyond that.

The evaluation stops rather than estimating. Where missing or conflicting evidence could change the result, RunPayway™ returns NEEDS ATTENTION and names what has to be settled. Evidence that was not supplied is never treated as zero.

It is designed as a layer inside the process an organization already runs, not a system to move into. Staff request one financial fact against the case the organization already holds, the person it is about authorizes their own financial sources, and the proof that comes back is filed against the originating case.

No. There are no named third-party connectors today, and no automated access to any lending or servicing system. What exists is a contract that accepts and returns case and source references, plus a manual path that requires no integration at all. Integration is scoped with the organization.

A subject reference, a case or record reference, a source system, and a staff reference. An organization identifier and a caller-supplied idempotency key are additionally accepted for an integrating system. These are returned on the issued record so it can be filed against the originating case without re-keying it.

No, and this is enforced rather than promised. Case and source references are carried as provenance only. They are never passed to the method, it never reads them, and they are returned alongside the result rather than inside it, so the result hash stays a hash of the evidence alone. The same evidence produces the same result regardless of which case it was filed under.

Yes. Staff sign in to an administrator-provisioned account, and every read and every write filters on the owning organization taken from the validated session rather than from request data. A record belonging to another organization does not resolve, and the response is the same not-found a record which never existed would receive. Access is still scoped with each organization through a written pilot; there is no self-service sign-up.

Yes, and deliberately. A completed record is kept as something your organization can open, download as a governed file, and hand to an examiner who has no account here. The figures, the result, the result hash and the method version are what the engine issued, and no operation in the product changes them. What is protected that way is protected by the application: there is no database constraint or cryptographic seal enforcing it below the application, and the security page says so.

Through the contact page. Access, deployment, and terms are scoped directly with each organization while the first fact class is in use. There is no self-service sign-up, and RunPayway™ is not sold to the people proofs are about.

Yes. The same governed evidence produces the same calculations and the same result, regardless of who ran it. The method version is attached to every record, so one issued today can be read later against the rules that were in force when it was issued.

Yes. Every material figure carries the calculation module that produced it and the evidence it was built from, so a member of staff can explain any number on the record rather than asserting it.

No. The calculations, the completeness rules, the thresholds, and the result are deterministic and defined in code. No model authors a figure, decides completeness, or influences a result.

No. RunPayway™ provides financial proof infrastructure, not financial, legal, tax, or investment advice, and not an underwriting or lending decision. What an organization pays for is the governed evaluation, never a particular result: no commercial arrangement changes the method, the evidence requirements, the thresholds or the warnings. RunPayway™ states what the authorized evidence established, and deciding what to do about it stays with the organization.

No. There is no document upload, no extraction, and no optical character recognition. Which is also why the product reports unresolved evidence rather than inferring what a missing document would have said.