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
- 7f88adbabf51afa542a3d4ba158be5f85c39401d75a6f544317d9ccf53f7d2b8
- request
- ec035d6ba7cb001cab1bc304f53e8709b1d3a7bb4ed8c8bda397b89075b3a434
- transaction
- 019fb4133d2a1a7e115564db2c107f1ded61435923205a62cbe83ec363eaf9f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54750
the chainentry 54750
- sealed to the entry before
- 4411efda4d7720dbcb2ab659591551439beda526dae0666e121cd4e9b80527cb
- this leaf
- 1b234878d52f83108d1b7b4d37132b6d1f7452f4f0dd4b4a20dbcb5210a4c874
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n13a0+m4DIVwop3mFgty1U46XxB0uQR9JIqMO6nDJn2uoYoj3yDIAdFDJKG4/evSgdV05J4kAFnAESWns1qoCA==