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
- 60d64c26a15017d5b2d6b67ec2aebc69f23c48ec35f5eb8b538dd2a6f7acd48a
- request
- 5d066b2aa0d502f344ae5195dcaf23505e0891a0c9d4f91461201005daa77871
- transaction
- 10c655f4d1aaaea05229023403514599edc6e516bc7b9bbdd12c87c619d25dfecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39882
the chainentry 39882
- sealed to the entry before
- d398a93cb216578962b409965f72c5c6146ebfb37ad6760ccd023796ea0f5696
- this leaf
- 18eab37848767999de99abd131b1f2cd56897cc62f943745a30647d074bd4ac0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +0Y3pg2TEaIughlsgaRvi1eJtgwfysT+l2QlMN0s9iCZQ/GRsVfM4qw9VN7qAUChw/zpQHRUDd9dXbUVqfYdAA==