Nylon PayNylon Pay

Supported Languages

SDK language availability and roadmap for Nylon Pay

Nylon Pay SDKs are open source and available in multiple programming languages. All SDKs follow the same API specification with idiomatic naming conventions for each language.

Public hub (all SDKs, docs links, website): nile-squad/nylonpay-overview.

Currently Available

TypeScript

The TypeScript SDK is the reference implementation. All other SDKs target the same API surface with language-appropriate naming.

Python

Python uses snake_case method and field names (e.g. collect_payment, phone_number).

PHP

  • Package: nile-squad/nylonpay-php (composer require nile-squad/nylonpay-php)
  • Runtime: PHP 8.1+ with ext-curl, ext-json, ext-openssl, ext-mbstring
  • Documentation: SDK Reference
  • SDK skill: SKILL.md on GitHub
  • Repository: GitHub

PHP method names and array keys match TypeScript camelCase (e.g. collectPayment, phoneNumber).

In pipeline

These SDKs are actively being built. Ask for status or early access in the WhatsApp community, or open an SDK request.

LanguageStatusExpected Release
GoIn pipelineQ3 2026
C#In pipelineQ4 2026

Planned SDKs

LanguageStatusExpected Release
RustPlannedQ4 2026
JavaPlannedQ1 2027
KotlinPlannedQ1 2027
ElixirPlannedQ2 2027

All pipeline and planned SDKs follow the same API specification. Language-idiomatic naming applies, for example collectPayment in TypeScript/PHP becomes collect_payment in Python.

Runtime Requirements

All SDKs require:

  • Server-side environment. SDKs are for backend use only. Client-side packages (browser, mobile) are not currently available.
  • HTTPS support. All communication with Nylon Pay servers occurs over HTTPS.
  • Authenticated requests. The SDK authenticates requests automatically.
  • Language runtimes: Node.js 18+ (TypeScript), Python 3.10+ (Python), PHP 8.1+ with the extensions listed above (PHP).

Integration and SDK skills

Each available SDK ships a SKILL.md for language-specific setup and code. Cross-language flows and operation choice live in the integration skill. See Example prompts.

Country, currency, and payment method coverage:

Contributing

SDKs are open source. Contributions follow the SDK specification, the single source of truth for all implementations.

Start from the public overview and CONTRIBUTING.

How to Contribute

  1. Review the SDK Specification. All implementations must conform to the defined API surface, types, behaviors, and invariants.

  2. Choose a Language. Check if an SDK already exists for your target language. If not, request it or ask on WhatsApp.

  3. Follow the Spec. Every implementation must:

    • Expose all operations defined in the specification
    • Use the exact type shapes and field names (or the documented idiomatic mapping)
    • Implement the PaymentInstance contract for async operations
    • Include request signing and response verification
    • Pass the test suite defined in the spec
  4. Submit for Review. Open a pull request in the appropriate language repository. We review for spec compliance before merging.

Getting Help

On this page