Status updated
Primer down?
Primer is a unified payments infrastructure and orchestration platform. It lets merchants connect multiple payment service providers, fraud tools and payment methods through a single integration, then design payment flows visually with no-code workflows. Primer's universal checkout supports cards, wallets and local payment methods, while features like smart routing, fallbacks and network tokens help increase authorisation rates. Merchants also get unified reporting and observability across processors. E-commerce, travel and subscription businesses use Primer to optimise payments globally.
I have a problem with Primer
Select the type of problem you're facing to help us and other users.
Recent User Report Trends for Primer
Aggregated reports in the last 48 hours.
No user reports about Primer in the last 48 hours.
View live report trends
Add your report to help, or tap to skip
Report a problem to see the chart, or skip
What is Primer's current status?
All systems are operational
No active incidents reported.
Incident history: past 7 days
times in UTCToday
Yesterday
Oct 28, 2026
Oct 27, 2026
Oct 26, 2026
User Reports for Primer
Recent issues reported by users from around the world.
No user reports for Primer in the last 30 days.
Experiencing an issue? Add your report:
Stop refreshing this page
We'll email you the moment Primer goes down — and again when it's back.
About Primer & Technical Insights
What this service does and the technologies behind it.
Read the tech stack as text▾
Overview: A no-code Webflow marketing site layered with custom LitElement components, animation libraries, and a global CDN/edge stack for a payments platform.
What stands out
- The combining of Webflow with Lit and Parcel suggests a split between marketing-owned content and developer-owned interactive components.
- Multiple CDNs (unpkg, jsDelivr, Google Hosted Libraries) along with CloudFront indicate a performance-focused global delivery strategy.
- Finsweet and Swiper show investment in advanced Webflow interactions, likely for product tours and customer stories.
- Presence of both Parcel and Webpack hints at legacy scripts or third-party embeds coexisting with a modern build pipeline.
Technologies primer.io uses
- AWS Certificate Manager — Manages SSL certificates for CloudFront, ensuring HTTPS on all assets.
- Google Font API — Provides web fonts for consistent typography.
- Finsweet — Extends Webflow with custom attributes for filtering, CMS logic, and advanced interactions.
- parcel — Bundler for custom modules, suggesting developer-built components beyond Webflow's standard site.
- Swiper — Touch slider/carousel library for customer testimonials and feature showcases.
- Amazon CloudFront — Content delivery network for global low-latency asset delivery, reflecting international audience.
- Linkedin Insight Tag — Tracks B2B visitors and retargets on LinkedIn, aligning with enterprise sales.
- GSAP — Animation library for scroll-triggered and timeline effects, enhancing marketing storytelling.
- lit-html — Rendering library for Lit components, efficient DOM updates for interactive payment calculators.
- Cloudflare — DNS and security layer in front of origin, mitigating threats and caching content.
- LottieFiles — Serves Lottie animations, used for polished product motion without heavy video.
- jsDelivr — Serves open-source JS packages like Swiper from a multi-CDN, improving load times.
- Amazon Web Services — Cloud infrastructure backbone, hosting assets and services for the site.
- jQuery — Legacy DOM library used by Webflow and some plugins.
- lit-element — Encapsulates custom web components, enabling dynamic UI elements on a mostly static Webflow site.
- Webpack — Bundler for JavaScript assets, indicating custom frontend tooling.
- Webflow — No-code CMS and hosting for marketing pages, allowing rapid content updates by marketing.
- Unpkg — CDN for npm packages, delivering Lit and other dependencies directly to the browser.
- Google Tag Manager — Deploys marketing/analytics tags without code changes.
- SWC — Transpiles modern JavaScript in build tooling, indicating a performance-minded frontend codebase.
- Google Hosted Libraries — Loads jQuery and other common libraries from Google's CDN for reliability.
- HSTS — Forces browsers to use HTTPS, protecting payment-related content.
How these technologies work together
- lit-element requires lit-html — LitElement uses lit-html for efficient, declarative DOM templates in custom payment components.
- Amazon CloudFront requires AWS Certificate Manager — ACM issues certificates that CloudFront uses to serve content over HTTPS.
- Amazon CloudFront runs on Amazon Web Services — CloudFront runs on AWS's global network, providing CDN for site assets.
- parcel requires SWC — Parcel uses SWC to transpile modern JavaScript and TypeScript during builds.
- Finsweet integrates with Webflow — Finsweet attributes add CMS filtering and custom interactions to Webflow without writing JavaScript.
- lit-element requires Unpkg — unpkg serves the lit-element package directly to browsers, enabling custom components delivery.
- GSAP works alongside LottieFiles — LottieFiles supplies lightweight vector animations while GSAP orchestrates scroll and timeline effects.
- Google Tag Manager integrates with Linkedin Insight Tag — GTM loads LinkedIn Insight Tag to track B2B visitors and power retargeting.
- Swiper integrates with Webflow — Swiper adds responsive carousels to Webflow sections for testimonials and feature highlights.
- lit-element integrates with Webflow — LitElement components embed dynamic functionality into Webflow's otherwise static marketing pages.
- Google Hosted Libraries requires jQuery — Google Hosted Libraries serves the jQuery library that Webflow and plugins depend on.
- Cloudflare integrates with Webflow — Cloudflare fronts the Webflow site for DNS, caching, and DDoS protection.
- jsDelivr requires Swiper — jsDelivr serves the Swiper carousel library from multiple CDN locations, ensuring fast global delivery.
- Google Font API integrates with Webflow — Webflow integrates Google Font API to load brand fonts across the site.
- parcel overlaps with Webpack — Two JavaScript bundlers suggest separate build pipelines for Webflow custom code and other assets.
Trust & Safety Checks
Public registration, DNS and certificate records UptimeCard checked independently for the domain primer.io.
Secure, encrypted connection
Everything sent to this site is encrypted, using a valid certificate from Amazon.
DNS managed by AWS Route 53
4 nameservers answer for this domain, so it stays reachable even if one goes offline.
Hosted by Amazon.com, Inc.
Served from professional infrastructure located in United States.
Records last verified August 2026.
How to fix Primer not working
Primer is a payments platform that connects a business to many payment providers and methods through one integration, with checkout and routing tools. Developers and payments teams use it. Find your symptom below. A failed payment affects a real customer, so check its status before you retry. Never share card data or API secrets in a support message.
Jump to what you are seeing
Payment Failed
A payment is declined, or it fails inside a payment flow. A bank or card decision is the usual reason, and a routing rule can also send a payment to a provider that does not accept it.
- Read the decline or error code on the payment. It usually says whether the bank declined it or the request was invalid.
- If the bank declined it, ask the customer to check with their bank or to try another method.
- Check your routing rules for that method and country, since a rule can send a payment to a provider that does not support it.
- Do not retry a charge until you have checked its status, so the customer is not charged twice.
API Down
Calls to the Primer API fail or time out.
- Check the status code. A 401 or 403 means the key or permission is wrong, a 429 means too many calls, and a 5xx means a platform-side problem.
- Check you are using the key for the right environment. Test and live keys are separate.
- Retry with a growing delay, and check the payment status before you retry any charge.
- Check status.primer.io if several calls fail together.
Dashboard Down
The Primer dashboard does not load, or shows an error.
- Reload in a private window with extensions turned off.
- Check your role allows the page you are opening.
- Try another browser. If one section fails, note its name and the time.
Checkout Not Loading
The checkout does not show, or stops partway, so customers cannot pay.
- Test the checkout in a private window with script blockers off.
- Check the checkout script on the page is the current version.
- Check the payment methods you have enabled are available for the customer's country and currency.
- If checkout fails for everyone, check status.primer.io and send the page address and the time to support.
Webhooks Delayed
Events from Primer reach your system late, or not at all.
- Check your endpoint address is still correct and reachable from the internet.
- Check your endpoint answers quickly with a success response. A slow endpoint causes retries.
- Check the status page for a webhook delay.
- Make sure your system handles an event that arrives twice, since retries can send the same event more than once.
Website Down
The Primer website does not load for you.
- Open the page in a private window and on another network.
- Check status.primer.io for an active incident.
- If only your network is affected, ask IT to check the firewall.
Login Failed
Sign-in to the dashboard is refused.
- If the message says the password is wrong, reset it and check spam.
- Check you are signing in to the organisation your team uses.
- Ask your administrator to confirm your user has access.
Still not working?
If it still does not work, contact Primer support through the help option in the dashboard or on primer.io. Have your organisation name, the payment or transaction reference, the exact error or decline code, the environment (test or live), and the time it happened with your time zone. Never send card data or API secrets in a support message. Live incident updates are on status.primer.io.
Most payment-orchestration problems come from a decline, a routing rule or an endpoint setting, and they usually clear once that is checked. The status page shows live platform incidents, so you can see whether the problem is on Primer's side.
Frequently asked questions about Primer
Is Primer down right now?
No. Based on the latest status data on this page, Primer (primer.io) is up and running normally. The most recent incident, "Security disclosure notice removed from status page", was resolved (last update Oct 30, 2026).
What should I do if Primer is not working for me?
First rule out your side: reload the page, try another browser or device, clear the cache and cookies for primer.io, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.
What was the most recent Primer incident?
The most recent incident on record is "Security disclosure notice removed from status page", last updated on Oct 30, 2026. It has been resolved.
How many people reported problems with Primer recently?
No user reports about Primer were submitted in the last 48 hours.
How do I report a problem with Primer?
Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.
Where is the official Primer status page?
The official status page for Primer is status.primer.io.
Related Services & Domains
Other websites and services in the same category as primer.io.
Related Keywords
Common themes, topics and technologies associated with primer.io.