Closed iLGunners closed 4 years ago
For mail and sms we will use separate gateways/aliases for sending following types of messages:
Both Lipi identity and company information on receipt should be clear and bold.
Options: Existing lipi.live domain
a) URL https://lipi.live/#/receipt:k302r232r1g
b) No new domain/server config
c) Needs work to make sure the site runs on non-google browsers
d) We may be able to forward https://lipi.live/receipt:k302r232r1g
to https://lipi.live/#/receipt:k302r232r1g
Options: New domain
a) URL https://<anotheranvildomain>/receipt:k302r232r1g
b) Will take time setting up domain, server
c) Will have to recode client side if not done on existing codebase
d) Separates receipt viewing from core lipi
get-receipt
apiConsider limiting how many times receipt of a sales can be sent
Step 1. Email receipts (only anti spamming limit)
Step 2. Per sales receipt sending limitation
Step 3. Sms receipts (hard limit, burn rate calculated)
Step 3. UI display sms email sent Stap 4. Charge after limit
Abstract
This is a hybrid between POS centric and invoice centric. We slowly move towards digital receipts.
Facebook
https://developers.facebook.com/docs/messenger-platform/reference/send-api/#recipient https://developers.facebook.com/docs/messenger-platform/send-messages/ We can ask here: https://www.facebook.com/groups/fbdevelopers/
WhatsApp
https://developers.facebook.com/docs/whatsapp/getting-started/ https://developers.facebook.com/docs/whatsapp/api/messages/message-templates
Extra
https://www.facebook.com/business/partner-directory/search?platforms=whatsapp&solution_type=messaging