Verify Package Signature

The SuprSend Java SDK is signed and checksummed starting from release v0.13.2. Before installing, you can cryptographically confirm that the artifact you are using was built by SuprSend and has not been modified in transit.

Before you begin

The SuprSend Java SDK ships with two independent trust signals:

Maven Central GPG signature — every artifact published to Maven Central is signed with SuprSend’s GPG key. Maven Central requires all publishers to sign their artifacts, and the .asc signature file is published alongside every .jar on the Maven Central file server at repo1.maven.org.
SHA-256 checksum + GPG signature on checksums.txt — every GitHub release also publishes a checksums.txt listing SHA-256 hashes of all release artifacts, signed with the same GPG key. This mirrors the flow used for the Python SDK and CLI.

Verification below covers both paths. Pick the one that matches where you are consuming the artifact from — Maven Central or GitHub release.

Prerequisites

You need GPG installed.

macOS
Linux (Debian / Ubuntu)
Windows

brew install gnupg

sudo apt-get install -y gnupg

Confirm it is working:

gpg --version

Path A — Verify a jar from Maven Central

Use this path if your build tool (Maven/Gradle) resolved the dependency from Maven Central, or if you want to verify a .jar downloaded directly from repo1.maven.org.

Step A1 — Create a working directory

macOS / Linux
Windows

mkdir suprsend-verify && cd suprsend-verify

New-Item -ItemType Directory -Name suprsend-verify
Set-Location suprsend-verify

Step A2 — Download the jar, its signature, and its checksum from Maven Central

Use curl to download directly from the Maven Central file server. Do not download through the Sonatype UI — it does not serve .asc files correctly.

macOS / Linux
Windows

VERSION="0.13.2"
BASE="https://repo1.maven.org/maven2/com/suprsend/suprsend-java-sdk/${VERSION}"

curl -sL -O "${BASE}/suprsend-java-sdk-${VERSION}.jar"
curl -sL -O "${BASE}/suprsend-java-sdk-${VERSION}.jar.asc"
curl -sL -O "${BASE}/suprsend-java-sdk-${VERSION}.jar.sha256"

$VERSION = "0.13.2"
$BASE    = "https://repo1.maven.org/maven2/com/suprsend/suprsend-java-sdk/$VERSION"

Invoke-WebRequest "$BASE/suprsend-java-sdk-$VERSION.jar"        -OutFile "suprsend-java-sdk-$VERSION.jar"
Invoke-WebRequest "$BASE/suprsend-java-sdk-$VERSION.jar.asc"    -OutFile "suprsend-java-sdk-$VERSION.jar.asc"
Invoke-WebRequest "$BASE/suprsend-java-sdk-$VERSION.jar.sha256" -OutFile "suprsend-java-sdk-$VERSION.jar.sha256"

Step A3 — Verify the jar checksum against Maven Central

Maven Central publishes its own SHA-256 hash for every artifact independently of SuprSend. Verifying against it confirms the file you downloaded matches what Maven Central is serving — using Maven Central’s infrastructure as the source of truth.

macOS
Linux
Windows

echo "$(cat suprsend-java-sdk-0.13.2.jar.sha256)  suprsend-java-sdk-0.13.2.jar" | shasum -a 256 --check

Expected output:

suprsend-java-sdk-0.13.2.jar: OK

echo "$(cat suprsend-java-sdk-0.13.2.jar.sha256)  suprsend-java-sdk-0.13.2.jar" | sha256sum --check

Expected output:

suprsend-java-sdk-0.13.2.jar: OK

$filename = "suprsend-java-sdk-0.13.2.jar"
$expected = (Get-Content "suprsend-java-sdk-0.13.2.jar.sha256").Trim().ToLower()
$actual   = (Get-FileHash ".\$filename" -Algorithm SHA256).Hash.ToLower()

if ($expected -eq $actual) {
  Write-Host "Checksum OK — $filename"
} else {
  Write-Error "CHECKSUM MISMATCH — do not use this artifact"
}

Expected output:

Checksum OK — suprsend-java-sdk-0.13.2.jar

Step A4 — Import and trust SuprSend’s public key

Download the public key from the SuprSend GitHub release, import it, and mark it as trusted. The second command sets trust non-interactively so the final verify output is clean with no warnings.

curl -sL -O https://github.com/suprsend/suprsend-java-sdk/releases/download/v0.13.2/public_key.asc
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

Expected output:

gpg: key 5261B38640D3A94D: public key "SuprSend (Maven Signing Key) <nikhilesh@suprsend.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: inserting ownertrust of 6

Always download public_key.asc directly from the official SuprSend Java SDK releases page. Do not copy it from mirrors or third-party sources. Before trusting the key, cross-check the fingerprint 2E736EA7E36AB94C883A490C5261B38640D3A94D against the one published on the releases page.

Step A5 — Verify the GPG signature on the jar

gpg --verify suprsend-java-sdk-0.13.2.jar.asc suprsend-java-sdk-0.13.2.jar

Expected output:

gpg: Signature made Fri Mar 27 09:14:21 2026 UTC
gpg:                using RSA key 2E736EA7E36AB94C883A490C5261B38640D3A94D
gpg: Good signature from "SuprSend (Maven Signing Key) <nikhilesh@suprsend.com>" [full]

Good signature [full] confirms the .jar was signed by SuprSend’s private key and has not been modified since signing.

If you see BAD signature, do not use this artifact. Re-download both the .jar and .jar.asc using the curl commands in Step A2 and retry. If the failure persists, contact SuprSend support.

Path B — Verify a jar downloaded from GitHub releases

Use this path if you downloaded the .jar from the GitHub releases page and want to verify it against the signed checksums.txt.

Step B1 — Create a working directory

All files must be in the same directory for the checksum step to work.

macOS / Linux
Windows

mkdir suprsend-verify && cd suprsend-verify

New-Item -ItemType Directory -Name suprsend-verify
Set-Location suprsend-verify

Step B2 — Download the jar and verification files

macOS / Linux
Windows

VERSION="0.13.2"
BASE="https://github.com/suprsend/suprsend-java-sdk/releases/download/v${VERSION}"

curl -sL -O "${BASE}/suprsend-java-sdk-${VERSION}.jar"
curl -sL -O "${BASE}/checksums.txt"
curl -sL -O "${BASE}/checksums.txt.asc"
curl -sL -O "${BASE}/public_key.asc"

$VERSION = "0.13.2"
$BASE    = "https://github.com/suprsend/suprsend-java-sdk/releases/download/v$VERSION"

Invoke-WebRequest "$BASE/suprsend-java-sdk-$VERSION.jar" -OutFile "suprsend-java-sdk-$VERSION.jar"
Invoke-WebRequest "$BASE/checksums.txt"                  -OutFile checksums.txt
Invoke-WebRequest "$BASE/checksums.txt.asc"              -OutFile checksums.txt.asc
Invoke-WebRequest "$BASE/public_key.asc"                 -OutFile public_key.asc

At this point your suprsend-verify directory should contain exactly these files:

suprsend-verify/
├── checksums.txt
├── checksums.txt.asc
├── public_key.asc
└── suprsend-java-sdk-0.13.2.jar

File	Description
`suprsend-java-sdk-0.13.2.jar`	The SDK artifact.
`checksums.txt`	SHA-256 hashes of all release artifacts. This is what gets signed.
`checksums.txt.asc`	GPG detached signature over `checksums.txt`.
`public_key.asc`	SuprSend’s GPG public key. Used to verify the signature.

Step B3 — Import and trust SuprSend’s public key

gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

Expected output:

gpg: key 5261B38640D3A94D: public key "SuprSend (Maven Signing Key) <nikhilesh@suprsend.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: inserting ownertrust of 6

Before trusting the key, cross-check the fingerprint 2E736EA7E36AB94C883A490C5261B38640D3A94D against the one published on the SuprSend Java SDK releases page.

Step B4 — Verify the signature on checksums.txt

gpg --verify checksums.txt.asc checksums.txt

Expected output:

gpg: Signature made ...
gpg:                using RSA key 2E736EA7E36AB94C883A490C5261B38640D3A94D
gpg: Good signature from "SuprSend (Maven Signing Key) <nikhilesh@suprsend.com>" [full]

Good signature [full] confirms checksums.txt was produced by SuprSend’s pipeline and has not been tampered with.

If you see BAD signature, do not proceed. Re-download all files from the same release and retry. If the failure persists, contact SuprSend support.

Step B5 — Verify the jar checksum

macOS
Linux
Windows

grep "suprsend-java-sdk-0.13.2.jar" checksums.txt | shasum -a 256 --check

Expected output:

suprsend-java-sdk-0.13.2.jar: OK

grep "suprsend-java-sdk-0.13.2.jar" checksums.txt | sha256sum --check

Expected output:

suprsend-java-sdk-0.13.2.jar: OK

$filename = "suprsend-java-sdk-0.13.2.jar"
$line     = Get-Content checksums.txt | Where-Object { $_ -match [regex]::Escape($filename) }
$expected = ($line -split '\s+')[0].ToLower()
$actual   = (Get-FileHash ".\$filename" -Algorithm SHA256).Hash.ToLower()

if ($expected -eq $actual) {
  Write-Host "Checksum OK — $filename"
} else {
  Write-Error "CHECKSUM MISMATCH — do not use this artifact"
}

Expected output:

Checksum OK — suprsend-java-sdk-0.13.2.jar

Add the dependency to your project

Once verification passes, add the SDK to your build configuration:

Maven
Gradle

<dependency>
  <groupId>com.suprsend</groupId>
  <artifactId>suprsend-java-sdk</artifactId>
  <version>0.13.2</version>
</dependency>

implementation 'com.suprsend:suprsend-java-sdk:0.13.2'

Full scripts

Path A — Maven Central

macOS (Apple Silicon / Intel)
Linux (x86_64 / ARM64)
Windows

#!/usr/bin/env bash
set -euo pipefail

VERSION="0.13.2"
JAR="suprsend-java-sdk-${VERSION}.jar"
MAVEN_BASE="https://repo1.maven.org/maven2/com/suprsend/suprsend-java-sdk/${VERSION}"
GH_BASE="https://github.com/suprsend/suprsend-java-sdk/releases/download/v${VERSION}"

mkdir suprsend-verify && cd suprsend-verify

echo "-> Downloading jar, signature, and checksum from Maven Central..."
curl -sL -O "${MAVEN_BASE}/${JAR}"
curl -sL -O "${MAVEN_BASE}/${JAR}.asc"
curl -sL -O "${MAVEN_BASE}/${JAR}.sha256"

echo "-> Verifying jar checksum against Maven Central..."
echo "$(cat ${JAR}.sha256)  ${JAR}" | shasum -a 256 --check

echo "-> Importing and trusting public key..."
curl -sL -O "${GH_BASE}/public_key.asc"
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

echo "-> Verifying GPG signature on jar..."
gpg --verify "${JAR}.asc" "${JAR}"

echo "Done. SuprSend Java SDK ${VERSION} verified."

#!/usr/bin/env bash
set -euo pipefail

VERSION="0.13.2"
JAR="suprsend-java-sdk-${VERSION}.jar"
MAVEN_BASE="https://repo1.maven.org/maven2/com/suprsend/suprsend-java-sdk/${VERSION}"
GH_BASE="https://github.com/suprsend/suprsend-java-sdk/releases/download/v${VERSION}"

mkdir suprsend-verify && cd suprsend-verify

echo "-> Downloading jar, signature, and checksum from Maven Central..."
curl -sL -O "${MAVEN_BASE}/${JAR}"
curl -sL -O "${MAVEN_BASE}/${JAR}.asc"
curl -sL -O "${MAVEN_BASE}/${JAR}.sha256"

echo "-> Verifying jar checksum against Maven Central..."
echo "$(cat ${JAR}.sha256)  ${JAR}" | sha256sum --check

echo "-> Importing and trusting public key..."
curl -sL -O "${GH_BASE}/public_key.asc"
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

echo "-> Verifying GPG signature on jar..."
gpg --verify "${JAR}.asc" "${JAR}"

echo "Done. SuprSend Java SDK ${VERSION} verified."

$VERSION     = "0.13.2"
$JAR         = "suprsend-java-sdk-$VERSION.jar"
$MAVEN_BASE  = "https://repo1.maven.org/maven2/com/suprsend/suprsend-java-sdk/$VERSION"
$GH_BASE     = "https://github.com/suprsend/suprsend-java-sdk/releases/download/v$VERSION"

New-Item -ItemType Directory -Name suprsend-verify
Set-Location suprsend-verify

Write-Host "-> Downloading jar, signature, and checksum from Maven Central..."
Invoke-WebRequest "$MAVEN_BASE/$JAR"        -OutFile $JAR
Invoke-WebRequest "$MAVEN_BASE/$JAR.asc"    -OutFile "$JAR.asc"
Invoke-WebRequest "$MAVEN_BASE/$JAR.sha256" -OutFile "$JAR.sha256"

Write-Host "-> Verifying jar checksum against Maven Central..."
$expected = (Get-Content "$JAR.sha256").Trim().ToLower()
$actual   = (Get-FileHash ".\$JAR" -Algorithm SHA256).Hash.ToLower()
if ($expected -eq $actual) { Write-Host "Checksum OK — $JAR" } else { Write-Error "CHECKSUM MISMATCH — do not use this artifact"; exit 1 }

Write-Host "-> Importing and trusting public key..."
Invoke-WebRequest "$GH_BASE/public_key.asc" -OutFile public_key.asc
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

Write-Host "-> Verifying GPG signature on jar..."
gpg --verify "$JAR.asc" $JAR

Write-Host "Done. SuprSend Java SDK $VERSION verified."

Path B — GitHub release

macOS (Apple Silicon / Intel)
Linux (x86_64 / ARM64)
Windows (x86_64 / ARM64)

#!/usr/bin/env bash
set -euo pipefail

VERSION="0.13.2"
JAR="suprsend-java-sdk-${VERSION}.jar"
BASE="https://github.com/suprsend/suprsend-java-sdk/releases/download/v${VERSION}"

mkdir suprsend-verify && cd suprsend-verify

echo "-> Downloading jar and verification files..."
curl -sL -O "${BASE}/${JAR}"
curl -sL -O "${BASE}/checksums.txt"
curl -sL -O "${BASE}/checksums.txt.asc"
curl -sL -O "${BASE}/public_key.asc"

echo "-> Importing and trusting public key..."
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

echo "-> Verifying signature on checksums.txt..."
gpg --verify checksums.txt.asc checksums.txt

echo "-> Verifying jar checksum..."
grep "${JAR}" checksums.txt | shasum -a 256 --check

echo "Done. SuprSend Java SDK ${VERSION} verified."

#!/usr/bin/env bash
set -euo pipefail

VERSION="0.13.2"
JAR="suprsend-java-sdk-${VERSION}.jar"
BASE="https://github.com/suprsend/suprsend-java-sdk/releases/download/v${VERSION}"

mkdir suprsend-verify && cd suprsend-verify

echo "-> Downloading jar and verification files..."
curl -sL -O "${BASE}/${JAR}"
curl -sL -O "${BASE}/checksums.txt"
curl -sL -O "${BASE}/checksums.txt.asc"
curl -sL -O "${BASE}/public_key.asc"

echo "-> Importing and trusting public key..."
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

echo "-> Verifying signature on checksums.txt..."
gpg --verify checksums.txt.asc checksums.txt

echo "-> Verifying jar checksum..."
grep "${JAR}" checksums.txt | sha256sum --check

echo "Done. SuprSend Java SDK ${VERSION} verified."

$VERSION  = "0.13.2"
$JAR      = "suprsend-java-sdk-$VERSION.jar"
$BASE     = "https://github.com/suprsend/suprsend-java-sdk/releases/download/v$VERSION"

New-Item -ItemType Directory -Name suprsend-verify
Set-Location suprsend-verify

Write-Host "-> Downloading jar and verification files..."
Invoke-WebRequest "$BASE/$JAR"              -OutFile $JAR
Invoke-WebRequest "$BASE/checksums.txt"     -OutFile checksums.txt
Invoke-WebRequest "$BASE/checksums.txt.asc" -OutFile checksums.txt.asc
Invoke-WebRequest "$BASE/public_key.asc"    -OutFile public_key.asc

Write-Host "-> Importing and trusting public key..."
gpg --import public_key.asc
echo "2E736EA7E36AB94C883A490C5261B38640D3A94D:6:" | gpg --import-ownertrust

Write-Host "-> Verifying signature on checksums.txt..."
gpg --verify checksums.txt.asc checksums.txt

Write-Host "-> Verifying jar checksum..."
$line     = Get-Content checksums.txt | Where-Object { $_ -match [regex]::Escape($JAR) }
$expected = ($line -split '\s+')[0].ToLower()
$actual   = (Get-FileHash ".\$JAR" -Algorithm SHA256).Hash.ToLower()
if ($expected -eq $actual) { Write-Host "Checksum OK — $JAR" } else { Write-Error "CHECKSUM MISMATCH — do not use this artifact" }

Write-Host "Done. SuprSend Java SDK $VERSION verified."

Add the dependency to your project

Once verification passes, add the SDK to your build configuration:

Maven
Gradle

<dependency>
  <groupId>com.suprsend</groupId>
  <artifactId>suprsend-java-sdk</artifactId>
  <version>0.13.2</version>
</dependency>

implementation 'com.suprsend:suprsend-java-sdk:0.13.2'

Reference

Available release artifacts

Artifact	Source	Description
`suprsend-java-sdk-{version}.jar`	GitHub / Maven Central	The SDK jar.
`suprsend-java-sdk-{version}.jar.asc`	Maven Central	GPG detached signature over the jar.
`suprsend-java-sdk-{version}.jar.sha256`	Maven Central	SHA-256 hash of the jar, published by Maven Central.
`checksums.txt`	GitHub	SHA-256 hashes of all release artifacts.
`checksums.txt.asc`	GitHub	GPG detached signature over `checksums.txt`.
`public_key.asc`	GitHub	SuprSend’s GPG public key.

Security model

SuprSend’s GPG signing private key is held exclusively by the automated release pipeline and never leaves the secure signing environment. public_key.asc is the public counterpart — it is published openly with every release and carries no risk of compromise.The key fingerprint is 2E73 6EA7 E36A B94C 883A 490C 5261 B386 40D3 A94D. You can cross-check this against the fingerprint published on the SuprSend Java SDK releases page to independently confirm the key’s authenticity before trusting it.Maven Central independently requires all publishers to sign their artifacts with a GPG key registered with a public keyserver, and publishes its own SHA-256 hash for every artifact. Path A therefore gives you three independent signals: Maven Central’s own checksum, SuprSend’s GPG signature on the jar, and the key fingerprint you can verify out-of-band.

If you encounter an unexpected verification failure, reach out at support@suprsend.com or open an issue on the SuprSend Java SDK GitHub repository.

Developer Resources

Updates and Versioning

Authentication

Security

SDKs and APIs

Features

Testing

Monitoring and Logging

Before you begin

Prerequisites

Path A — Verify a jar from Maven Central

Step A1 — Create a working directory

Step A2 — Download the jar, its signature, and its checksum from Maven Central

Step A3 — Verify the jar checksum against Maven Central

Step A4 — Import and trust SuprSend’s public key

Step A5 — Verify the GPG signature on the jar

Path B — Verify a jar downloaded from GitHub releases

Step B1 — Create a working directory

Step B2 — Download the jar and verification files

Step B3 — Import and trust SuprSend’s public key

Step B4 — Verify the signature on checksums.txt

Step B5 — Verify the jar checksum

Add the dependency to your project

Full scripts

Path A — Maven Central

Path B — GitHub release

Add the dependency to your project

Reference

Developer Resources

Updates and Versioning

Authentication

Security

SDKs and APIs

Features

Testing

Monitoring and Logging

Documentation Index

​Before you begin

​Prerequisites

​Path A — Verify a jar from Maven Central

​Step A1 — Create a working directory

​Step A2 — Download the jar, its signature, and its checksum from Maven Central

​Step A3 — Verify the jar checksum against Maven Central

​Step A4 — Import and trust SuprSend’s public key

​Step A5 — Verify the GPG signature on the jar

​Path B — Verify a jar downloaded from GitHub releases

​Step B1 — Create a working directory

​Step B2 — Download the jar and verification files

​Step B3 — Import and trust SuprSend’s public key

​Step B4 — Verify the signature on checksums.txt

​Step B5 — Verify the jar checksum

​Add the dependency to your project

​Full scripts

​Path A — Maven Central

​Path B — GitHub release

​Add the dependency to your project

​Reference

Before you begin

Prerequisites

Path A — Verify a jar from Maven Central

Step A1 — Create a working directory

Step A2 — Download the jar, its signature, and its checksum from Maven Central

Step A3 — Verify the jar checksum against Maven Central

Step A4 — Import and trust SuprSend’s public key

Step A5 — Verify the GPG signature on the jar

Path B — Verify a jar downloaded from GitHub releases

Step B1 — Create a working directory

Step B2 — Download the jar and verification files

Step B3 — Import and trust SuprSend’s public key

Step B4 — Verify the signature on checksums.txt

Step B5 — Verify the jar checksum

Add the dependency to your project

Full scripts

Path A — Maven Central

Path B — GitHub release

Add the dependency to your project

Reference