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
- 313af61a78da236268dcf3d7c4026c5663cbc63d00398d9c0ef87447f3e569bc
- request
- de1f6cbd5fe37a519dbb3dd6ebdc62fcdd2418e439ce3d952a31e0e5622f5fa5
- transaction
- ce2b4a3d5d2a25c56d2c0775980c7509b4588e8f29038c18e2a9e49d4f5be424computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 426
the chainentry 426
- sealed to the entry before
- 1c128093e0bc530b69e9412c42b8973936bb6452303373d3708d9410797e2c05
- this leaf
- 40ea785f1cb1148cc1b7529cd01aab88ae7af31eeb3d9ad8e3d97790a5f2791a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YvPGcZQG59kwV7uF6zlnAw1WAZBV/boeNpqWSOlShNAH72RQpcUumovBCdVURkhv/OeQKmWDHpZUReeq2EfGBA==