Firetip | Unified Communications Infrastructure

Overview

Firetip Payments is the payment communication layer inside Firetip. Stripe is responsible for processing the actual payment while Firetip controls the request, communication, tracking and automation lifecycle.

A payment request can be dispatched through one or multiple communication channels.

Layer	Responsibility
Stripe	Secure Checkout and payment processing.
Firetip	Payment request, dispatch, tracking and automation.
Email	Payment request delivery through Firetip Email.
SMS	Payment reminders and recovery messages.
WhatsApp	Conversational payment delivery and recovery.

Payment Architecture

The intended Firetip payment flow is:

01. Request

Create the payment request.

02. Checkout

Generate the secure Stripe destination.

03. Dispatch

Send Email, SMS and/or WhatsApp.

04. Event

Process payment events and automation.

Stripe Integration

Firetip uses Stripe Checkout as the payment destination. Firetip should not collect or store raw card details.

Connection

A connected Stripe account is represented by the Firetip Stripe connection layer.

Stripe Account ↓ Firetip Payment Request ↓ Stripe Checkout Session ↓ Customer Payment ↓ Stripe Event ↓ Firetip Payment Event

Email Dispatch

Firetip Email can deliver the payment request directly to the customer's email address.

Typical message

Subject: Your payment is ready Hello {{customer_name}}, You have received a secure payment request. Amount: {{amount}} {{currency}} Reference: {{reference}} Pay securely: {{checkout_url}} Thank you.

SMS Dispatch

SMS is intended primarily for short payment notifications and reminders.

FIRETIP PAYMENT Your payment request for {{amount}} {{currency}} is ready. Pay securely: {{checkout_url}} Ref: {{reference}}

WhatsApp Payment Dispatch

WhatsApp provides a conversational payment channel. The customer receives the payment request within their WhatsApp conversation rather than having to return to an email.

WhatsApp integration layer

Firetip's payment system sends the payment event and message payload to the configured WhatsApp integration. The actual WhatsApp transport and account configuration remains controlled by the connected WhatsApp infrastructure.

Example payment message

FIRETIP PAYMENT Hi {{customer_name}}, Your payment request is ready. Amount: {{amount}} {{currency}} Reference: {{reference}} Complete your payment securely: {{checkout_url}} FIRETIP™

Recommended WhatsApp variables

Variable	Description
`{{customer_name}}`	Customer or company name.
`{{amount}}`	Payment amount.
`{{currency}}`	Payment currency.
`{{reference}}`	Firetip payment reference.
`{{checkout_url}}`	Secure Stripe Checkout destination.

Payment Events

Payment state should be represented as events so downstream Firetip automation can react without tightly coupling the communication channel to the payment processor.

Event	Meaning	Typical Action
`payment.created`	Payment request created.	Dispatch payment communication.
`payment.pending`	Customer has not completed payment.	Schedule reminder.
`payment.completed`	Stripe confirms successful payment.	Send confirmation.
`payment.failed`	Payment attempt failed.	Start recovery workflow.
`payment.expired`	Payment request is no longer active.	Notify or create replacement.
`payment.cancelled`	Request cancelled.	Stop pending communication.

Payment Automation

Payment events can become automation triggers inside Firetip.

payment.created ↓ Email / SMS / WhatsApp ↓ WAIT ↓ payment.pending ↓ Reminder ↓ payment.completed ↓ Confirmation

Example recovery workflow

WHEN payment.pending WAIT 24 HOURS IF payment.status != paid SEND WhatsApp reminder WAIT 24 HOURS IF payment.status != paid SEND SMS reminder

Payment Creation Payload

The dashboard sends the payment request to the Firetip payment creation endpoint.

{ "customer": "Example Customer", "email": "customer@example.com", "phone": "+447700900000", "amount": "249.00", "currency": "GBP", "description": "Invoice INV-2026-00144", "reference": "INV-2026-00144", "send_email": true, "send_sms": false, "send_whatsapp": true }

Endpoint

POST payments/create_payment.php

Expected response

{ "success": true, "payment_id": "PAY-2026-00001", "checkout_url": "https://checkout.stripe.com/..." }

Security Model

Firetip should treat the payment system as an orchestration and communication layer rather than a card-storage system.

Stripe handles payment processing.
Firetip stores payment request metadata rather than raw card details.
Checkout destinations should be generated by the authenticated payment backend.
Payment events should be validated before changing a request to paid.
Customer communication should use authenticated Firetip dispatch infrastructure.
WhatsApp numbers should be validated and associated with the intended customer before dispatch.

Important

Never mark a payment as paid merely because a customer reaches a success URL. The payment backend should rely on a validated payment-provider event before changing the persistent payment state.