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
- 3abebdf7887fc5eeaba0d89c340e84cac72d52f068883800e3921040a47cf51e
- request
- 00d348fa08b4de7741a2caca4b390c0e4d54ec94d44ce511b9e2332f044471c9
- transaction
- 220fb6c6b08138855f73dae56f709d1458144bc21fa1df783b1c027ff0efce88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1875
the chainentry 1875
- sealed to the entry before
- 0bd22ccd04dc0d4ccbfee3c8304f61cafde118fe920ce5e948e006f84adf70c7
- this leaf
- a9a1ac214ddc31906aa3cab7f0e4e4dad32a5bc9cd0f6394135b162ee353e879
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IwdtdUlE8oifyv+u9ucknWd2Gl6ce7pjPlVBCwoBf2biIeBmnT9S/aEvk8s+sh3FO42U8yqi/mNOM9Ahg5tQCQ==