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
- b3552f5e23229bfa5e39d8115b09641d42876bb4e0f05ef5dd8eff6180a0b42a
- request
- 2afd5a87d47ffb8db277d2a1f998db81939e872524398ac3430c269adc680e61
- transaction
- fca8a95c144652e3693935a8ddd1e84364b5aa55aefb5ab020dd7a9de6848239computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2345
the chainentry 2345
- sealed to the entry before
- 2c7355817120f0cea04837dd94d014283a338f16a1d5861a5cccc4998d7493d4
- this leaf
- de203f0cc5f1c0dc805b4c2ff96fbc2a68aa83e4bda3012ee6247e3cebcda6b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OkP0hjziZvxi4KrYv80a+fQp+4S2le702wLRRfEFtc6Oao4qm7g+M/gjUCbvKQQyKBwkPuHMLgrvN7/DsIDeCQ==