Describe the bug
When using the RiskDataCollector as documented (in combination with an <Elements> based model), device data is not sent to Kount.
Based on further investigation, recurly.fraud.attachDataCollector() is never called, so a fraud_session_id is never obtained, and therefore recurly.token does not include the appropriate data.
CodeSandbox repro
To Reproduce
- Follow the React Recurly "Implementation Guide"
- Add a
<RiskDataCollector strategy="kount" onError={(error) => console.error(error)} /> element to the payment form
- Load the app and submit the form using testing data
(A modified version of this process, including some debugging aids, is available in the CodeSandbox repro)
Expected behavior
Device data is sent to Kount
Actual behaviour
The fraud functionality is not initialized (e.g. no API call is made to /risk/info, no fraud_session_id is obtained/set, no device data is sent to Kount)
Your Environment
- react-recurly@1.2.6
- react@18.2.0
- Chrome 107.0.5304.87 (arm64) on MacOS Ventura
Describe the bug
When using the
RiskDataCollectoras documented (in combination with an<Elements>based model), device data is not sent to Kount.Based on further investigation,
recurly.fraud.attachDataCollector()is never called, so afraud_session_idis never obtained, and thereforerecurly.tokendoes not include the appropriate data.CodeSandbox repro
To Reproduce
<RiskDataCollector strategy="kount" onError={(error) => console.error(error)} />element to the payment form(A modified version of this process, including some debugging aids, is available in the CodeSandbox repro)
Expected behavior
Device data is sent to Kount
Actual behaviour
The fraud functionality is not initialized (e.g. no API call is made to
/risk/info, nofraud_session_idis obtained/set, no device data is sent to Kount)Your Environment