New: Invisible Enforcement SDKs for PHP, Node & Python

Ethical payment enforcement for real-world client work.

Ship confidently. DevPayr adds a discreet, non-destructive enforcement layer to your software, activating only when invoices are overdue — fully controlled by you, invisible until triggered.

Non-destructive Client-safe Full control 3-minute setup

Join the Waitlist Watch a Demo

Bootstrap

import { DevPayr } from '@xultech/devpayr';

DevPayr.bootstrap({
  license: 'YOUR-LICENSE',
  secret: 'your secret key',
  base_url: 'https://api.devpayr.com',
  action: 'boot',
  injectables: true,
  invalidBehavior: 'modal',
  onReady: (res) => console.log('✅', res)
});

<?php
require 'vendor/autoload.php';
use DevPayr\DevPayr;
use DevPayr\Exceptions\DevPayrException;

try {
    DevPayr::bootstrap([
        'license'         => 'YOUR-LICENSE-KEY',
        'injectables'     => true,
        'invalidBehavior' => 'modal',
    ]);
    echo "License valid.";
} catch (DevPayrException $e) {
    echo "DevPayr error: ".$e->getMessage();
}

from devpayr import DevPayr

DevPayr.bootstrap({
  "license": "YOUR-LICENSE",
  "api_key": "YOUR-API-KEY",
  "base_url": "https://api.devpayr.dev/api/v1/",
  "secret": "shared-secret",
  "injectables": True,
  "invalidBehavior": "modal",
  "onReady": lambda d: print("✅", d)
})

npm i @xultech/devpayr composer require devpayr/devpayr pip install devpayr

Why teams choose DevPayr

Invisible when everything’s fine. Precise when it’s not. DevPayr adds a quiet, ethical guardrail that protects your work—without breaking trust.

Non-destructive enforcement

No data locks, no vandalism. Apply gentle limits or guidance when invoices slip.

Client-safe by design

Clear messaging and reversible actions keep relationships healthy while you get paid.

3-minute setup

Install SDK, call bootstrap, pick your behavior. Works with Node, PHP, and Python.

API integration for custom dev & ops

Extend workflows via REST—sync status to your CI/CD, billing, or support tooling.

Realtime restoration

Payment clears → access restored instantly. No redeploys needed.

Audit-ready logging

Every check is traceable. Use log-only behavior in staging to tune rules safely.

Pick your enforcement style

Choose how DevPayr responds when invoices are overdue. Switch and preview below.

Payment required

Your license appears overdue. Please settle your invoice to continue.

Pay Now

Behavior can be changed anytime. Restoration is instant on payment confirmation.

Quick start (Node)

import { DevPayr } from '@xultech/devpayr';

DevPayr.bootstrap({
  license: 'YOUR-LICENSE',
  base_url: 'https://api.devpayr.com',
  invalidBehavior: 'modal',          // or: 'redirect' | 'silent' | 'log'
  redirectUrl: '/billing/upgrade',   // optional
  onReady: (d) => console.log('✅', d)
});

REST API (Custom integrations)

# Sync license status into your own systems
curl -H "Authorization: Bearer <API_KEY>" \
     "https://api.devpayr.com/v1/licenses/<LICENSE_ID>/status"

# Example JSON response
# { "license": "...", "status": "ok|overdue|blocked", "updated_at": "..." }

3min

Typical setup time

Enforcement styles

∞

Reversible, client-safe

Built for your workflow

From solo projects to multi-client studios, DevPayr safeguards delivery with ethical, reversible enforcement.

Ship confidently, collect respectfully

Protect premium features when invoices slip — without burning bridges.
Clear messaging and reversible actions maintain client trust.
Automate follow-ups while you focus on delivery.

3min

Typical setup time

Vendor lock-in

Simple SDK call

Join the Waitlist

DevPayr Console

Payment required

Your license appears overdue. Please settle your invoice to continue.

Pay Now

import { DevPayr } from '@xultech/devpayr';

DevPayr.bootstrap({
  license: 'YOUR-LICENSE',
  base_url: 'https://api.devpayr.com',
  invalidBehavior: 'modal',
  onReady: (d) => console.log('✅', d)
});

// REST status check (custom ops)
// curl -H "Authorization: Bearer <API_KEY>" https://api.devpayr.com/v1/licenses/<LICENSE_ID>/status

Why we built DevPayr

A manifesto for people who build — and deserve to be paid fairly.

We’ve watched brilliant designers and developers pour themselves into client work only to be ghosted when the invoice arrives. We’ve seen it happen on well-known “protective” platforms too. The fees were real; the protection often wasn’t. And yes — we’ve been burned ourselves.

Each time, the choice felt impossible: surrender control to intermediaries who don’t fight for you, or gamble your livelihood on trust. There wasn’t a real solution on the horizon. So we built one.

DevPayr is a quiet contract of respect. It doesn’t hold your money or dictate how you get paid. It simply ensures your work isn’t exploited. When everything’s fine, it stays invisible. When things slip, it steps in — firm, reversible, and fair.

“We didn’t want vengeance. We wanted dignity. DevPayr protects your craft without punishing your clients — it just asks them to keep their word.”

Traditional job platforms

Take a cut; protection varies; you lose control of the relationship.
Disputes can be slow, opaque, and stressful.

Open-source “didn’t pay” hacks

Often rigid, invasive, or destructive; hard to adapt per project.
Can harm relationships and your brand if misapplied.

DevPayr

Payment-rail agnostic — you choose how you get paid (transfer, cards, wallets, crypto, etc.).
Invisible when healthy; ethical, reversible guardrails when overdue.
Multi-language SDKs + clean API for custom ops — fits how you already ship.

Join the Waitlist

Built by people who’ve been there.

Frequently Asked Questions

Everything you need to know about DevPayr — from integration to ethics.

DevPayr is an ethical payment enforcement layer you add to your projects. It stays invisible while clients pay, but enforces agreed behavior (modal, redirect, log, silent) when invoices are overdue.

No. DevPayr never touches your money. You choose how you bill (bank transfer, PayPal, Stripe, Flutterwave, crypto, etc.). DevPayr only enforces access if payments fall behind.

Freelancers, designers, developers, agencies, and product teams who deliver digital work and want peace of mind that clients respect their invoices.

Most integrations take less than 5 minutes. Install via npm, Composer, or pip, then call `DevPayr.bootstrap()`. We provide SDKs in Node.js, PHP, and Python, plus an API for custom operations.

No. DevPayr runs silently until enforcement is required. Healthy projects behave normally, with no hints that DevPayr exists.

Access is restored instantly. No redeploys, no manual intervention. The moment you mark an invoice paid, DevPayr updates in real time.

Yes. You can pick from different behaviors: show a modal, redirect to your billing page, disable silently, or log events. You remain in full control.

Never. DevPayr is payment-rail agnostic. Use Stripe, PayPal, Flutterwave, crypto wallets, or even direct bank transfers — it doesn’t matter.

No. DevPayr is intentionally non-destructive. It pauses or limits usage but never deletes, corrupts, or damages your client’s work.

Those scripts are rigid and invasive. DevPayr is multi-language, API-driven, reversible, and built to protect your reputation while still securing your work.

It requires a connection to validate license or API keys. If the client is offline, DevPayr follows your configured fallback behavior.

Yes. All API calls are encrypted via HTTPS. Sensitive data is never logged. You can self-host if compliance requires.

Currently Node.js, PHP, and Python SDKs are available. More SDKs (Go, .NET, Ruby) are planned. A universal REST API is also available.

Yes. Whether you’re licensing SaaS seats, shipping custom client apps, or delivering agency projects, DevPayr adapts to your workflow.

No. DevPayr isn’t a billing gateway. You can pair it with your subscription system (Stripe, PayPal, Paddle, etc.) to enforce when invoices lapse.

Our API is highly available. If you self-host, redundancy is your responsibility. In all cases, clients default to your configured fallback.

Yes. We provide sandbox keys and a “log-only” mode for staging and testing. Nothing is enforced in those environments.

No. Checks are lightweight. They run during bootstrap and are optimized to avoid adding latency.

Final pricing will be announced at launch. During waitlist, early adopters will enjoy founder-friendly discounts.

Yes. Self-hosting is possible for enterprise teams needing full control. Our SDKs can point to your own API base URL.

You stay in control. DevPayr provides reversible behaviors. Once the client pays, normal access resumes without friction.

Yes. Our API can be hooked into CI pipelines, deployment workflows, or billing systems.

Yes. DevPayr is designed to be ethical — no destruction, no ransomware tactics. It is essentially a guardrail for fairness, not punishment.

We’re expanding SDK support, adding analytics dashboards, and integrating with more billing tools. Our vision: every creative gets paid without fear.

Still have questions?

Contact our team

Early Access

Join the DevPayr Waitlist

Be first to try ethical payment enforcement for real client work — gentle when things are good, firm when they’re not.

Non-destructive API & SDKs Payment-rail agnostic

Full name

Role

Company / Studio (optional)

I agree to receive early-access emails from DevPayr. We’ll never share your info.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.