A requirements brief for your current payment arrangement

Make the requirement something an offer can fail

A request for better processing, a backup, or a lower cost is not yet a requirement. A requirement names one observed gap and the statement a later written offer has to make about that gap. If the offer does not mention the gap, it does not meet the requirement. You are writing that test now, before an offer is in hand. Scoring offers you have already received is a later task, and it cannot start from a test you have not written.

Keep one problem on each line. A checkout that does not complete, a notice that names a limit, and a settlement practice that does not match your records are different gaps. Folding them into one sentence makes it impossible to see which part an offer answered. This page does not decide whether you should add a second provider. It only states what the current arrangement fails to do.

Do not redescribe the business in order to describe the change

The thing that may change is the payment arrangement. The legal entity, the public business name, and the catalog the site actually sells stay as they are. Prism's features page treats the catalog, promotional content, store policies, and business disclosures as one picture. A requirement that asks a provider to review a narrower catalog than the live site, or a public name that is not the business, is a contradiction, not a requirement.

Stripe's account setup guide says a Stripe merchant provides information about the business, the product, and the person's relationship to the business. It also says the business name, website, support contacts, and statement descriptor that customers see should be clearly associated with you. Use that only as a consistency test when Stripe is the provider you are describing. It is not a reason to hide products, and it is not a finding that Stripe will process this catalog. If the provider is not Stripe, keep the same rule against a mismatched description and ask that provider what it compares.

Write down constraints the current arrangement already fixed

Some facts are no longer wishes. They are written in the current agreement, on a notice, or in that provider's own account rules. The brief records them as constraints the next offer has to live with, or has to say it cannot meet. It does not record them as already solved.

One Stripe limit is narrow. Stripe's setup guide says that after a Stripe service is activated on a live account, the business origin country cannot be changed. If your brief needs a different country, that point is unresolved on that account. This page does not tell you to open another account. Ask the provider you are actually speaking with what country its written offer uses, and leave the answer blank until that writing exists. Do not copy this Stripe limit onto a different provider.

Stripe's balance guide says Stripe might create a reserve balance that holds funds until the reserve hold period is complete. The same guide says settlement timing varies by country and by payment method, and that risk criteria might keep an account on its initial timing instead of the default. A line such as 'no reserve,' or a payout speed copied from Stripe's country table, is not a fact this brief can settle. The measurable requirement is that the offer states, in writing, whether a reserve can be applied and what payout timing it actually offers for this account.

Decide the brief, and leave the provider's decision alone

You can decide which problems are in the brief, which records you will rely on, and which sentences an offer must contain before you will treat it as responsive. You can also say which published Prism support type you are asking about: a review of storefront content, preparation for a card-processing conversation, or help connecting a provider's website questions to the pages involved. Prism's solutions page says that, for a processing conversation, Prism can help organize website findings and the questions to raise, and that you should bring the current situation and what you need to change. Scope, fees, and service terms are discussed before that work. The solutions page does not list a fee.

You cannot decide eligibility, approval, price, a reserve, or whether an account stays open. Prism's features page says the provider determines eligibility, approval, and account terms through its own underwriting, and that a website review does not guarantee approval or continued processing. Prism's resources page describes underwriting as that provider's assessment and says processing approval remains the provider's decision. Requirements depend on the products, the practices, the jurisdiction, and the provider. A research-use-only label on the site does not answer the assessment.

The contact form is how you ask Prism to discuss the brief. It asks for your name, email, role, an optional company, and a message with the website, the research-only products, and the question, including any relevant provider feedback. Prism reviews the inquiry and follows up by email. The request does not book a time, buy a service, or submit a processing application. The contact page lists tom@prismpro.io and does not state a response time. Do not send card numbers, passwords, or customer records. The worksheet does not submit or save entries. Send only a non-sensitive summary through the contact form.

What has to stay unknown

Whether any provider will accept the business, on what terms, and on what date, is unknown until that provider says so in writing about this business. The Prism pages checked for this guide do not list accepted countries, accepted products, processor relationships, or a fee schedule. Do not fill those gaps from another company's advertisement or from memory.

If you do not have the notice, the agreement clause, or the screen that shows the problem, the row stays blank. An unknown is a usable result. A guessed requirement will not match the offer when you later compare written proposals.

Requirements brief

Use one row for one observed gap. The last column is the question you will ask a provider, in your own words. Leave the row blank when you cannot point to a record. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.