Every SDK shipped an install command that fails. A developer following the
README hits an error on the first step.
- go: `go get github.com/qbirr/sdk-go` pointed at GitHub. The module lives at
git.qbirr.com/admin/sdk-go (see go.mod), so that command could never work.
- node / python / php: the commands assumed a published package, but nothing is
on npm, PyPI or Packagist yet (all four return 404).
The commands are now the ones that were actually run and verified:
go go get git.qbirr.com/admin/sdk-go
node npm install git+https://git.qbirr.com/admin/sdk-node.git
python pip install "git+https://git.qbirr.com/admin/sdk-python.git"
php composer config repositories.qbirr vcs <repo>
composer require qbirr/sdk:dev-main
A note under each explains that the package is not on the public registry yet,
so the install comes straight from the repository.
The repositories stay public, so no credentials are needed for any of the above.
If they were made private, the Go install would break first: Go fetches modules
directly from the git host.
- The example account number in the README and in the source docblock was a
REAL account number. Replaced with an obviously fake one (1000123456789).
The same scrub had already been applied to sdks/ in qbirr-saas; this repo
had drifted from it.
- Document that CBE accepts the full receipt link, the "v2-" token and the bare
token as the SAME payment. qbirr reduces them to one identity, so a receipt
cannot be verified twice by presenting it differently. Case is ignored for
that check.
- Document the webhook contract: `verification.created` fires for BOTH outcomes
so always read data.verified; data.client_ref echoes the tag your own upload
sent (null if you did not send one); a 4xx response is final and is NOT
retried, while 5xx / timeouts are retried with exponential backoff.
- Document that only verified lookups count against the monthly quota.
- sdk-node: the committed dist/ comment blocks were updated to match src. The
change is inside comments only — no executable code differs.
The API returns five fields the SDKs were dropping, so a caller could not
act on any of them:
retryable TRUE means we could not reach the bank. In that case
verified=false is NOT a verdict on the payment -- it is
"not checked yet". Retry, or fall back to manual review.
Never reject an order on it. Check it BEFORE acting on
verified=false.
code Stable machine-readable reason; branch on this instead of
parsing the human-readable error string. Empty/null on
success. RECEIPT_NOT_FOUND, AMOUNT_MISMATCH,
RECEIVER_MISMATCH, RECEIPT_EXPIRED, RECEIPT_UNREADABLE,
REFERENCE_INVALID, RECEIVER_ACCOUNT_REQUIRED,
UNSUPPORTED_INPUT, VERIFICATION_FAILED,
DUPLICATE_REFERENCE, UPSTREAM_UNAVAILABLE (retryable).
paid_amount What the receipt ACTUALLY shows, so a short payment can be
compared to the expected figure rather than only described
in prose.
receiver_source Which receiver identity was actually checked: 'settings'
(your saved dashboard account -- strongest), 'request' (the
receiver_name/account you sent), or 'none' (NOTHING was
checked: verified=true with 'none' means the reference
exists and the amount matches, but says nothing about who
received the money).
sandbox True only on TEST-... responses.
Additive only. Defaults are filled in on the way out so a caller never sees a
missing value, including against an API build that predates these fields.