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
- ed4a19d408a6ad4a30241724e0d8051fa512fa72d2d950b7305c3bdef119dd0d
- request
- 98dcc0d02f384cbda45932e05ee721ecb2a2fdf3344c0e0ca9bbba9768559a6d
- transaction
- 362772cd06cb0f58d8b0db2b893ba0b16cfaf7f092dc60d0ba22cfb3999450d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6082
the chainentry 6082
- sealed to the entry before
- c93a8ed2f6028060a3020afb07a183bca26cfcc04c8a59d796b875c11227c27a
- this leaf
- b529da962e7c4ee8a942f0158afa91747acda41024d949b4cb88eee5d8038e51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dTc9gK4FaMBsDkHUngtU2XmVGZNaZvOd4YoOYRAc6IWEMnRUaEvagG6U2xe++eXsSQKuy0KOOZqnNMJty7zDDw==