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
- 361976c21f061dd16bb4a2c06096524a0ae1299d4e822db82141f700016657da
- request
- 19cb3d44bbe4280c1ff44519fb5770c47b2bfdcfe01cde9319a67f926e664b59
- transaction
- 73b97581f13a54103aa275648b1b47d831ace2b09eee2ecb4e2ac86bc333fad1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53536
the chainentry 53536
- sealed to the entry before
- e961501717ef4652701b747492184faf42efee31edb56b1a11934721613229ad
- this leaf
- 6c77d111998289191ad48c1600f51a24d361f19012922f4d524fc293173fa48a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lic0xGDqvt6E1XuNED8dw72Qp3kpOHDP0L3I7FZT+HTBpqFkRZ3nKcXM3eBKVeDkwo8bzIIO2mtbnCJJHDHwDA==