“Where can I update my payment method?”
It sounds simple. In practice, it can lead to instructions, another account search and a follow-up question.
We developed a route from FRED to the relevant Stripe self-service flow. AI recognises the request, checks the intended customer relationship and can provide the appropriate link. The customer makes the actual change in payment management.
AI opens the right route
The implemented workflow uses the verified contract relationship. It must not infer access to somebody else’s payment settings from a similar name.
Illustrative example: a customer wants to use a different payment method. After the required checks, they receive the appropriate route. The conversation does not collect full card or bank-account details. This example is fictional.

Who does what?
| Participant | Responsibility |
|---|---|
| FRED | Understand the request, check the relationship, provide the intended link |
| Customer | Make the desired change |
| Payment management | Process it through the configured workflow |
| Team | Resolve uncertain associations or exceptions |
A link does not confirm that an update succeeded. AI needs an appropriate result before describing the change as complete.

Built around a specific service question
AI contributed to developing the matching, tool and result handling. The outcome is a limited action that fits an existing service process. It depends on portal configuration and the enabled channel.
Outstanding balances use a different workflow: invoice information from Stripe. Keeping these tasks distinct prevents a payment question from triggering the wrong action.
Sources.
- SolvraONE: own development and technical source reviewOwn source · As of
- Stripe: customer portalVendor / primary · As of


