Quickstart and manual tools
The SDK repository contains server-side integration examples. Use them with an approved credential to validate SDK initialization, read-only queries, protected create requests and query-based recovery. It does not replace the merchant order database, secret management, Webhook verification or production release process.
Versions and downloads
| Version | Status | Download entry | Description |
|---|---|---|---|
1.1.0 | Released on 2026-09-04 | SDK source tag v1.1.0 | Matches public interface version 1.0 and SDK 1.1.0; Quickstart and manual tools support payer email/phone for Payment creation. |
The published SDK source contains examples/Quickstart.java plus local Keys.java and five independent manual classes: BalanceQueryLocalTestTool, PaymentCreateLocalTestTool, PaymentQueryLocalTestTool, PayoutCreateLocalTestTool and PayoutQueryLocalTestTool. Each class maps to one final interface and can run directly from its IDE main with the shared intl-sdk-local.properties. Complete the credential setup in the Quickstart and follow the download instructions on the SDK page before running them.
Environment variables
INTL_API_BASE_URL
INTL_API_KEY
INTL_API_SECRET
INTL_COUNTRY
INTL_CURRENCYINTL_API_BASE_URL must be the approved HTTPS API domain and must not include the /intl/v1 path prefix. Use test credentials for integration testing and production credentials only after go-live approval.
Read-only checks
The Demo runs only a read-only balance request by default. Use this stage to validate the base URL, API Key, API Secret, Timestamp, Nonce and Signature handling before any create request.
Create-request testing
Create requests are disabled by default. The Demo sends create requests only after you explicitly enable writes and provide the amount, product code and merchant order number for the target environment.
INTL_ENABLE_WRITES=true
INTL_PAYMENT_AMOUNT
INTL_PAYMENT_PRODUCT_CODE
INTL_MERCHANT_ORDER_NO
INTL_PAYMENT_PAYER_EMAIL
INTL_PAYMENT_PAYER_PHONEINTL_PAYMENT_PAYER_EMAIL and INTL_PAYMENT_PAYER_PHONE are optional payer contact fields.
Generate and save merchantOrderNo before sending the create request. HTTP 200 means the API call succeeded; use the response status, query API or Webhook for the business result. HTTP 5xx, timeout, connection loss or an unverifiable response means the create result may be unknown; query with the original merchantOrderNo. If repeated queries still find no order, resend only the unchanged request with the same original merchantOrderNo; never create a new order with another number.
Boundaries
- Run the Demo only on the merchant backend or a controlled developer machine.
- Load API Secrets and Webhook Secrets only from backend environment variables or secret management.
- The Demo does not automatically retry create requests.
- Confirm platform operations approved the calling outbound IP at the gateway security group, WAF or API Gateway; Portal credentials contain no IP field.
- Enable production writes only after go-live approval and replace all sample values with approved production test data.