PayFunnels

Use Case Scenarios

• The right link shape for the offer

  A new offer is approved. The agent reads its terms and chooses the route rather than defaulting to one. A pilot that should end by itself becomes Create Payment Plan Link, which bills a fixed number of times and cancels itself, so nobody has to remember to stop it. An open-ended retainer becomes Create Recurring Payment Link. A community donation becomes Create Pay What You Want Link with recurring switched on so a supporter can choose to give monthly. If the offer carries an onboarding charge, Create Setup Fee runs first and its identifier is attached to the link. The finished URL posts into Slack and onto the deal record in HubSpot.

• Dunning that actually gets worked

  On a schedule, the agent calls List Payments filtered to failed, which is the dunning queue in practice. For each one it reads Get Payment for the full breakdown, then reads the customer's subscription with Get Subscription and compares the total due against the total subscription amount, which is the arrears picture on a payment plan. Accounts inside a grace window get a reminder over Brevo. Accounts past it are assembled into a review list with the amount owed, the cycles remaining, and the payment history, and posted for a person to decide between another attempt, a pause, and a cancellation.

• A refund that does not fall through the unit trap

  A refund is agreed in support. The agent reads the payment with Get Payment, which breaks out the tax, the setup fee, the processing fee, and anything already refunded, so the figure it proposes is the actual remaining balance rather than the headline price. It then converts to the smallest currency unit, because Refund Payment takes cents while every payment link amount is in the major unit, and a naive pass would return twenty five cents where twenty five dollars was meant. It supplies one of the three reasons the card networks recognize, and posts the confirmed refund back into the Zendesk ticket.