An application asks for a cross-border sales percentage

Turn the application label into a reproducible question

The words cross-border sales do not, by themselves, identify which two countries to compare. Ask the provider to name the transaction geography and the reference geography. A billing-country comparison, an issuer-country comparison and a delivery-country comparison are separate measures even when they happen to agree for some orders. Also establish whether the reference is the contracting entity's country, the payment account's country or another expressly named location.

Keep the reply with the version of the application you are answering. Record whether the provider wants a historical percentage or a forecast. If it wants history, a planned market does not belong in the observed record set. If it wants a forecast, label the estimate and its basis separately from completed activity. A definition received for a different provider's form is not automatically the definition for this one.

Map the requested geography to a real field

Inspect the available order and payment exports without rewriting their column names. Record which field contains the billing country, which contains the delivery country and whether an issuer-country field is actually available. Identify the payment or order reference that lets the relevant records be matched internally. A column called country needs its own definition; its label alone does not establish whose country it is.

Where the requested field is missing, mark the record unclassified. Do not fill an absent issuer country from a delivery address or infer a billing country from a currency. Stripe's currencies documentation describes currency-specific amount and settlement constraints; it does not supply the geographic definition for another provider's application. A common currency is not a documented country match, and a currency conversion is not a substitute for the requested country comparison.

A disagreement between fields is not necessarily an error. Preserve each recorded value and classify using the provider's named field. If that field itself looks unreliable, keep the inconsistency visible and identify the record that needs clarification instead of selecting a more favorable field.

Keep the numerator and denominator on the same basis

Once the definition is confirmed, the percentage is the cross-border portion divided by the defined total, multiplied by 100. For a count-based request, both parts are counts of the same eligible record type. For a value-based request, both are amounts on the same agreed reporting basis. Do not divide the value of cross-border payments by the number of all orders, or compare captured amounts on one side with order totals on the other.

Use the same reporting dates, time zone, accounts and sales channels for both parts. Ask how refunds, canceled orders and partially captured payments enter the requested measure when the form does not say. If amounts use multiple currencies, agree the reporting currency and conversion basis rather than adding unlike amounts. These are calculation choices that must follow this request, not universal underwriting rules.

Keep the number or value of unclassified records alongside the result. Excluding them silently can make an incomplete calculation look complete. Obtain the provider's treatment of those records before presenting the result as the full percentage it requested. If the defined total is zero, the percentage cannot be calculated; disclose that there is no eligible activity instead of entering zero percent cross-border.

Deliver the definition with the figure

A useful answer contains the percentage, the period, the comparison used, the count-or-value basis and the unresolved coverage. Retain the unchanged source exports and your calculation separately so the result can be traced without altering the history. If the provider has not clarified the field, give it the available-field summary and the exact open question rather than an unsupported single figure.

Stripe's restricted-business policy prohibits misleading information about the business. That policy is Stripe's; it does not define every provider's cross-border metric or decide whether your research-only catalog is eligible. Accurate measurement supports an accurate application, not approval. For a Prism processing consultation, describe the application question and which aggregate fields you have. Scope, responsibilities, fees and terms must be agreed before work begins.

Cross-border metric definition sheet

Complete this for one provider request using field names and aggregate coverage, not customer addresses. A missing definition or an unresolved unclassified group means the percentage is not yet a complete answer. Keep the detailed calculation in your own controlled records.

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. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.