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
- b9a9dadb2914de3565c128276b579760df82fd37cfce8e845c69dd6688c70663
- request
- 7e439ada02eea801aeda43c6ca900cf73d1103d5dcc5c6c0060d1aa500db127c
- transaction
- 38e373420602c5e58ce6c80470234a6ebc637c3fcc0037d60c1cc2d953029049computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69129
the chainentry 69129
- sealed to the entry before
- 7df3ff53f088df3a39bad38a8fde8aa55fb353c3c88e11d06b0e685e6f2780e2
- this leaf
- e4f4bf5513c2dd82b91c35004a951b711c6edcb64e5ffd4a2718bed0a368b088
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XniQs0W2mfH5HlGG0UHTl3MTKiHQWDl/YnFfes1Hm5yg+2f6e7sUlxVQgwBgBsKtQpaV582uJkk+9vXGAPfoBQ==