Skip to content
/bounty
Sign in
All bounties

PayPay

Open
paypay.ne.jp

Japanese payment wallet with balance, point, transaction, and settlement workflows.

Reward
₩500,000
Tier
Platinum
Auth
Browser
APIs
6 APIs
Working now
none
Posted
2026-07-04
Kind
New service
Lifecycle
  1. Open
  2. Claimed
  3. In review
  4. Finalizing
  5. Syncing
  6. Merged
  7. Paid

Scope

This provider targets the unofficial PayPay browser or mobile surface, not a public API. It must handle strong authentication, account state, receipt retrieval, and payment-sensitive actions with careful approval boundaries. The surface is operationally hard and carries legal and anti-abuse risk, especially around transaction history, money movement, and proof of payment.

Expected APIs

6
get-balance-and-limitsGet balance and limitsReadHard

Read the current PayPay wallet balance, point balance, linked payment methods, and relevant transfer or payment limits from the account dashboard.

Inputs
  • account_scopestringOptionalOptional scope selector for wallet, points, or linked funding sources.Example wallet
Outputs
balancepoint_balancelinked_methodslimits
Acceptance
  • Returns the current wallet balance and point balance for the authenticated account.
  • Includes linked funding methods or account-linked payment sources when available.
  • Surfaces applicable daily or per-transaction limits instead of silently omitting them.

Auth required for this API.

list-campaigns-and-expiryList campaigns and expiry detailsReadHard

Fetch active campaigns, coupons, and point-expiry information shown to the user, including any conditions that affect eligibility.

Inputs
  • statusstringOptionalOptional filter for active, upcoming, or expired promotions.Example active
Outputs
campaignscouponspoint_expiry_dateeligibility
Acceptance
  • Returns the campaigns or coupons currently associated with the account.
  • Shows point-expiry timing or expiry windows when the product exposes them.
  • Keeps campaign eligibility details attached to each item instead of flattening them away.

Auth required for this API.

search-payment-historySearch payment historyReadHard

Query transaction history for payments, refunds, and merchant receipts, with enough detail to identify the merchant, amount, and settlement state.

Inputs
  • from_datedateOptionalStart date for the transaction search window.Example 2026-06-01
  • to_datedateOptionalEnd date for the transaction search window.Example 2026-06-30
  • transaction_typestringOptionalOptional filter for payment, refund, transfer, or charge activity.Example payment
Outputs
transactionsmerchant_nameamountstatusreceipt_url
Acceptance
  • Returns matching transactions with merchant and amount details for the requested range.
  • Distinguishes payments from refunds or other settlement events when the account surface provides that information.
  • Includes a receipt or evidence link when the underlying UI exposes one.

Auth required for this API.

prepare-money-movementPrepare money movementWriteHard

Build a preflight request for top-up, transfer, or payment initiation with full amount, counterparty, and source-of-funds details before any execution step.

Inputs
  • movement_typestringRequiredType of money movement to stage.Example payment
  • amountnumberRequiredRequested amount in JPY.Example 2500
  • counterpartyobjectOptionalMerchant, recipient, or target account details needed to stage the request.Example {"name":"Tokyo Store"}
Outputs
draft_idamountcounterpartyfeerequires_approval
Acceptance
  • Produces a draft or staged request rather than submitting a payment immediately.
  • Carries forward the full amount and counterparty details so the user can review them.
  • Flags any fee, limit, or approval requirement before execution.

Auth required for this API.

execute-money-movementExecute money movementWriteHard

Submit the staged PayPay action only after explicit user approval, using the previously prepared amount and counterparty details.

Inputs
  • draft_idstringRequiredIdentifier for the preflight request to execute.Example draft_12345
  • user_approvalbooleanRequiredExplicit confirmation that the user approved the money movement.Example true
Outputs
transaction_idstatussubmitted_atamount
Acceptance
  • Refuses to submit unless explicit approval is present.
  • Returns a transaction identifier or a comparable settlement reference after submission.
  • Keeps the approved amount unchanged between preview and execution.

Auth required for this API.

get-transaction-status-and-receiptGet transaction status and receiptReadHard

Retrieve the current state of a payment, refund, dispute, or settlement outcome together with the receipt or evidence payload shown to the user.

Inputs
  • transaction_idstringRequiredTransaction or settlement reference to look up.Example tx_987654
Outputs
transaction_idstatusreceiptdispute_statesettlement_result
Acceptance
  • Returns the latest transaction state for the requested identifier.
  • Includes receipt or evidence content when the account surface makes it available.
  • Exposes dispute or settlement outcome data rather than only a generic success flag.

Auth required for this API.

Suggested surface. Propose changes in your submission if the upstream differs.

Acceptance criteria

  • Service scaffolded from the public @apifuse/provider-sdk
  • All listed APIs implemented with Zod/Standard Schema input & output
  • Each API declares exactly one of healthCheck or healthCheckUnsupported
  • Real upstream fixture data included where applicable
  • bun run check and bun run test pass
  • Auth, credential and env-secret behavior documented. No real secrets committed

Evidence to submit

  • Workspace repository and main commit link
  • SDK version/tag and the create command used
  • API list with input/output summaries
  • healthCheck coverage table per API
  • bun run check and bun run test output

Ready to claim?

Submit a claim. Your workspace is prepared after confirmation.