Integration Docs
Embed the offerwall, receive signed postbacks, credit your members β and understand every commission calculation end to end.
On this page
How it works
PubCrypto connects offer providers with your website. When your members complete offers, you earn commission in USDT and your members receive points or coins in your own system.
Quick Start
Create your App
Register, then add your website via App/Website β Add New App (Terms β App Info β Config β Submit).
Get approved
An admin reviews your app. On approval you receive an embed key and a forward secret.
Create a signed iframe
Your server requests a one-time iframe URL using the publisher API key.
Receive postbacks
When a member completes a task, we POST a signed postback to your server so you can credit them.
Money Flow: A β B
The project has two different settlement flows: Offerwall and PubCrypto Link. Their formulas are not interchangeable. The calculations below match the fields and transactions used by the current backend.
1. Offerwall
Example β $0.003 payout, 80% member share, 25,000 Coins/USD
2. PubCrypto Link
For PubCrypto Link, the Admin-configured reward is the Publisher's full USD credit. Each app sets pubcrypto_link_member_percent for a separate member reward; it does not reduce Publisher earnings.
Example β $0.010 task, 50% member share, 1,000 Coins/USD
status=1. Manual approve: starts at status=0 with no publisher credit; admin approval credits the publisher and sends status=1. Rejection sends status=2.referral_commission = Publisher Amount Γ referral_percent / 100. It is an additional credit and does not reduce publisher payout; chargebacks reverse it. PubCrypto Link does not currently generate referral commission.status=2 postback so Website B can subtract the original transaction's reward_pb.Embed the Iframe
You can embed the Offerwall in 2 ways. New apps use Signed by default; Legacy is only for websites that cannot yet integrate the server API.
Signed β more secure
RecommendedWebsite B's backend uses the publisher API key to create a member-specific iframe_url. It contains a short-lived, single-use token and never exposes the API key to the browser.
/api/publisher/embed-tokensLegacy β less secure
LegacyLegacy embeds directly with site_key + sub_id and does not use a one-time signed embed token. It is easier to integrate, but site_key and sub_id are visible in the URL.
URL Parameters
risk_held and is not credited.site_key + sub_id without a one-time signed embed token. Origin protection is weaker; the click gateway and anti-automation checks remain active.List PubCrypto Links
Call this API from your publisher server to list active PubCrypto Links for an approved app. The response includes calculated member and publisher rewards, quota usage, and cooldown state for the supplied site_key.
/api/publisher/pubcrypto-linksAuthorization: Bearer YOUR_PUBLISHER_API_KEY. The API key is a server-side secret and must never be exposed in browser JavaScript.Query parameter
link_dotask sends the member to CAPTCHA, is single-use, and expires after link_expires_in seconds. available=false means the member exhausted quota or the task is cooling down. Only Admin- and publisher-enabled tasks are returned.400 missing site_key, 401 invalid/inactive API key, 404 app not owned or approved, and 429 rate limit exceeded.What is a Postback?
Postback, also called an S2S callback, is an HTTP request sent directly from PubCrypto to your server whenever a member completes a task. It tells you which member to credit even after their browser is closed.
PubCrypto sends an HTTP POST using application/x-www-form-urlencoded to the Postback URL configured for your app. The reward_pb value already includes your Member Percent, and every postback is MD5-signed for verification.
ok. If your server errors or times out, PubCrypto retries with backoff (up to 8 attempts, exponential delay).Postback Parameters
postback_url. Always verify signature before processing any field.| Parameter | Description | Example |
|---|---|---|
subId | The member id you passed in the iframe URL. Use this to identify who to credit. | user123 |
transId | Unique transaction ID. Skip duplicates to avoid double-crediting. | XX-12345678 |
offer_name | Human-readable name of the completed offer (informational). | Airdrops Engine |
offer_type | Offer category (informational). | ptc |
reward_pb | Points/coins to credit (already multiplied by Member Percent). Add or subtract this value. | 1.25 |
reward_name | Your configured currency name (Coins, Pointsβ¦). | Coins |
payout_pb | USD value of the reward (informational). payout_pb = reward_pb / reward_value. | 0.100000 |
status | 0 = pending(record only, do not credit)1 = credit(add reward_pb)2 = chargeback(subtract reward_pb) | 0 |
clicked_at | ISO timestamp of first click (for fraud analytics). | 2026-07-14 10:23:45 |
completed_at | ISO timestamp when the offer was completed. | 2026-07-14 10:31:02 |
ip | IP address of the member at completion time. | 192.168.1.0 |
country | 2-letter country code derived from IP. | US |
signature | MD5 verification hash: md5(subId + transId + reward_pb + secretKey). Always verify before crediting. | 17b4e2a70d6efe6796dd4c5507a9f9ab |
md5( subId + transId + reward_pb + secretKey )secretKey is your app's Forward Secret β not the API key.Verify & Credit
Process each postback in 4 steps: (1) verify the MD5 signature, (2) deduplicate transId, (3) record pending or credit/charge back reward_pb, and (4) return exactly ok.
Best Practices
Deduplicate transactions
Store every processed transId and ignore repeats. Never credit the same transaction twice.
Verify every signature
Reject postbacks with an invalid MD5 signature. Never expose the Forward Secret in client-side HTML.
Return "ok"
Respond with exactly ok and HTTP 2xx. Any other response is treated as a failure and retried.
Handle pending status
Store status 0 as pending. Credit only on status 1 and subtract only on status 2.
Respond quickly
Respond within 60 seconds. For slow work, acknowledge with ok and process it in the background.
Log every postback
Store timestamps, IP, country, and all other fields for fraud analysis and reconciliation.
Β© 2026 PubCrypto. Back to Home