platform-guideline 1 linked patterns checked
Braintree Hosted Fields overview
Documents hosted fields for card number, CVV, expiration date, and postal code, with externally hosted payment fields used to reduce PCI scope while keeping a merchant-styled checkout form.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Payment card entry | Choose payment card entry when the task is to charge a card, verify a card, save a card payment method, or replace a card-on-file credential. | Users can type, paste, autofill, delete, select, and correct card number, expiry, CVC, and postal code fields without losing entered values. | Braintree supports hosted card number, CVV, expiration date, and postal code fields for custom-styled checkout pages. |
Comparisons supported by this source
- Payment card entry vs bank details vs input mask vs review before submit
Braintree supports hosted card number, CVV, expiration date, and postal code fields for SAQ A-eligible checkout capture.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: PayPal Braintree. Last checked: .