Payment teams, finance operators and online sellers often need a customer message immediately after a transaction changes. CityPay records the payment event, while Mobile Message can deliver the plain text update. A Zapier workflow links those moments so staff do not have to watch the gateway and copy numbers into a separate messaging tool.

Use Transaction Successful. to send a receipt-style confirmation or service update. Transaction Failed can alert a customer to try again, and New Paylink Token can send a payment link when a token is created. Token Cancelled can also notify an internal recipient that a payment path is no longer available. CityPay actions provide another option for workflows started by Mobile Message, such as creating a Paylink Token after an inbound SMS, but use that only where the request and required payment data are clear. Each Zap has one trigger and one action. Map CityPay transaction fields in Zapier, write a concise message, and test before publishing. Both platforms need active accounts.