M
MerchantLoyaltyBridge

Active Workspace

API Integrations

Phase 2 starts here: configure InCard connectors for API member lookup and voucher award, with live mode using the real InCard JSON API.

Add Integration

Use sandbox mode to validate the flow locally, or live mode to hit the real InCard API.

Connector setup rules

  • Use this form for merchant terminal settings like Merchant ID, Terminal ID, Secure Code, and PosType.
  • Leave Base URL blank to use the default live InCard endpoint.
  • `API Award` batch control now lives on the campaign via `Voucher Batch ID`.
  • Server env vars are only used as fallback when the integration record has no credentials yet.

Delivery Channel Settings

Configure tenant-level sender and provider details for SMS, WhatsApp, and email dispatch.

WhatsApp

Provider, sender, API URL, and credential for WhatsApp dispatch. Leave the URL blank to use the default DirectWAGW endpoint.

Supported placeholders: `{{customerName}}`, `{{memberName}}`, `{{campaignName}}`, `{{voucherCode}}`, `{{voucherCodes}}`, `{{claimId}}`.

SMS

Provider, sender, gateway URL, and credentials for SMS dispatch. Leave the URL blank to use the default OwnSMSGW endpoint.

Supported placeholders: `{{customerName}}`, `{{memberName}}`, `{{campaignName}}`, `{{voucherCode}}`, `{{voucherCodes}}`, `{{claimId}}`.

Email

Provider identity, sender details, and SMTP credentials for email dispatch.

Supported placeholders: `{{customerName}}`, `{{memberName}}`, `{{campaignName}}`, `{{voucherCode}}`, `{{voucherCodes}}`, `{{claimId}}`. QR images are appended automatically below the email body.

Use only when your SMTP server has a hostname or certificate mismatch. This is less secure than normal TLS verification.

Connectivity Checks

Run quick provider tests here after saving delivery settings.

Save delivery settings first, then use `Test WhatsApp`, `Test SMS`, or `Test SMTP` to validate the saved provider configuration. WhatsApp and SMS send a real test message to the number you enter here.

Phase 2 Notes

How the current connector layer behaves.

  • Campaigns can now use `API` member lookup, `API Award`, or both through a selected connector.
  • Sandbox mode works without external infrastructure and synthesizes member and voucher responses for testing.
  • Live mode defaults to `https://api.incard.my/posjson` with JSON payloads, `PosType=ECOMM`, and the Postman command set: `INLogiN`, `INScrhMember`, `INRVoucherFindNEWMulti`, and `INRVoucherAWardMulti`.
  • Successful API lookups create or refresh an API-backed member shadow record for duplicate prevention and delivery.
  • InCard voucher award now uses the campaign `Voucher Batch ID` to reserve and award fresh vouchers from the live API.

Configured Connectors

Tenant-level integration registry for Phase 2 campaigns.

INCARD

Provider: incard • Mode: live

Base URLhttps://api.incard.my/posjson
Lookup and award/members/lookup • /vouchers/award
Merchant terminal283800414900135 • 3800492400
Terminal profileOnline • ECOMM • 38004
Campaign usageC3, C2
Legacy program codeNot set

Delete blocked by active campaigns

C3 still uses this connector.

Delete will auto-unlink inactive campaigns

C2

Test succeeded

InCard login successful.

Result: connected • Last checked 2026-04-29T13:06:27.376Z

Endpointhttps://api.incard.my/posjson
Transportjson
CommandINLogiN
trxStatus9802
Status messageTerminal Login successful
API versionP.10.18.001.J
Session codee32Wc3DK2iQKiC44omoPrJtC
Session IDE3NgTddv2MdWpmCJaAZzh222
TermTypeOnline
PosTypeECOMM
Terminal IP103.13.75.71
Login time2026-04-27 00:47:41
Login attempts1
Credential sourceintegration
Connected
Edit