Building a useful payment-provider support dossier
Keep one dossier for one issue. Record the date you observed it, any reference the provider already gave you, the behavior you actually saw, the business operation it affects, the documents you already have, what was already replied, and one question that is still unanswered. You can decide what belongs in that record and which of the provider's own channels receives it. Only the provider can decide the outcome, the queue, or whether the case moves. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a business that sells peptides for laboratory research use only and has one provider issue that is still unresolved.
Updated 2026-09-21
One issue, one record
A payout you cannot match, a catalog question, and a fee line you cannot tie to the agreement are different issues. Putting them in one message makes the next reply harder to match to any of them. This page is the record for a single unresolved issue. A contradictory pair of answers, a reserve release, and a payout comparison each have their own guide.
Start from the latest written notice or the screen you can still open. Write what it says. Do not replace it with a shorter story about what you think the provider meant. If you have no reference number yet, say that. An invented ticket number is worse than a blank.
What you can settle before you write
You can settle the contents of the dossier. That means the date, the reference, the observed behavior, the operation that stopped or changed, the documents already in your files, and the reply you already received. You can also settle the single question you want answered next, stated so that a yes, a no, or a specific fact would close it.
You cannot settle the provider's decision from this page. A complete record does not change an account status, move a payout, or establish that a prior reply was wrong. If two replies conflict, keep both and ask which one controls. Do not drop the older reply to make the file look consistent.
Use the provider's own channel, and only the facts that channel needs
Stripe's help article for businesses using Stripe through a platform says to start with the platform for most questions, and to contact Stripe through the Stripe Dashboard about a specific charge, refund, payout, or dispute, an account issue such as a lockout, or Dashboard settings. It says to log in before submitting, so Stripe can tell which account the request concerns, and to include formatted identifiers. It says never to send a full card number or CVC. If the question is about a card, it says the expiration date, the last four digits, and the card brand can be included. It gives charge identifiers that begin with ch_ or py_, and transfer identifiers that begin with tr_, as examples of formatted identifiers.
That article is Stripe's guidance for that situation. It is not a support route for a different provider, and it does not publish an escalation ladder or a response time. If your provider is not Stripe, use the contact method printed in that provider's dashboard or agreement. Do not borrow Stripe's identifier prefixes for another company's case numbers.
Leave out anything the question does not need. Prism's contact page tells merchants to leave payment card details, passwords, and customer records out of the consultation form. The same limit belongs on a provider message: no full card number, no CVC, no password, and no customer list. A payout or charge identifier is not a customer list. An export that includes customer names, email addresses, and addresses is.
Confirm the owner of each follow-up
Prism's solutions page describes three kinds of support, arranged through a consultation: a review of public storefront content, preparation for a card-processing review, and help connecting a provider's website questions to the pages, claims, or policies involved. Scope, fees, and terms are discussed before work. The provider decides whether a response meets its requirements.
Describe the specific payout, fee, account, or website question so its scope and responsible party can be confirmed. Identify whether the issue concerns the website, the payment account, or both; confirm any provider follow-up in the agreed scope. The dossier still goes to the provider through the provider's channel.
The contact form asks for your name, email, role, and a message about the website, the research-only products, and the question. Company is optional. Follow-up is by email. Sending the form does not book a time, buy a service, or submit a processing application. There is no published response time.
Issue dossier
Use one copy of this table for one unresolved issue. Leave a row blank when you do not have the document. Do not invent a reference, a date, or a reply. 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.
Issue dossier. The last column is for temporary notes.
Item
What belongs in the record
Where you get it
Your notes
Date you observed the issue
What belongs in the recordRecord the date the screen, notice, or bank record changed. A later date, when you decided to write, is a different fact.
Where you get itThe notice, the dashboard history, or your own dated note of what you saw.
Reference the provider already issued
What belongs in the recordUse the ticket, payout, charge, or transfer identifier exactly as the provider printed it. Stripe's platform help article points to charge identifiers beginning ch_ or py_ and transfer identifiers beginning tr_ for Stripe questions. Another provider's reference will not use those prefixes.
Where you get itThe provider's reply or the dashboard object for this issue. Leave blank if none exists.
Behavior you actually saw
What belongs in the recordWrite the status word, the amount, and the screen or sentence. Do not translate that into a cause such as a reserve, a review, or a bank delay unless the document says so.
Where you get itThe dashboard entry or the notice. Quote the status. Do not paraphrase it into a diagnosis.
Business operation affected
What belongs in the recordName the operation that cannot proceed, such as paying a supplier, refunding an order already taken, or answering the provider's website question. Do not include a customer list to prove the operation exists.
Where you get itYour order or payout records, reduced to the operation and the date. Not a customer export.
Documents you already have
What belongs in the recordList the notice, agreement section, dashboard export, or bank line you will attach. Attach the identifier and the dates, not passwords and not full card numbers.
Where you get itYour own files. Stripe's article says not to send a full card number or CVC.
What was already replied
What belongs in the recordCopy the prior reply that still matters, including a reply you disagree with. Deleting it does not close the question.
Where you get itThe provider's earlier message. If there has been no reply, write that.
The one question still open
What belongs in the recordAsk for one fact or one decision, such as which status applies or which written term covers the line. A second issue needs a second dossier.
Where you get itYour draft message. Stop when one unanswered request is explicit.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Do not send a full card number, a CVC, a password, or a customer list to the provider or through Prism's form.
Stripe's logged-in Dashboard route and identifier examples apply to Stripe questions. They are not another provider's support process, and they are not a response-time promise.
Stripe help: getting started through a platform — checked 2026-09-21. For Stripe used through a platform, Stripe says to contact support from the Dashboard while logged in, to include formatted identifiers, and never to send a full card number or CVC. Charge identifiers can begin with ch_ or py_, and transfer identifiers with tr_.
Prism solutions — checked 2026-09-21. Published support is storefront review, card-processing preparation, and help with a provider's website questions. The provider decides whether a response meets its requirements. Scope, fees, and terms are discussed before work.
Prism contact — checked 2026-09-21. The form asks for identity, role, and a message about the website, research-only products, and the question. Company is optional. Follow-up is by email. The request does not book a time, purchase a service, or submit a processing application. Card details, passwords, and customer records are excluded.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.