Which product did that price sell?

A customer says they bought the plan with the name, or says the charge was for something else. Tonight, three proofs, in a console you administer. Name the product that price sells: the price id, the product id on that price, and the unit amount. Show a different price whose product id, or whose amount, is not this one. Show another account's list that does not contain this price. If any of the three needs the person who wired checkout, you have not shown the product. You have a display name and a guess.

This is the method on one price. It is not the payout. Which payout did that charge settle? is the payout id, the status, and the amount that left. A price can be active while no payout exists, and a payout can succeed while this price is no longer the one on the product. It is not the figure they were shown. Show the price they accepted is the amount on the screen at acceptance. A screen can be right while the price object points at a different product. It is not the subscription. Which status is that subscription in? is one of the names a subscription stores. A price type of recurring is not a subscription status. It is not the branch a pull request targeted, and it is not the store a file joined. Those are later, and they are not this id.

None of what follows is a rate for this product, and none of it is legal advice. The fields below are one processor's current description of a price and of a product. The counts below that are a 2024 model of other companies' pricing pages. A unit amount is not a census of your customers. A paper that never opened your catalog cannot name the product on the price you charged tonight. They do tell you which numbers people mix up when they try to sound precise about a product they have not opened.

Stripe's sample price prints id price_1MoBy5LkdIwHu7ixZhnattbh, object price, active true, billing_scheme per_unit, created 1679431181, currency usd, and unit_amount 1000. The same object prints unit_amount_decimal as the string 1000. 1000 the integer is not the string, and the page does not print a dollar sign next to either. Do not rewrite 1000 as ten dollars until you have named the currency's smallest unit yourself. The id is 30 characters. The product field on that object is prod_NZKdYqrwEYx6iK, which is 19 characters. 30 is not 19. custom_unit_amount is null. lookup_key is null. nickname is null. metadata is an empty object. livemode is false. tax_behavior is unspecified. tiers_mode is null. transform_quantity is null. type is recurring. A null nickname is not a missing price. False on livemode means the sample is not a live charge on your account (Stripe, The Price object).

The recurring hash is not the product. interval is month. interval_count is 1. trial_period_days is null. usage_type is licensed. 1 is not 1000, and month is not a product id. licensed is not metered. The attribute text says usage_type can be metered or licensed, and that it defaults to licensed. Two names. billing_scheme can be per_unit or tiered. Two names, and the sample is the first. type can be one_time or recurring. Two names, and the sample is the second. tax_behavior can be exclusive, inclusive, or unspecified. Three names, and the sample is the third. Three is not two. A lookup key may be up to 200 characters. The sample's lookup_key is null, and null is not a 200-character string. 200 is not 30, and it is not 19.

The product object is a different sample, and the name people remember is not the id. The product sample prints id prod_NWjs8kKbJWmuuc, also 19 characters, object product, active true, name Gold Plan, created 1678833149, and updated 1678833149. Gold Plan is 9 characters. 9 is not 19. The two product ids are the same length and they are not the same string. prod_NZKdYqrwEYx6iK is the id on the price. prod_NWjs8kKbJWmuuc is the id on the product page. Do not paste one into the other because both start with prod_. default_price is null. description is null. images is an empty array. marketing_features is an empty array. package_dimensions is null. shippable is null. statement_descriptor is null. tax_code is null. unit_label is null. url is null. A null default price is not the price id, and an empty image list is not a missing product. Created and updated are the same integer, so the gap on the product sample is 0. 0 is not 1679431181 (Stripe, The Product object).

Subtract the product's created integer from the price's created integer and the difference is 598032 seconds. Six days is 518400 seconds, because 6 times 86400 is 518400. The remainder is 79632 seconds. 598032 is not 518400, so the gap is not six days. Seven days is 604800. 604800 minus 598032 is 6768, so the gap is not seven days either. 79632 seconds is 22 hours, 7 minutes, and 12 seconds: 22 times 3600 is 79200, and 79632 minus 79200 is 432, and 432 is 7 times 60 plus 12. The page does not print that split. Do not round the gap to a week. 598032 is also not 1000, and it is not 0, the gap on the product sample itself. The product's updated time equals its created time. The price was not created at that instant.

The create call is where the name and the id part company. Creating a price can send product_data name Gold Plan, currency usd, unit_amount 1000, and a recurring interval of month. The response then prints the price id above and the product id prod_NZKdYqrwEYx6iK. Gold Plan is the product sample's name and the create example's name. It is not a field on the price object, whose nickname is null. The returned product id is still not prod_NWjs8kKbJWmuuc. The parameter text says only one of unit_amount and unit_amount_decimal can be set. The object example sets both, the integer 1000 and the string 1000. A rule that says only one, printed next to an example that carries both, is not a license to pick the one you prefer. Write what the object you opened actually stores. The version header on the example is 2026-10-28.endive. That string is 17 characters. 17 is not 30, and it is not a timestamp (Stripe, Create a price).

The list call is a third page, and its request is not the size of the catalog. The example asks for limit 3 and returns object list, has_more false, and a data array of 1. The one object is price_1MoBy5LkdIwHu7ixZhnattbh again, with the same product id and the same unit_amount 1000. 1 is not 3. The parameter text says the limit can range from 1 to 100, and the default is 10. 3 is not 10. 10 is not 100. 100 is not 1000. has_more false means this page did not claim a further page. It does not mean the account holds one price. lookup_keys on a list filter can name up to 10 keys. 10 is not the 200-character maximum on a single lookup_key, and the sample key is still null. An empty result would be a data array of 0. This example is not empty. It is one row, and that row is the same id as the object page (Stripe, List all prices).

The caps on the product are not the caps on the price. Images is a list of up to 8 URLs. marketing_features is a list of up to 15. The sample holds 0 of each. 0 is not 8, and 8 is not 15. 15 is not 100, the list maximum, and it is not 1, the number of prices in the list example. A statement descriptor, when several products are billed together, uses the first one. The sample's statement_descriptor is null, so there is no first string to quote. Do not invent one from Gold Plan. 9 characters of name are not a descriptor, and null is not Gold Plan.

The study people reach for when they want a catalog did not open a processor console. Alejandro García-Fernández, José Antonio Parejo, and Antonio Ruiz-Cortés introduce Pricing4SaaS and say its expressiveness is shown on 16 distinct popular SaaS systems. The same paper, two sections later, says the model followed an in-depth analysis of the pricing of 13 real-world SaaS. 16 is not 13. 13 divided by 16 is 0.8125, which is 81.25%. The page does not print 81.25%. Do not average the two counts, and do not cite 16 as if the methods sentence had said 16. The running example is Zoom. The figure they describe is three plans, which manage 10 features, and two add-ons, which manage one feature each. 10 plus 1 plus 1 is 12. 12 is not 16, and 12 is not 13, and 3 plans are not 10 features. The page does not print 12. The huge-meetings add-on allows up to 1000 participants. 1000 participants is not the price sample's unit_amount 1000, and it is not a product id (García-Fernández, Parejo, and Ruiz-Cortés, Pricing4SaaS).

The types they list are a cut of the page, not a price object. They name eight feature types: domain, integration, automation, management, information, guarantee, support, and payment. Eight names. They name four groups of usage limits: renewable, non-renewable, response-driven, and time-driven. Four names. 8 is not 4. A validity section then gives three conditions a pricing must meet. 3 is not 8, and 3 is not 4. Eight feature types are not two Stripe type names, and four limit groups are not three tax behaviors. They also mention OpenAI's models as constrained by tokens. A token is not prod_NZKdYqrwEYx6iK, and a token is not unit_amount 1000. None of these integers is the 30-character price id. A model of someone else's pricing page does not tell you which product your price stores.

Do the three proofs on one real price, in the console that actually holds it. First, the binding. Copy the price id, the product id, the currency, the unit amount, and the type. If unit_amount is 1000 and unit_amount_decimal is the string 1000, write both and write that they are not the same type. If the product id is not the id on the product you think you sell, write both ids. Do not promote Gold Plan into an id because a sample uses that name. If nickname is null, write null. If default_price on the product is null, write null. Do not infer the sample's 1000 because an example prints it. Second, the other price. A different price, with a different id, or a different product id, is not this one. A chart of sixteen companies is not that second price. If you cannot show a price that is not this one, you have a counter, not a record. Third, the other account. A list that belongs to someone else does not contain this price id. If the only list is a single shared table and you cannot say whose price it is, write that. A tenant you cannot name is the finding.

Three moves feel like the proof and are a second problem. Renaming the product because the customer used a different word, before you have copied the id. A name change does not tell you which price you were looking at. Quoting 16 systems, or 13, because one of them looks precise, while the price you were asked about is one row, and the companies in that paper had not opened your charge. Asking a model which product it was. The model will pick a plausible name. It will not open the price. A payout you have not kept, while the customer is arguing about money that already moved, is which payout did that charge settle?. Opening that screen does not name the product id.

The path is ordinary when an operator can open one merchant's price without opening the next merchant's price as the way to prove it. PayOrch is a payment orchestration dashboard: wallets, providers, merchants, fees, and fraud controls in one view. The shape that matters here is one price you can point at, in an account you administer, distinct from the next merchant's price. That case is not a product catalog. Nothing in the description is a headcount, a duration, or a result figure. If the only control on the screen changes every merchant's catalog together, you do not have this proof. You have a totals page.

There is a version of this afternoon where hiring the path is the wrong purchase. Nothing is for sale, because the product does not take money yet. You have no product. You are still choosing who will build, and the document in front of you is a term sheet. The criteria for that choice sit on the page written for a top SaaS development company. That page is criteria. It does not rank anyone, including us. The only fact in the room is a count of other companies' pricing pages. 16 is not your product, and 13 is not your product, and 1000 is not your product. A customer has already seen another customer's catalog. Naming a plan does not close a leak. Or you wanted a lawyer to say whether a price is a contract. Hire the lawyer.

When the price is real and the console cannot name the product, the missing object is specific. An admin action, in an account you administer, that shows one price id, one product id, and one unit amount, shows a different price that is not that one, and shows another account's list without it. A startup software development company that expects this will have put that action next to the rest of the billing screen, before a stranger's complaint is the way you discover the vendor owns the catalog. One that needs a call in order for you to see which product is stored is telling you who holds the case. If the first slice is a fixed capability, an AI integration sprint is the shape where the acceptance sentence can include the three proofs. If you do not yet know which system stores the price, a two-week AI readiness assessment maps the systems. The findings are yours. They are not a promise that a paper's count of companies applies, and they are not 1000.

The branch a pull targeted, and the store a file joined, are different objects: which branch did that pull target? and which store did that file join?. Do not record either on this page. A base ref is not a product id. A store id is not a unit amount. The coupon a checkout applied is a different object: which coupon did that checkout apply?. Do not record it here. A coupon id is not a product id.

Before you tell them which plan they bought, do the three proofs and write the ids. Name the price, the product, and the amount, or write that no price was stored. Show a different price that is not that one. Show another account's list that does not hold it. Do not rename the product to avoid reading the id, and do not ask a model which of the sample names it was. A paper can tell you how a model counted other companies' plans. The binding is the product you can defend.