Point One Percent — pop-pay
Note: This is the PyPI published documentation. For the full architecture diagrams and real UI screenshots, please visit the GitHub Repository.
it only takes 0.1% of Hallucination to drain 100% of your wallet.
The runtime security layer for AI agent commerce. Drop-in CLI + MCP server. Card credentials are injected directly into the browser DOM via CDP — they never enter the agent's context window. One hallucinated prompt can't drain a wallet it can't see.
Install
Choose your preferred method:
pipx — isolated global CLI
pipx install "pop-pay[mcp]"
pip
pip install "pop-pay[mcp]"
uv (isolated tool install)
uv tool install "pop-pay[mcp]"
Extras matrix — feature flags
pip install "pop-pay" # core (keyword guardrail + mock provider)
pip install "pop-pay[mcp,browser]" # CDP injection (browser automation)
pip install "pop-pay[mcp,llm]" # LLM guardrails (OpenAI, Ollama, vLLM, OpenRouter)
pip install "pop-pay[stripe]" # Stripe virtual card issuing
pip install "pop-pay[langchain]" # LangChain integration
pip install "pop-pay[all]" # everything
All install paths expose the CLI binaries: pop-launch, pop-init-vault, pop-unlock, and pop-pay (dashboard launcher).
Using Node.js / JavaScript? Check out pop-pay (npm) —
npm i -g pop-payorbrew install 100xpercent/tap/pop-pay. Same security model, same vault format, independent release cycle — safe to switch between runtimes.
Quick Start (CLI)
1. Initialize the encrypted credential vault
pop-init-vault
This encrypts your card credentials into ~/.config/pop-pay/vault.enc (AES-256-GCM). For stronger protection (blocks agents with shell access):
pop-init-vault --passphrase # one-time setup
pop-unlock # run once per session
2. Launch Chrome with CDP remote debugging
pop-launch
Opens a Chromium instance on http://localhost:9222 that pop-pay injects credentials into. Your agent (via MCP, browser automation, or x402) then drives the checkout flow — card details never leave the browser process.
3. Open the monitoring dashboard (optional)
pop-pay
Real-time view of agent payment activity, budget utilization, and rejection logs.
4. Plug into your agent
Two supported integration paths:
- MCP server — add pop-pay to any MCP-compatible client (Claude Code, OpenClaw). See MCP Server below.
- Python SDK / LangChain — see Python SDK below.
MCP Server (optional)
The MCP server is invoked as a Python module and decrypts the vault at startup.
Add to your MCP client
{
"mcpServers": {
"pop-pay": {
"command": "python3",
"args": ["-m", "pop_pay.mcp_server"],
"env": {
"POP_CDP_URL": "http://localhost:9222"
}
}
}
}
Claude Code
claude mcp add pop-pay -- python3 -m pop_pay.mcp_server
With environment variables:
claude mcp add pop-pay \
-e POP_CDP_URL=http://localhost:9222 \
-e POP_ALLOWED_CATEGORIES='["aws","cloudflare"]' \
-e POP_MAX_PER_TX=100.0 \
-e POP_MAX_DAILY=500.0 \
-e POP_GUARDRAIL_ENGINE=keyword \
-- python3 -m pop_pay.mcp_server
OpenClaw / NemoClaw
Compatible with any MCP host. See the Integration Guide for setup instructions and System Prompt templates.
Docker
docker-compose up -d
Runs the MCP server + headless Chromium with CDP. Mount your encrypted vault from the host. See docker-compose.yml for configuration.
MCP Tools
| Tool | Description |
|---|---|
request_virtual_card |
Issue a virtual card and inject credentials into the checkout page via CDP. |
request_purchaser_info |
Auto-fill billing/contact info (name, address, email, phone). |
request_x402_payment |
Pay for API calls via the x402 HTTP payment protocol. |
page_snapshot |
Scan a checkout page for hidden prompt injections or anomalies. |
Configuration
Core variables in ~/.config/pop-pay/.env. See ENV_REFERENCE.md for the full list.
| Variable | Default | Description |
|---|---|---|
POP_ALLOWED_CATEGORIES |
["aws","cloudflare"] |
Approved vendor categories — see Categories Cookbook |
POP_MAX_PER_TX |
100.0 |
Max USD per transaction |
POP_MAX_DAILY |
500.0 |
Max USD per day |
POP_BLOCK_LOOPS |
true |
Block hallucination/retry loops |
POP_AUTO_INJECT |
true |
Enable CDP card injection |
POP_GUARDRAIL_ENGINE |
keyword |
keyword (zero-cost) or llm (semantic) |
Guardrail Mode
keyword (default) |
llm |
|
|---|---|---|
| Mechanism | Keyword matching on reasoning string | Semantic analysis via LLM |
| Cost | Zero — no API calls | One LLM call per request |
| Best for | Development, low-risk workflows | Production, high-value transactions |
To enable LLM mode, see Integration Guide §1.
Providers
| Provider | Description |
|---|---|
| BYOC (default) | Bring Your Own Card — encrypted vault credentials, local CDP injection. |
| Stripe Issuing | Real virtual cards via Stripe API. Requires POP_STRIPE_KEY. |
| Lithic | Multi-issuer adapter (Stripe Issuing / Lithic). |
| Mock | Test mode with generated card numbers for development. |
Priority: Stripe Issuing → BYOC Local → Mock.
Python SDK
Integrate pop-pay into custom Python or LangChain workflows:
from pop_pay.client import PopClient
from pop_pay.providers.stripe_mock import MockStripeProvider
from pop_pay.core.models import GuardrailPolicy
client = PopClient(
provider=MockStripeProvider(),
policy=GuardrailPolicy(
allowed_categories=["API", "Cloud"],
max_amount_per_tx=50.0,
max_daily_budget=200.0,
),
)
# LangChain integration
from pop_pay.tools.langchain import PopPaymentTool
tool = PopPaymentTool(client=client, agent_id="agent-01")
See Integration Guide §2 for the full SDK and provider reference.
Security
| Layer | Defense |
|---|---|
| Context Isolation | Card credentials never enter the agent's context window or logs |
| Encrypted Vault | AES-256-GCM with PBKDF2 key derivation and OS keyring integration |
| TOCTOU Guard | Domain verified at the moment of CDP injection — blocks redirect attacks |
| Repr Redaction | Automatic masking (****-4242) in all MCP responses, logs, and tracebacks |
See THREAT_MODEL.md for the full STRIDE analysis and COMPLIANCE_FAQ.md for enterprise details.
Architecture
- Python — Core engine, MCP server, guardrail logic, CLI
- Cython — Performance-critical vault operations and memory protection
- Chrome DevTools Protocol — Direct DOM injection via raw WebSocket
- SQLite — Local transaction auditing and state management
Documentation
- Threat Model — STRIDE analysis, 5 security primitives, 10 attack scenarios
- Guardrail Benchmark — Cross-model evaluation (Anthropic / OpenAI / Gemini) across 585 payloads, 11 attack categories
- Compliance FAQ — PCI DSS, SOC 2, GDPR details
- Environment Reference — All POP_* environment variables
- Integration Guide — Setup for Claude Code, Python SDK, and browser agents
- Categories Cookbook — POP_ALLOWED_CATEGORIES patterns and examples
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for pop-pay 0.8.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 5.7 MB
Release files / pop_pay-0.8.9-cp313-cp313-win_amd64.whl
| Download URL | pop_pay-0.8.9-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 284.3 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
1af5a31c6e44e2d8761f322d314f509a369622398b0f9e7e91d3e52c72002fb1
|
|
BLAKE2b-256 checksum How to use checksums |
2d4e46f5b7ff9c7872703fe85e33e51523a5b8441b050172b6b837f36f2482b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp313-cp313-win32.whl
| Download URL | pop_pay-0.8.9-cp313-cp313-win32.whl |
|---|---|
| Size | 257.3 kB |
| Tags | CPython 3.13 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
86e4d9e632b5337538abf46bfcc9443bcea23075530fb4243461d4e4c948ed44
|
|
BLAKE2b-256 checksum How to use checksums |
8fd27bfe9b7b1b5b743233f5c2bffde7c70228227d8a148eb4bc2a3ddc88d4e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pop_pay-0.8.9-cp313-cp313-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 689.1 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
31f09419b953bc783c44fb3c5d5eaca5a17fb7a775ffa787383233c1babaad78
|
|
BLAKE2b-256 checksum How to use checksums |
803ec3bb6c91652a79c662821eb6aa12a7fc6cfcced79ad93d3a510096173f72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | pop_pay-0.8.9-cp313-cp313-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 661.0 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
6259267981359751e4fe90270631fa6fa529fa9f6fe9c018bb5e55e61298c256
|
|
BLAKE2b-256 checksum How to use checksums |
42ffb611e1b97225027354e031f8c3975bfef419df38d471351213bc3fc67535
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pop_pay-0.8.9-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 187.9 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7aa16e14f167741e2a1a6f829769e1ffb58ab72dbeb028cdf057ac20c812cf20
|
|
BLAKE2b-256 checksum How to use checksums |
d55daaa65c5f44b7be2b21578cb54899421dadfc2b4f75d983228928e5a98a1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp312-cp312-win_amd64.whl
| Download URL | pop_pay-0.8.9-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 233.6 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
33d041a0de293be611c3a5ae54ab5d8b49f1cfb2516ffddcaf67671b48b354fe
|
|
BLAKE2b-256 checksum How to use checksums |
e0204462e087f37c8c2a861dd7e0b2885fa566eb92d4cc3bd73ae946137cbc14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp312-cp312-win32.whl
| Download URL | pop_pay-0.8.9-cp312-cp312-win32.whl |
|---|---|
| Size | 206.1 kB |
| Tags | CPython 3.12 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
dde3e569961b69d00f139da0eae99062499b4c88f3ef84bda9d71496c2ab5da3
|
|
BLAKE2b-256 checksum How to use checksums |
3db60f8f9bf7eeff0285fd935e2ed931e030cf64b67889d644e25439fe5d0a6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pop_pay-0.8.9-cp312-cp312-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 533.7 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
ece5353b6fdf3619db4e9d745baa45640318916e7d68457ee1ecb8b148067089
|
|
BLAKE2b-256 checksum How to use checksums |
b5fe4793c943938189cede5123ec066c4e40df0d65f11376c14583cd996ff918
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | pop_pay-0.8.9-cp312-cp312-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 512.9 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
8109129e47b4ea241a457570608a6475f72dd6abde7313f227ea8e985a37aefe
|
|
BLAKE2b-256 checksum How to use checksums |
8c9697506d5b21332ffe90b9726c9cf49689535904a30f3d862198541a43d815
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pop_pay-0.8.9-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 161.3 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8faf60b0598f8365937df7da8e3e6ca4042bede5a3e5ddccd5e11c1acbea4d29
|
|
BLAKE2b-256 checksum How to use checksums |
75a5431730809323b1cc5f6e9f214988449bb5231bd48b12bf5cc8e076424bbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp311-cp311-win_amd64.whl
| Download URL | pop_pay-0.8.9-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 182.1 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
291c10a85ed3340e3b8cdc9d762157193b232fd2f188c88cadcbe0fe62a8da4f
|
|
BLAKE2b-256 checksum How to use checksums |
86a3cfd80ebbb4d1d2635ad41ca6319fad26d95dfaf7cfa00076a32ca2c6c501
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp311-cp311-win32.whl
| Download URL | pop_pay-0.8.9-cp311-cp311-win32.whl |
|---|---|
| Size | 154.7 kB |
| Tags | CPython 3.11 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
9ea3c0e309028f48fe66e47d7d4cf6637e356c58bcfd1f13e4dfd3a99f92b5ba
|
|
BLAKE2b-256 checksum How to use checksums |
6a1dbe9ff9d96bb12e358003fcda902b4713bf23988dc4c9cc9478b56650acfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pop_pay-0.8.9-cp311-cp311-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 372.2 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
af73adba34928cfd4984959caa352a44475d15eea21ad362f79a1689e5e2ae94
|
|
BLAKE2b-256 checksum How to use checksums |
eca6ec6d9708b1fce378ec5eca0a0322c55b19db807f7b51ea53ec8be55adc44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | pop_pay-0.8.9-cp311-cp311-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 359.3 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
63484956f43fc2618e2c8b429ee510c1e790fcf8d7398e925a80bec1d355557b
|
|
BLAKE2b-256 checksum How to use checksums |
01d8353f929e656ac55132cc3cfe9f85aca6888c0d90ea1beb92baf7fad479bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pop_pay-0.8.9-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 134.3 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f5da00c25a50bd3e81eed7887e775be8a0f5f21f3707a8e87d004f9710edcfec
|
|
BLAKE2b-256 checksum How to use checksums |
e3150c1b0237db51bac6395235ab5cf961a3e69239ac762ee4f6182292f58797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp310-cp310-win_amd64.whl
| Download URL | pop_pay-0.8.9-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 130.8 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
cb32a2b1f873639b4dd339514c77d9d72bf67d06bccd6f64f55602287c463d4e
|
|
BLAKE2b-256 checksum How to use checksums |
d25210339f8a1fc92d94e566e5e0dabee901a2cf8270c1c36f6d7a4c3f247d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp310-cp310-win32.whl
| Download URL | pop_pay-0.8.9-cp310-cp310-win32.whl |
|---|---|
| Size | 103.4 kB |
| Tags | CPython 3.10 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
bf50eb51e4e4354fdedd595382eff734aa8d02fc9b79d9d69d2766afaac79f77
|
|
BLAKE2b-256 checksum How to use checksums |
5facb40e1f19814aa6a08822786593d43b7d470c53bf9ca99036b3d91d551d60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pop_pay-0.8.9-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 222.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
c938d778a9a5ac8c4194c48ece5c742684dad634d75898cfb2d7ef6d7f619672
|
|
BLAKE2b-256 checksum How to use checksums |
159f4c86e27063a9b4c4faa0b5829e8f95e7a1299a42dfe3f13b5ad937c456a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl
| Download URL | pop_pay-0.8.9-cp310-cp310-manylinux_2_5_i686.manylinux1_i686.manylinux_2_17_i686.manylinux2014_i686.whl |
|---|---|
| Size | 215.7 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-32 Linux glibc 2.5+ x86-32 |
|
SHA-256 checksum How to use checksums |
ce82135b38b11dd96760713646579ddc5143bfd172564aecbac4ea60f45df3ca
|
|
BLAKE2b-256 checksum How to use checksums |
9893a5ba2891628fa42eab4b5210091c9196d13a516549c6cb03b1d810380bc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logRelease files / pop_pay-0.8.9-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | pop_pay-0.8.9-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 107.2 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4fabef38490c24e4427cbbdec921700379108e4add87a1bb3e3b7ff6515cbb16
|
|
BLAKE2b-256 checksum How to use checksums |
57e2e3497b8be8c5e624c333371908bf735b302265f8eae8de7a37b42418c28e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logSecurity for pop-pay 0.8.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 20 files in this release have been uploaded with provenance metadata.
Attestation for pop_pay-0.8.9-cp313-cp313-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
