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
- 610efa65ae0988b26cddff730b4d58b1b29ceb84d2a5464cd2ef87ec91ce0ebe
- request
- ec8caaca5d9b7af1fc78ea7726a513c169bcfa785535319775d2d95d12e2c252
- transaction
- 72d45c71a2934bf0adc42de5eea5cce70d9e752f67ebeaa625fe22ef7dd2794acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3610
the chainentry 3610
- sealed to the entry before
- 74f53cd760feda38d88902d88869b598bb23512986cdd7c88dd404a19315ffb9
- this leaf
- 0b11d295ff7b343a0a836d31b681d64cd64aed35177f158a050510b0befa8a6e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c7m0DOz7XVp7yRsZVBflGcNjdjL57X6BU2rgWQFBfXYV5xKea815ktRpkh0GzxQo+P7mUySaDDz/egWFUKqwCQ==