why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- b69b5d152ddf50b8d6167bc722937ec6b3d3c7018d11fa53c04db17eb197ba82
- request
- 90f6df5ebca05fb4ff438930ca3834e0235b66bccfdb86b82281a7abbd3468ea
- transaction
- f99c605d2c7a3664284986c15adc5260e89535425c7bdf336b2b79a7756c7f7fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38445
the chainentry 38445
- sealed to the entry before
- 990998b836b64158f017ffb9770a03d84daaaf38ee9922272b7a440851e7b350
- this leaf
- 04ed9fe2a86e43eeb862bf08ea00bad62fdbabfa020a1f9f4352a24c9279a86d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ePIS3GQhX2dGfjv3dFFJ0bYGBtnLRsjYZyht3zyM6c3CtAWtxPu4xu1SSF7PCAkMF+F0zqCNaQqN1nM8TlsRAQ==