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
- 91ceacd1d09dd5774a4fb7964e43553ea117f83ba27c19ad2b1fd24d09f87c22
- request
- 67d3d41161ffc1f35b173f9f8b677dcee03291ea1011bbb5792219e9ae43c610
- transaction
- e6ed6b510b2d68d034bf0e69ac970f0beb4ed5b9f2d25d923858a1db0fa777f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31603
the chainentry 31603
- sealed to the entry before
- 8711e7f9d2e5ada22466c5d02e0b3bd6996e7f0235be6dd84a74d2d0c0961daa
- this leaf
- 2bbb3be35b2400b96791d43cf21745da2e910e04ca893b7f02e38bc1cd4d9a07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9cL+f2sf3JGQ51CoXL3HT0Wtut9PYq6gRrvqiN7U6qMext3g1cZxwjDTW8n4W7rMwmIkqJpEwVfD73FPpAvtAA==