STRAX Reach · Messaging apps
LINE Official Account conversations in Reach
If your payment service reaches travellers or partners from East and South-East Asia, LINE is often the app they already use. Reach adds your Official Account to the same client history as every other channel.
- Signed webhooks
- Instant reply tokens
- Push for later answers
Reply tokens first, pushes when the moment has passed
LINE signs every webhook with an HMAC of the body using your channel secret. Reach checks that base64 signature before anything else and ignores the empty test call the console sends when you verify the address.
Each text message from a person in a one-to-one chat lands in their Reach conversation. Group and room chats, stickers and images are skipped so the timeline stays readable.
A LINE reply token lets you answer a message within about a minute without using your message allowance. Reach keeps the token briefly and uses it for quick answers, including those from the AI assistant, and switches to a push with a retry key for anything that takes longer.
Where it helps
Cross-border remittances
Senders abroad check whether a transfer to family in South Africa has been paid out.
Tourist card support
Visitors with a prepaid travel card ask about a declined purchase in the language app they know.
Partner settlement questions
Agents of a regional partner confirm settlement times with your operations team.
What you need
-
A LINE Official Account
With a Messaging API channel in the LINE Developers console.
-
A channel access token
A long-lived token kept in the credential vault for replies and pushes.
-
The channel secret
Used to verify the signature on every webhook call.
-
Reach Core
Keeps the LINE conversations beside the client's other channels.
Good to know
Only one-to-one text messages are filed; stickers, images and group chats are skipped. The LINE display name is not in the webhook, so new contacts start with a generic name.
Questions
What happens after the reply token expires?
The answer goes out as a push message instead, which counts towards your account's message allowance.
Can a push be sent twice by mistake?
Every push carries a retry key based on the Reach message, so LINE drops a duplicate.
Will the Official Account auto-reply clash with Reach?
Turn off auto-reply and greeting messages in the account manager if your team answers in Reach.
How do clients link their account?
They send the link code from your portal as a chat message to the Official Account.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add LINE to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Data table | 1 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the LINE channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - LINE"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
LINE is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.