Using an SDK does not transfer every payment responsibility to a client library. Server validation, order confirmation, secret key management and notification processing remain part of your application architecture. This page explains integration choices without publishing unverified package names or download commands.
Check whether a package is suitable
Before using a package, verify its official distribution source, version, supported runtime and maintenance scope. A third-party package with a name resembling the product should not be assumed trustworthy.
- Separate server and mobile or web client roles.
- Do not embed secret keys in application packages.
- Repeat payment tests after dependency updates.
What if there is no SDK?
Direct server integration can be considered where the current API specification supports it. Confirm scope, authentication methods and error behavior with the technical teams.
A client result is not enough
Reaching a success screen should not be the sole evidence used to close an order financially. Confirm the outcome through server notifications and status queries. Before a demo, you can share your language, platform and version.