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
- dadd2106be84c947361de4282352a5459f0bd94623af6564e40f49abfc9a5203
- request
- f2201ed1fd1118dd95fd4147d8f7071cc3ad3b41817738418ef80c1b2c1f3ee3
- transaction
- df13bb05a339b59232003c5a303c41cfcdf9eede0b9b13ca0bd5a43cf852670acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64991
the chainentry 64991
- sealed to the entry before
- d3023276bd6a9d29b4fcb023451d665b2a5ccaefd3ba1b94312f9e02077ba5b0
- this leaf
- 4728557d8c5a8775fe4ebc32cb2941f3e863383ddb67355311280ba701b2598d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JQdvbKAL0Cg1tFHHzBYdmVnh+aWB6NsNHn2ezMlzjo5Pk2e1Beruu4/gEE9DdNemt54NNGSKWjI1C00Yv05wBQ==