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
- 98d99b622c0fef648e393c9d14c8db3e482cdaf3181da7e6ed2ade6c730fcbb1
- request
- e460d694dde1e8dadf196dac1f857fb194461c2f933df93749cb93b51d1bcbb1
- transaction
- 4a926532b6e8942d0a2d678052ddd0ab3e655b348f02e4dd1efb16b4541827d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55946
the chainentry 55946
- sealed to the entry before
- 440f0874eb13c9a3f2e49d35f2caf2580c667ae82e833fefc68d5bbbc2f5ea5b
- this leaf
- ebc745c1ae73c6d5b4728adddd8aafb0aba5de7c4b758cb82c4f75f1f4b6cea9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FAeAkLK96AWI/4dFmmH0aXNGxdt5wPRMrA2UsXTxOo+u4imT1iiYGbA4EVIWkBkBPvJ3olJvECX8JeC+8QUBAA==