Telcell setup guide
Accept Telcell Wallet payments on Telcell's own invoice payment page. OneGate never sees the customer's Telcell credentials.
What you need
- Merchant integration access from Telcell for the Telcell Wallet shop gateway.
- Your Shop / Merchant ID, which Telcell issues. The protocol calls it
issuer, and it is usually your shop's email. - Your shop key, the secret that signs every request and every Telcell notification.
Connect Telcell in OneGate
- Dashboard → Payment providers → Telcell → Connect. Choose Test or Live.
- Copy the Callback URL shown for the connection and give it to Telcell. Also give them the Return URL if they ask for a redirect link.
- Enter your Shop / Merchant ID and shop key and save. The shop key is encrypted and never shown again.
- Run test payments with the Test connection. Create a Live connection only after Telcell approves your shop for production.
| OneGate URL | Telcell setting | Purpose |
|---|---|---|
/callbacks/telcell/{connection} | Callback | Invoice status changes, server to server. Only a callback with a valid checksum can change a payment. |
/returns/telcell/{connection} | return_url | The customer's browser after the Telcell page. It shows “We’re confirming your payment” and is never proof of payment. |
Test and Live
Each connection is bound to one Telcell environment and never falls back to the other. A Test connection uses https://telcellmoney.am/proto_test2/invoices, and a Live connection uses https://telcellmoney.am/invoices. In both, customers pay on https://telcellmoney.am/payments/invoice/. TEST payments are never sent to Live, and a Test connection's callback can never settle a Live payment.
How a payment works
- The customer chooses Telcell in checkout. OneGate creates a payment attempt and issues a Telcell invoice (
bill) with the amount, a Base64 description and the attempt ID as the order code (issuer_id). - Telcell returns the invoice ID, and OneGate stores it on the attempt. The customer is sent to Telcell's invoice payment page.
- Telcell posts the new invoice status to the Callback URL. OneGate verifies the checksum and matches the invoice, the order code, the amount and the currency against its own records. It then applies the status:
PAIDcompletes the payment, andREJECTEDends the attempt so the customer can choose another method. - If no callback arrives, OneGate queries the invoice status (
check_bill) and applies only a response with a valid signature.
Security
- Telcell's protocol mandates MD5 checksums keyed with the shop key. OneGate uses MD5 only for Telcell and compares checksums in constant time. An invalid checksum never changes a payment.
- Duplicate and simultaneous callbacks complete a payment once. Webhooks, billing and fiscal receipts are produced once.
- A callback for another invoice, amount or currency, or one sent to another merchant's connection, is never applied.
- The shop key, checksums and the payer's phone or email are never logged, stored or shown.
Connection status
Telcell offers no way to check credentials before real traffic. After saving, a Test connection shows Test ready and a Live connection shows Configured. Either becomes Active once OneGate receives the first callback with a valid checksum, which proves the shop key. Replacing the shop key resets that proof.
Cancelling a paid invoice
Telcell documents cancelling a paid invoice. The dashboard offers it as Cancel paid invoice on completed Telcell payments, for roles that can create refunds. It is not a OneGate refund. Telcell defines how and when money returns to the customer. The payment stays completed and is flagged for review.
Limitations
- Refunds: full or partial refunds are not available through the documented integration. Arrange them with Telcell.
- No recurring payments, Apple Pay or Google Pay through Telcell.
- AMD only, whole dram amounts. Invoices are valid for one day.
buyer for web checkout. Second, the exact construction of the status response checksum. See docs/providers/telcell.md in the repository.