Looks like "Japanese format" to me - or something similar.
"Japanese format" is similar to extended NEC protocol - described in my words here:
Extended NEC protocol: 1/4 or 1/3 duty cycle 38khz (21 pulses per bit approx)
9ms mark then 4.5ms space header
560us mark, 560us space zero
560us mark, 1.69ms space one
4 bytes, LSB first
560us mark - long space stop bit of one
option 1 = repeat every 110ms (if wanted), but just 9ms mark, 2.25 space, 560us mark (no data)
option 2 = repeat full message
00ff = default address, custom codes available, byte 4 is inverse of byte 3
byte1 is low byte of address, byte2 is either inverse of byte 1 or high byte
IR protocols are explained well here:
https://www.sbprojects.com/knowledge/ir/nec.php
Your sample seems to be four bytes:
0x40 custom byte hexadecimal 0x40 - will be the same for every button on your remote
0xBF inverse of byte 1
0x80 command byte of 0x80 hexadecimal - will depend on which button you press on the remote
0x7F inverse of byte 3
The only way that I know of to decode NEC or similar protocol is to program a microprocessor to decode the pulse train
If you only need to flash an LED every time ANY IR remote signal is received, then maybe no decoding is necessary. The receiver may have enough output power to drive an LED with series resistor directly, or a transistor or two may be required to supply enough current to the LED and series resistor. It will not be practical to distinguish which button was pressed, or even which remote control type you have used.