Support centre
Search the library, jump to a topic, or reach a person. The response times further down are the ones we hold ourselves to — nothing is routed to a queue we do not read.
Ten published articles across eight topics. Results filter as you type.
Eight topics, ten published articles. This is a prototype library: it is small on purpose and grows with the product, so what you see is everything there is.
Each entry is the short answer. Longer walk-throughs, with the arithmetic and the API calls, live in the documentation.
A quoted rate covers one card type on one route. Your effective rate is every charge you actually took — interchange, scheme fees, cross-border, FX spread and per-charge fixed fees, divided by volume.
Understanding your analysis
Soft declines recover on a schedule: do_not_honor, insufficient_funds and processing_error. Hard declines never do — stolen_card, pickup_card and lost_card are terminal, and retrying them costs you a fee per attempt.
Opportunities and enabling fixes
Create a restricted key with read access to charges, balance transactions, payouts and disputes, then paste it into Connect. Pyncht never asks for write scope to run an analysis, and the key can be revoked at your processor at any time.
Connecting a processor
Settlement files, fee lines, payout records and decline logs for the last twelve months. No primary account numbers, no cardholder names, no CVV, and no write access to your processor account.
Account and security
Twelve months of history for an account the size of our sample merchant — 1,425 charges a month, $269,269 in volume — finishes in under an hour. Larger back-catalogues queue and email you when the cost ledger is complete.
Getting started
Token provisioning lags card issuance by a few days, so the first cycle after enablement runs partly untokenised. Expect a dip in week one and a recovery above your previous baseline by week three. The analysis holds both baselines so you can see it.
Opportunities and enabling fixes
Only against the pre-change baseline for the same card mix, ticket size and volume. Seasonal swings are excluded rather than claimed, and every line shows the arithmetic that produced it.
Understanding your analysis
Yes. Plans prorate to the day. The change lands on your next invoice with the old and new lines shown separately, so the amount is reconcilable without contacting us.
Billing and subscription
opportunity.enabled first, then either routing.rule.updated or retry.policy.updated depending on the fix. Both payloads carry the configuration before and after the change, so your audit log does not need a separate read.
API and integrations
The signup IP and timestamp, the cancellation policy the customer accepted, and the run of earlier charges they let stand undisputed. Shipping proof and service logs matter less on recurring billing than proof of an ongoing, accepted relationship.
Disputes and chargebacks
No article matches .
The library is ten articles deep, so this happens. Clear the filters, or send the question to a payments engineer — we answer within one business day.
Every route below is one we operate. The times are targets we measure against, not a contractual service level — Pyncht is a working prototype and says so.
Instant
Every endpoint, every fee definition, and the arithmetic behind each line of the cost ledger. No account needed, nothing gated.
Open the docsWithin one business day
Answered by the payments engineers who built the analysis. Include your account ID and, if it is about a charge, the charge ID.
support@pyncht.com1 hour, named contact
A named engineer, a shared channel, and a one-hour first response on anything touching live volume. Included with an Enterprise agreement.
Talk to salesAPI, dashboard and analysis-pipeline health is published continuously, with incident history and scheduled maintenance. We do not restate it here — a second copy is the copy that goes stale mid-incident.