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
- 0e5aba6755c57f54684b16321b32b1623abdbff1ceefec9639884ee9449ac9fc
- request
- cd63315ddb466c6032b856524d44c7eab394ba0f11b27c23f97bfab045cca86b
- transaction
- 63847cb01c1b7f324f542251113a87f6e4b75e49163a72f6825a5aa4bea2baf9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38826
the chainentry 38826
- sealed to the entry before
- a8d5360b34a5ea14cafa130f67d9894b4b48c4976c264d469ef81d5022e941a8
- this leaf
- 658425ce38d5b59cf2ae074fac979f8767967df7d7fce56469e339e1b886b3ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DrSYaRtCAWGqWe5tOvzaKEGo5R1gTnkHPKHNa6DYdD+7rde8z+ktY7WX1pt5SqWcK5T9UJ+6HsVI+fgSmiSSCw==