`cardmng`

As the name might imply, this service is responsible for handling interactions with physical e-Amusement cards. e-Amusement currently has two different types of cards in circulation. There are classic e-Amusement cards making use of a magnetic stripe, and the newer RFID cards using FeliCa (these are probably what you have). They are identified in requests using the cardtype attribute as in the below table.

e-Amusement cards have a "card number" and a "card id". Confusingly, neither is a number. The card number is the one printed on your card. The card ID is your KONAMI ID. You can (and should) read about the algorithm used for these IDs on the Card IDs page.

In the interest of not wasting space, cardid and cardtype will be omitted from individual breakdowns where their meaning is obvious.

Card types:

`cardtype`	Meaning
`1`	Old style magnetic stripe card
`2`	FeliCa RFID card

cardmng.inquire
cardmng.getrefid
cardmng.bindmodel
cardmng.bindcard
cardmng.authpass
cardmng.getkeepspan
cardmng.getkeepremain
cardmng.getdatalist

`cardmng.inquire`

Request information about a card that has been inserted or touched against a reader.

Request:

<call ...>
    <cardmng method="inquire" cardid="" cardtype="" update="" model*="" />
</call>

update Should the tracked last play time be updated by this inquiry? (Just a guess)

Response:

<response>
    <cardmng status="status" refid="" dataid="" pcode=""  newflag="" binded="" expired=" ecflag="" useridflag="" extidflag="" lastupdate="" />
</response>

To handle this request, we first must lookup if this cardid has ever been seen by our servers before. If not, we abort with a 112 status. Otherwise, we proceeed to check if this card has been seen for this specific game. If we have never seen this card used on this game, it is possible this card was used with an older version of this game, and migration is supported, in which case we report as if we had found a profile for this game.

`refid`	A reference to this card to be used in other requests
`dataid`	Appears to be set the same as `refid`; presumably to allow different keys for game state vs login details.
`newflag`	Inverse of `binded`
`binded`	Has a profile ever been created for this game (or an older version, requiring a migration) (`1` or `0`)
`expired`	? Just set to `0`.

`cardmng.getrefid`

Request:

<call ...>
    <cardmng method="getrefid" cardtype="" cardid=" newflag="" passwd="" model*="" />
</call>

`newflag`	?
`passwd`	The pin for this new user. Should always be a four digit number (and that's worth validating), but it's passed as a string so could feasibly be anything desired.

Response:

<response>
    <cardmng status="status" refid="" dataid="" pcode="" />
</response>

`refid`	A reference to this card to be used in other requests
`dataid`	Appears to be set the same as `refid`; presumably to allow different keys for game state vs login details.
`pcode`	? Not present in captured data.

`cardmng.bindmodel`

Request:

<call ...>
    <cardmng method="bindmodel" refid="" newflag="" model*="" />
</call>

Response:

<response>
    <cardmng status="status" dataid="" />
</response>

`cardmng.bindcard`

Request:

<call ...>
    <cardmng method="bindcard" cardtype="" newid="" refid="" model*="" />
</call>

Response:

<response>
    <cardmng status="status" />
</response>

`cardmng.authpass`

Test a pin for a card. This request notably uses the refid, so required a cardmng.inquire call to be made first.

Request:

<call ...>
    <cardmng method="authpass" refid="" pass="" model*="" />
</call>

`refid`	The reference we received either during `cardmng.inquire` or `cardmng.getrefid` (the latter for new cards)
`pass`	The pin to test. See `cardmng.getrefid`.

Response:

<response>
    <cardmng status="status" />
</response>

If the pin is valid, status should be 0. Otherwise, 116.

`cardmng.getkeepspan`

Request:

<call ...>
    <cardmng method="getkeepspan" model*="" />
</call>

Response:

<response>
    <cardmng status="status" keepspan="" />
</response>

`cardmng.getkeepremain`

Request:

<call ...>
    <cardmng method="getkeepremain" refid="" model*="" />
</call>

Response:

<response>
    <cardmng status="status" keepremain="" />
</response>

`cardmng.getdatalist`

Request:

<call ...>
    <cardmng method="getdatalist" refid="" model*="" />
</call>

Response:

<response>
    <cardmng status="status">
        <item[]>
            <mcode __type="str" />
            <dataid __type="str" />
            <regtime __type="str" />
            <lasttime __type="str" />
            <exptime __type="str" />
            <expflag __type="u8" />
        </item[]>
    </cardmng>
</response>