Rakuten Card Data API

Rakuten Card Co., Ltd. · Banking

楽天カード：明細確認アプリ is Rakuten Card Co., Ltd.'s official card-management app for Rakuten Card members in Japan. Members sign in with Rakuten ID and, where required, a card second password to check monthly meisai statements, purchase alerts, available shopping and cashing credit, revolving-payment capacity, and Rakuten Point and Rakuten Cash balances. The app also brings together linked Rakuten Bank balances, net-cashing requests, auto-revolving enrollment, in-app card-number display and Google Pay provisioning. Cardholders with multiple cards can switch between them to review card-specific payments and service availability alongside the issuer's e-navi web service. As the card-issuing arm of Rakuten Group, Rakuten Card issues Visa, Mastercard, JCB and American Express cards whose spending earns Rakuten Points toward the group's Super Point UP programme, and it competes for Japanese cardholders with issuers such as JCB, Credit Saison, d CARD, PayPay Card and Epos Card.

Meisai billing months tie statementYearMonth to monthlyTotalAmount and paymentYearMonthDay, with charge-level salesSequenceNumber, usageDate, usageAmount and payMethodDivisionName for household expense ledgers. Separate currentUsage, revolvingUsage and pointPaymentAmount values distinguish spending and repayment components, while usage alerts stamp each authorization with cardUsageNotificationId and usageTime and carry familyUsageDivisionName and cancelUsageFlag for family-card classification and cancelled-charge handling.

Credit-capacity records pair shoppingUtilizableAmount, cashingUtilizableAmount and revolvingUtilizableAmount with their respective limits and balances. A purchase planner can monitor remaining headroom, while a direct-debit coverage check compares the billed amount and due date with linked-bank accountBalance, lastUpdatedDateTime and balanceInsufficientFlag. Loyalty dashboards can track allPoint, limitedPoint, rakutenCash, spuPoint and rakutenRank separately rather than collapsing points and stored cash into one balance.

Card-portfolio records add cardBrandKey, cardTypeName, familyCardFlag, edyCardFlag and netCashingAvailableFlag, so a multi-card household tool can tell family cards, Edy-enabled cards and cash-advance-eligible cards apart. Net-cashing draws are described by loanAmount, transferDate and paymentMethod, while autoRevoStatus records whether auto-revolving is enrolled, which lets a borrowing-cost monitor watch how cash advances and revolving balances build up. openData Studio turns these statement, capacity, bank-balance, reward and card-portfolio records into callable open data for authorized integrations.

Screenshots

API surface

The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.

Card login

POST /v1/card-sessions/start osint

Signs the cardholder in with Rakuten ID, password and optional second password. Returned card-session and Omni tokens plus userHash support later authenticated card requests.

Auth: No existing session required. The JSON body carries userId and pwd, optional secondPwd, authMethod, loginType, privacyPolicyVersion, deviceRootedFlag and exchangeToken. It returns accessToken, refreshToken, omniAccessToken, omniRefreshToken, userHash, authenticationKey and webMemberIdHash for subsequent session-authenticated calls.

userId
pwd
secondPwd
authMethod
loginType
accessToken
refreshToken
omniAccessToken
omniRefreshToken
userHash
webMemberIdHash
authenticationKey
eeid
secondPwdRegisteredFlag
cardData

POST /v1/card-sessions/start HTTP/1.1
Content-Type: application/json

{
  "authMethod": "PASSWORD",
  "deviceRootedFlag": "0",
  "loginType": "1",
  "privacyPolicyVersion": "20240926",
  "userId": "[email protected]",
  "pwd": "<password>",
  "secondPwd": "<second-password>",
  "exchangeToken": ""
}

{
  "resultCode": "0",
  "accessToken": "<access-token>",
  "refreshToken": "<refresh-token>",
  "omniAccessToken": "<omni-access-token>",
  "omniRefreshToken": "<omni-refresh-token>",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "authenticationKey": "<auth-key>",
  "eeid": "<eeid>",
  "secondPwdRegisteredFlag": "1",
  "skipSecondPwdFlag": "0",
  "needSkipSecondPwdSetting": "0",
  "needCardSelectionFlag": "0",
  "cardData": {
    "cardId": "card_demo_001",
    "cardName": "楽天カード",
    "maskedCardNo": "************1234",
    "cardDigit": "1234",
    "cardBrandKey": "VISA"
  }
}

Home snapshot

POST /v1/card-overviews/query opendata

Loads the signed-in home: wallet of cards, this cycle's totalPaymentAmount, earned points and campaign flags that drive the home tiles.

Auth: Cardholder session tokens supplied in the JSON body: cardId, loginType, userHash, omniAccessToken, omniRefreshToken and authenticationKey. App and device metadata accompany the request.

designModeSettingFlag
resultCode
cardList
cardId
cardName
cardDigit
earnedPoint
totalAmount
paymentDate
totalReductionPoint
panSuspendFlag
enteredBonusCampaign

POST /v1/card-overviews/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "loginType": "1",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "omniRefreshToken": "<omni-refresh-token>",
  "authenticationKey": "<auth-key>",
  "latestCardInfoAcquisitionFlag": "1",
  "designModeSettingFlag": "0"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "omniAccessToken": "<omni-access-token>",
  "needCardSelectionFlag": "0",
  "cardData": {
    "cardId": "card_demo_001",
    "cardName": "楽天カード",
    "maskedCardNo": "************1234",
    "cardDigit": "1234"
  },
  "cardList": [
    {
      "cardId": "card_demo_001",
      "cardName": "楽天カード",
      "cardDigit": "1234",
      "cardIconUrl": "<illustrative-resource-url>",
      "earnedPoint": "1250",
      "cardType": "1",
      "cardlessFlag": "0"
    }
  ],
  "totalPaymentAmount": {
    "totalAmount": "45820",
    "paymentDate": "20261027"
  },
  "totalReductionPoint": {
    "totalReductionPoint": "320"
  },
  "panSuspendFlag": "0",
  "enteredBonusCampaign": false
}

Header points

POST /v1/reward-snapshots/query openfinance

Returns the header point snapshot: total, limited, temporary and Super Point Up balances plus Rakuten Cash and membership rank.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash and omniAccessToken; pointRefreshFlag controls the reward refresh.

pointRefreshFlag
allPoint
limitedPoint
rakutenCash
tempPoint
fixedPoint
usedPoint
spuPoint
rakutenRank
rakutenRankJ
rakutenRankE
rankImageURL

POST /v1/reward-snapshots/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "pointRefreshFlag": "1"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "omniAccessToken": "<omni-access-token>",
  "pointData": {
    "allPoint": "15420",
    "limitedPoint": "800",
    "rakutenCash": "2500",
    "tempPoint": "120",
    "fixedPoint": "14500",
    "usedPoint": "300",
    "spuPoint": "4",
    "rakutenRank": "GOLD",
    "rakutenRankJ": "ゴールド",
    "rakutenRankE": "Gold",
    "rankImageURL": "<illustrative-resource-url>"
  },
  "emergencyBannerList": [],
  "importantMessages": [],
  "additionalMessages": []
}

Monthly statement search

POST /v1/billing-periods/query openbanking

Pages monthly meisai for selected year-months: billed total, revolving/cashing split, point-pay amount, debit bank, and per-charge usage rows.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example. Statement selection is supplied in the same body.

statementGetType
targetYearMonthList
latestDate
oldestDate
statementYearMonth
statementDivision
statementDivisionName
paymentYearMonthDay
monthlyTotalAmount
bankName
accountNo
totalChargeAmount
currentUsage
revolvingUsage
pointPaymentAmount
cardPoint
totalPoint
salesSequenceNumber
usageDate
usageAmount
payMethodDivisionName

POST /v1/billing-periods/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "statementGetType": "LATEST",
  "targetYearMonthList": [
    "202610",
    "202609"
  ],
  "designModeSettingFlag": "0"
}

{
  "resultCode": "0",
  "latestDate": "20261022",
  "oldestDate": "202401",
  "preferentialRateFlag": "0",
  "statementDataList": [
    {
      "statementYearMonth": "202610",
      "statementDivision": "1",
      "statementDivisionName": "確定",
      "paymentYearMonthDay": "20261027",
      "monthlyTotalAmount": "45820",
      "bankName": "楽天銀行",
      "bankBranchName": "本店",
      "accountNo": "****1234",
      "accountRegisteredFlag": "1",
      "monthlyPaymentResultType": "0",
      "revolvingCloseTime": "20261015",
      "summaryData": {
        "totalChargeAmount": "45820",
        "currentUsage": "38200",
        "revolvingUsage": "5000",
        "revolvingTotalFee": "320",
        "cashingTotalAmount": "0",
        "cashingTotalFee": "0",
        "pointPaymentAmount": "1000",
        "statementTotalAmount": "44820",
        "unsettledAmount": "0",
        "paymentFixDay": "20261027",
        "familyUsageTotalAmount": "2400",
        "savingPointData": {
          "cardPoint": "382",
          "familyPoint": "24",
          "cancelPoint": "0",
          "bonusPoint": "50",
          "subTotalPoint": "456",
          "totalPoint": "456"
        }
      },
      "monthlyStatementList": [
        {
          "salesSequenceNumber": "10001",
          "statementNo": "ST-202610-001",
          "usageDate": "20261003",
          "userName": "EXAMPLE MEMBER",
          "usageAmount": "3280",
          "payMethodDivision": "01",
          "payMethodDivisionName": "1回払い",
          "payMethodName": "一括",
          "familyUsageDivision": "0",
          "familyUsageDivisionName": "本人"
        }
      ]
    }
  ]
}

Utilizable credit limit

POST /v1/spending-capacity/query openbanking

Returns remaining shopping, cashing and revolving headroom against each limit and the outstanding balance on each bucket.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example.

shoppingUtilizableAmount
shoppingUtilizableLimit
shoppingBalance
cashingUtilizableAmount
cashingUtilizableLimit
cashingBalance
revolvingUtilizableAmount
revolvingUtilizableLimit
revolvingBalance
currentDate

POST /v1/spending-capacity/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "loginType": "1"
}

{
  "resultCode": "0",
  "currentDate": "20261022",
  "shoppingUtilizableAmount": "420000",
  "shoppingUtilizableLimit": "500000",
  "shoppingBalance": "80000",
  "cashingUtilizableAmount": "180000",
  "cashingUtilizableLimit": "200000",
  "cashingBalance": "20000",
  "revolvingUtilizableAmount": "150000",
  "revolvingUtilizableLimit": "200000",
  "revolvingBalance": "50000",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "omniAccessToken": "<omni-access-token>",
  "secondPwdRegisteredFlag": "1",
  "skipSecondPwdFlag": "0",
  "needCardSelectionFlag": "0"
}

Card usage notifications

POST /v1/purchase-alerts/query openbanking

Lists near-real-time card-present and card-not-present authorizations with amount, masked PAN, family-card flag and cancel state.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example.

cardUsageNotificationId
usageDate
usageTime
usageAmount
cardName
maskedCardNo
cardDigit
familyUsageDivision
familyUsageDivisionName
cancelUsageFlag
cancelUsageFlagName
usageCardId

POST /v1/purchase-alerts/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "cardData": {
    "cardId": "card_demo_001",
    "cardName": "楽天カード",
    "maskedCardNo": "************1234"
  },
  "usageList": [
    {
      "cardUsageNotificationId": "UN-20261022-8891",
      "usageDate": "20261022",
      "usageTime": "14:32:11",
      "usageAmount": "2180",
      "cardName": "楽天カード",
      "maskedCardNo": "************1234",
      "cardDigit": "1234",
      "cardId": "card_demo_001",
      "usageCardId": "card_demo_001",
      "familyUsageDivision": "0",
      "familyUsageDivisionName": "本人",
      "cancelUsageFlag": "0",
      "cancelUsageFlagName": ""
    }
  ]
}

Point information

POST /v1/reward-options/query openfinance

Loads the point-info screen: reduction points this cycle, whether the card is a Rakuten Point Card, and whether point-pay is available.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example.

totalReductionPoint
rakutenPointCardFlag
pointPaymentAvailableFlag
allPoint
rakutenCash
cardId
cardName

POST /v1/reward-options/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "totalReductionPoint": "320",
  "cardData": {
    "cardId": "card_demo_001",
    "cardName": "楽天カード",
    "rakutenPointCardFlag": "1",
    "pointPaymentAvailableFlag": "1"
  },
  "pointNoCashNoPay": {
    "allPoint": "15420"
  },
  "pointCashPayInstalled": {
    "rakutenCash": "2500"
  }
}

Rakuten Bank balances

POST /v1/debit-account-funds/query openbanking

Reads linked Rakuten Bank deposit balances used for card auto-debit, including an insufficient-balance flag for the coming payment date.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example. A linked Rakuten Bank account is required.

cardBankDataList
cardId
agreementStatus
balanceInsufficientFlag
bankErrorCode
accountBalance
lastUpdatedDateTime

POST /v1/debit-account-funds/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "cardBankDataList": [
    {
      "cardId": "card_demo_001",
      "agreementStatus": "LINKED",
      "balanceInsufficientFlag": "0",
      "bankErrorCode": "",
      "balanceInformation": {
        "accountBalance": "186540",
        "lastUpdatedDateTime": "2026-10-22T09:15:00+09:00"
      }
    }
  ],
  "agreementLink": {
    "url": "<illustrative-resource-url>"
  }
}

Encrypted PAN

POST /v1/card-display/prepare osint

Returns the full PAN, expiry and CVV for in-app card-number display / Google Pay, encrypted to the device publicKey.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example. Device binding also requires deviceToken, innerDeviceName and publicKey; a second password may be required unless skipSecondPwdFlag is set.

deviceToken
innerDeviceName
publicKey
cardName
cardIdHash
cardNo
name
expirationYear
expirationMonth
cvv
cardIconUrl

POST /v1/card-display/prepare HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "deviceToken": "<device-token>",
  "innerDeviceName": "Pixel 8",
  "publicKey": "<device-public-key>"
}

{
  "resultCode": "0",
  "cardName": "楽天カード",
  "cardIconUrl": "<illustrative-resource-url>",
  "cardIdHash": "<card-id-hash>",
  "cardNo": "<encrypted-pan>",
  "name": "EXAMPLE MEMBER",
  "expirationYear": "28",
  "expirationMonth": "12",
  "cvv": "<encrypted-cvv>",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "secondPwdRegisteredFlag": "1",
  "skipSecondPwdFlag": "0"
}

Net cashing register

POST /v1/advance-requests/submit openbanking

Submits a net-cashing (カードローン) draw to the linked bank for loanAmount on transferDate with the chosen repayment method.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example. The card must have netCashingAvailableFlag enabled.

transferDate
loanAmount
paymentMethod
passCode
initialTransferDate
cashAdvanceUtilizableAmount
authNumber
netCashingAvailableFlag
resultCode

POST /v1/advance-requests/submit HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "transferDate": "20261023",
  "loanAmount": "50000",
  "paymentMethod": "REVO",
  "passCode": "<pin>",
  "initialTransferDate": "20261023",
  "cashAdvanceUtilizableAmount": "180000",
  "authNumber": ""
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "cardData": {
    "cardId": "card_demo_001",
    "netCashingAvailableFlag": "1"
  }
}

Auto-revolving status

POST /v1/repayment-preferences/query openbanking

Reads whether auto-revolving (自動リボ) is enrolled on the card and the campaign copy shown on the auto-revo screens.

Auth: Cardholder session tokens supplied in the JSON body: cardId, userHash, omniAccessToken and authenticationKey. No Bearer header is shown in this example.

autoRevoStatus
contactNumber
revoCampaignBannerText
contractPaymentMethodDivision
resultCode
cardId

POST /v1/repayment-preferences/query HTTP/1.1
Content-Type: application/json

{
  "cardId": "card_demo_001",
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>"
}

{
  "resultCode": "0",
  "autoRevoStatus": "REGISTERED",
  "contactNumber": "<contact-number>",
  "revoCampaignBannerText": "自動リボ登録キャンペーン",
  "userHash": "<user-hash>",
  "webMemberIdHash": "<web-member-id-hash>",
  "cardData": {
    "cardId": "card_demo_001",
    "contractPaymentMethodDivision": "REVO"
  }
}

Member card list

POST /v1/card-portfolio/query opendata

Lists every card on the membership — brand, masked PAN, family/Edy/point-card flags and net-cashing eligibility — for the card-switcher.

Auth: Cardholder session tokens supplied in the JSON body: userHash, omniAccessToken and authenticationKey, with latestCardInfoAcquisitionFlag controlling card-information refresh.

latestCardInfoAcquisitionFlag
needCardSelectionFlag
cardListIndex
cardId
cardName
cardDigit
maskedCardNo
cardBrandKey
cardTypeName
familyCardFlag
edyCardFlag
rakutenPointCardFlag
netCashingAvailableFlag
userName
contractDate
loginSequenceHash

POST /v1/card-portfolio/query HTTP/1.1
Content-Type: application/json

{
  "userHash": "<user-hash>",
  "omniAccessToken": "<omni-access-token>",
  "authenticationKey": "<auth-key>",
  "loginType": "1",
  "latestCardInfoAcquisitionFlag": "1"
}

{
  "resultCode": "0",
  "userHash": "<user-hash>",
  "needCardSelectionFlag": "1",
  "cardList": [
    {
      "cardListIndex": "0",
      "cardId": "card_demo_001",
      "cardName": "楽天カード",
      "cardDigit": "1234",
      "maskedCardNo": "************1234",
      "cardBrandKey": "VISA",
      "cardType": "1",
      "cardTypeName": "一般",
      "familyCardFlag": "0",
      "edyCardFlag": "1",
      "rakutenPointCardFlag": "1",
      "pointPaymentAvailableFlag": "1",
      "netCashingAvailableFlag": "1",
      "partnerCardFlag": "0",
      "allRoundServiceFlag": "1",
      "userName": "EXAMPLE MEMBER",
      "contractDate": "20180315",
      "loginSequenceHash": "<login-sequence-hash>"
    }
  ]
}

Where teams use this data

Household expense classification from meisai
Pull monthlyStatementList rows (usageDate, usageAmount, payMethodDivisionName, familyUsageDivisionName) and roll them into a household ledger, splitting family-card spend from the primary card.
Headroom monitor before large purchases
Watch shoppingUtilizableAmount against shoppingUtilizableLimit (and the cashing/revolving twins) so a checkout or travel planner can warn when a planned charge would breach the remaining limit.
Direct-debit coverage check
Compare statement monthlyTotalAmount and paymentYearMonthDay with linked Rakuten Bank accountBalance and balanceInsufficientFlag to flag a shortfall before the debit date.
Point and rank snapshot for loyalty ops
Read allPoint, limitedPoint, rakutenCash, spuPoint and rakutenRank from the header to drive a loyalty dashboard or Super Point Up progress widget.

Frequently asked questions

What statement fields are represented in the Rakuten Card data API?

Billing records include statementYearMonth, monthlyTotalAmount, paymentYearMonthDay, totalChargeAmount, currentUsage, revolvingUsage and pointPaymentAmount. Charge rows include salesSequenceNumber, usageDate, usageAmount and payMethodDivisionName, supporting billing-period reconciliation and household expense classification.

Can the data support credit-headroom and direct-debit coverage checks?

Shopping, cashing and revolving balances each have corresponding available amounts and limits. Linked Rakuten Bank records include accountBalance, lastUpdatedDateTime and balanceInsufficientFlag, which can be compared with a statement payment amount and due date when the cardholder has authorized access.

Which reward and membership fields are available?

The reward snapshot distinguishes allPoint, limitedPoint, tempPoint, fixedPoint, usedPoint, spuPoint and rakutenCash, alongside rakutenRank. Point-payment records include totalReductionPoint, rakutenPointCardFlag and pointPaymentAvailableFlag, while the card portfolio describes brand, family-card and net-cashing eligibility.

Are these official Rakuten Card endpoints, and how is authentication represented?

No. The paths and payloads are illustrative examples of card-related data and workflows, not documented public Rakuten Card endpoints or an official SDK. In the examples, sign-in uses userId, pwd and an optional secondPwd and returns card-session and Omni tokens; later calls carry userHash, omniAccessToken and authenticationKey in the JSON body, with cardId where needed, and device-bound card details also require deviceToken and publicKey. Every credential and encrypted-card value shown is a placeholder. Nothing here grants account access; an integration must use an authorized access arrangement and protect cardholder credentials, balances and card details.

Apps similar to 楽天カード：明細確認アプリ

MyJCB — MyJCB is JCB's official cardholder app for checking monthly usage amounts and statements, sorting or keyword-filtering meisai, viewing J-POINT balances, switching among registered cards after combined login, and signing in with biometrics or a passkey.
セゾンPortal — セゾンPortal is Credit Saison's smartphone app for viewing card statements and 永久不滅ポイント balances around the clock, managing multiple Saison and UC cards issued by Credit Saison, and setting up Apple Pay or Google Pay from the app.
PayPay — PayPay Card members register the card in the PayPay app to review card details and billing statements there; family-card holders can check their own card number and transaction history in their own PayPay app.
dカードアプリ — NTT Docomo's dカードアプリ lets registered dカード members check payment dates and amounts, d POINT balances and member rank, usage statements and campaigns, and set up Osaifu-Keitai, Apple Pay or Google Pay.
エポスアプリ — Marui Group subsidiary Epos Card's official app shows this month's and next month's payment amounts on a graph, displays Epos Points, and sends real-time notices of card usage.
オリコアプリ — Orient Corporation's Orico app is presented on the issuer's site for checking billed totals, usage statements and accumulated points, alongside the eオリコ web service for statements, point redemption and member procedures.

More Banking apps

Topics

Rakuten Card data API
楽天カード明細
meisai statement data
shoppingUtilizableAmount
Rakuten Point balances
Rakuten Bank balance fields
card usage alerts
net cashing loanAmount

Need this app's data API integrated?

We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.

NDA + SOW on every engagement
Delivery in 3–7 days
Payment only after acceptance
Work scoped to authorized use

Get a quote

Rakuten Card Data API

Screenshots

API surface

Card login

Home snapshot

Header points

Monthly statement search

Utilizable credit limit

Card usage notifications

Point information

Rakuten Bank balances

Encrypted PAN

Net cashing register

Auto-revolving status

Member card list

Data categories

Where teams use this data

Household expense classification from meisai

Headroom monitor before large purchases

Direct-debit coverage check

Point and rank snapshot for loyalty ops

Frequently asked questions

Apps similar to 楽天カード：明細確認アプリ

More Banking apps

5paisa: Demat, Stocks & IPO

Ajaib: Stock, Crypto, US Stock

Albert: Budgeting and Banking

AndroMoney

Topics

Need this app's data API integrated?

Rakuten Card Data API

Screenshots

API surface

Card login

Home snapshot

Header points

Monthly statement search

Utilizable credit limit

Card usage notifications

Point information

Rakuten Bank balances

Encrypted PAN

Net cashing register

Auto-revolving status

Member card list

Data categories

Where teams use this data

Household expense classification from meisai

Headroom monitor before large purchases

Direct-debit coverage check

Point and rank snapshot for loyalty ops

Frequently asked questions

Related apps

Apps similar to 楽天カード：明細確認アプリ

More Banking apps

5paisa: Demat, Stocks & IPO

Ajaib: Stock, Crypto, US Stock

Albert: Budgeting and Banking

AndroMoney

Topics

Need this app's data API integrated?