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
- 9ca02d8603f3b67797e1ae872c1e90ddde80abbc63a0fb8b337c835be6e3eb03
- request
- 8d415ad99d361947303e7435325b368ce0ee5a695aa48dcc74b6570344c83143
- transaction
- ededd698fa420f240f6ac7897e98ddeea820c54b9d580cdacdb8cc12751457becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64108
the chainentry 64108
- sealed to the entry before
- 923c19d94213489188586d439ea1e6ce0983fb2c3adec760473013919c4e0ccb
- this leaf
- 271c884f830c500d01d81d1a447e7e11d6f55bc86c53d096df65a2e74caa6bd2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9PI3bn3Fzbylpm3Hja+8HKn+3X+QHnMrIZDsSZRcEaPH5Zh0FHlhe+i00npQeLSxiEzfXecDB2zw5ivJtlDXCQ==