Nexus Pay is the NSDS payment product. It is live at mynexuspay.com, it takes card payments, and it is what this site uses to charge for a paid consultation at the moment the meeting is booked.
Payment acceptance is one of the most common blockers we meet. A business with a working website cannot take a card payment without an onboarding process that takes months, or cannot reconcile what it does receive, or cannot support the payment method its customers actually use.
Every platform we built ran into the same wall. Rather than keep routing around it, we built the thing.
A checkout session is created against an order and the customer is taken to a hosted payment page, so card details never touch your own site.
Payment results arrive as signed events with a replay window, so an order is marked paid by a verified event rather than by a customer returning to a page.
Requests carry an idempotency key, so a retry after a dropped connection cannot take a second payment.
A plugin connects a WordPress site to a merchant account, which is how the paid consultation on this site is charged.
Nexus Pay is live and taking real payments, and it is the product formerly listed here as NSDS Pay. It now carries its own brand and its own domain at mynexuspay.com. What is available to any given merchant depends on onboarding and on the market, so the honest answer about your own situation comes from a conversation rather than from this page.
Yes. Nexus Pay is live. What applies to your business depends on onboarding and on your market, so tell us what you sell and where, and we will tell you what is possible.
Yes. It was listed here as NSDS Pay while it was on the roadmap. It is now a live product with its own brand and domain.
No. The customer completes payment on a hosted page, and your site receives a signed event confirming the result.
Tell us what payment problem you are trying to solve.
