How Detection Works
The SDK examines the page URL and HTML to detect the payment provider. Each profile has optimized selectors for that provider’s form structure.Supported Profiles
| Profile | Detection | Fields |
|---|---|---|
| Stripe Elements | URL or HTML contains “stripe” | cardNumber, cardExpiry, cardCvc |
| Adyen Drop-in | HTML contains “adyen-checkout” | encryptedCardNumber, encryptedExpiryDate, encryptedSecurityCode |
| Braintree | HTML contains “braintree-hosted-field” | credit-card-number, expiration, cvv |
| Shopify | URL contains “shopify” | cc-number, cc-exp-month, cc-exp-year, cc-csc |
| Generic | Fallback | Semantic detection via autocomplete, aria-label, placeholder |
Fallback Strategy
If provider-specific selectors fail, the SDK falls back to semantic detection:- Check
autocompleteattributes (cc-number,cc-exp,cc-csc) - Check
aria-labelandplaceholdertext - Check
nameandidattributes for common patterns