Data map

Payment, charge and operation identifiers, so every attempt is unique and replays never double-count.

Stored in minor units, so totals never suffer from rounding.

Authorized, manual review, issuer declined, blocked or invalid.

Approved by the network, declined by the network, never sent, or reversed after approval.

The processor's plain code, such as insufficient funds or expired card.

The issuer's own response (51, 05, 54, N7…) and whether it was received or inferred.

Mastercard Merchant Advice Codes that say whether to try again.

The processor's free-text reason, kept for the merchant view only.

Checkout, rescue, follow-up link or an organic retry.

When each try happened, giving retry gaps and time-of-day patterns.

Authorized and captured amounts and timing, for split shipments and partial captures.

Gateway response time and timeouts per attempt.

The scheme's reference, needed to link a retry to the original decline.

Visa, Mastercard, American Express, Discover or other.

Credit, debit or prepaid.

Where the card was issued, for domestic vs cross-border splits.

The bank behind the card, for an issuer league table.

A stable, non-reversible card identity that links attempts without storing the number.

Rewards, business or corporate tier, to see which products decline more.

Lets Lasso warn before a stored card expires.

Whether a payment came from Apple Pay, Google Pay or a network token.

Stored-credential flag for each payment.

Pass, fail, unavailable or not checked.

Whether the ZIP matches the bank's record.

Whether the street address matches.

The processor's own risk read on the attempt.

Whether a bank verification step was tried.

Frictionless or challenge flow, and whether it passed.

Who carries the fraud risk after a verified payment.

Which of your own fraud rules blocked the payment.

Attempts per card, email and device in a window.

Used for receipts and, only with consent, follow-ups.

So rescue copy and follow-ups use the shopper's language.

Whether the shopper agreed to a pay-later link. No consent, no message.

From the card fingerprint and earlier paid orders.

How long the customer account has existed.

What the shopper has spent, to decide how hard to fight for them.

Members, VIPs and subscribers.

Past tickets and refunds, to spot friction.

Where the goods are going, compared with the card's country.

Pending, paid or abandoned.

Standard, express or pickup and what it cost.

The promo code or concierge offer that changed the price.

How long checkout took, and how long a recovery took.

Which products and sizes were in the basket.

So Lasso can price a rescue offer without losing money.

Whether an item was low or sold out when the shopper paid.

Referrer, campaign or affiliate behind the order.

Each remedy shown, accepted or dismissed, with its remedy ID.

Every initial try, retry and blocked retry per card, with the reason.

The Visa category of the decline that preceded each retry.

Scheduled, sent, paid or expired, with the send time.

Whether a follow-up reached the shopper. Simulated delivery is labelled as such.

From an email or SMS provider.

Whether the sale came back by a fixed field, a new card, a wallet or a pay-later link.

Open, resolved, declined or handed off.

Budget, shipping, promo, question, availability or other.

What the shopper asked and what the concierge answered, with source labelled.

Discounts, free shipping, promo codes and restock alerts, and whether each was accepted.

Percent off and the cap, so margin given away can be totalled.

Product page, bag or checkout.

Which unavailable sizes shoppers reach for most.

Demo, Stripe sandbox or Visa sandbox, kept apart on every chart.

Type, receipt time, retries, lag and errors.

State of each hosted-checkout operation and its last status check.

Card-on-file, network tokens and 3-D Secure settings, which gate the recommendations.

When each connection last brought data in.

Known outages, to separate a processor problem from a real decline.

Which acquirer or merchant account handled a payment.

When money lands, for cash-flow forecasts.

Phone, tablet or desktop, and which browser.

Slow forms often mean a confusing field.

Which input gets retyped most, the typo hot spot.

Where abandoning shoppers dropped off.

A mismatch that explains some bank blocks.

Signals that raise issuer suspicion.

Full and partial refunds and their timing.

Reason codes and outcomes, to judge whether recovered sales stay sold.

Whether a subscription renewal paid, for involuntary-churn reporting.

When a stored card was refreshed automatically.