# Fidel API Brand Voice

> A technical, high-performance voice that balances developer utility with enterprise reliability.

## Positioning
Fidel API is a financial infrastructure platform that provides a connectivity layer for card-linked experiences. It is built for developers and businesses looking to leverage real-time payment events to create reward programs and personalized user experiences.

## Voice principles
*   **Functional:** Focuses on what the product does and how it works, using active verbs like "connect," "capture," and "leverage."
*   **Scalable:** Uses language that suggests growth and robustness, positioning the tool as both easy to start and powerful for large-scale use.
*   **Technical:** Speaks directly to a developer audience using industry-standard terminology without unnecessary fluff.
*   **Secure:** Maintains a professional, authoritative tone when discussing data, reliability, and platform standards.

## Tone by context
| Context | Tone |
|---|---|
| Marketing Hero | Bold and outcome-oriented, focusing on speed and "real-time" capabilities. |
| Product Features | Descriptive and benefit-driven, explaining the "how" behind the connectivity. |
| Developer Section | Precise and list-oriented, focusing on tools, environments, and documentation. |
| Call to Action | Direct and urgent, emphasizing the "fastest way" to begin. |

## Lexicon
*   **Use:** Real-time, engine, connectivity layer, card-linked, embed, leverage, secure, reliable, powerful, premium, event-based.
*   **Avoid:** "Magic" (use "real-time"), "Easy" (use "simple" or "fastest way"), "Middleman" (use "connectivity layer").

## Messaging do's and don'ts
*   **Do:** Emphasize the "real-time" nature of the data and events.
*   **Do:** Use "Engine" or "Layer" to describe the product's role in the tech stack.
*   **Do:** Highlight the developer-first nature of the platform (documentation, test environments).
*   **Don't:** Use flowery or metaphorical language that obscures the technical function.
*   **Don't:** Focus on the end-consumer experience without mentioning the developer tools that power it.
*   **Don't:** Overpromise simplicity without acknowledging the "powerful" scale of the API.

## Evidence
*   "The Engine for Real-Time Rewards"
*   "Simple to start. Powerful as you grow."
*   "Embed Fidel API as a connectivity layer"
*   "Designed for Developers"
*   "The fastest way to bring card-linked experiences to your users."