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
- ade954aea75ab81a288a5df309c56b431aa39fc24e0589ab9e8d94c863f3a534
- request
- d273ce0ff9b28c631dd00977f4f82925c708a04cab66e3cd46c866ed2550acdd
- transaction
- 32531d2113505a4825a86a526c120f869aa4471df3daf1bb99ecf1454ac224afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53619
the chainentry 53619
- sealed to the entry before
- 0fbd199191f0022f881523df3decc065608d0b7106ec39a63350dbd2994a4b45
- this leaf
- 1bcd8db912d511c8cad33ea1f826dd421a7a29664baa6b0b8bfc05abd25d4d80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AExTY6ZhbGjpqyyM0GeWn7jvbD1tHQTljZgMGWRuilQ14zFqub/YJxxYFbE0piZbsc0Vy2mM3bvG2UxS3iMmBg==