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
- a96a64cf4d9045f2c4c86729e424add4c1ff2d3c556f2f91d5c9e0cd403f2b01
- request
- 9f6f36b529b237efb2d98def4951dd77507a625d7c96cccbbff023635e03dddb
- transaction
- b9bf1d660f586ce6df0d9bdb379edfb1946619a049bcc0444d9f060df1c95df0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 616
the chainentry 616
- sealed to the entry before
- 2ded7cf8169c536edbc5cbdd33ff8a22cd67e49cf7ea0368922abd993021636b
- this leaf
- 88e85e6d89f1939c5709377e04c406a9737a9fa1e30d3a9ad2aec07923ad8997
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ATtWshU+6izGvVNs4uiafKeoFhVx0KBAl9mIyhtH0CZtaA36HZ2ENO14d0Nd0oX7v1PuVY6lbQgEU6KKlnNiCg==