Add Payment Card to Google Wallet

Add Payment Card to Google Wallet

This endpoint enables a customer's Netevia payment card to be provisioned into Google Wallet, making it available for contactless payments via Google Pay. The request requires the card's unique identifier and, depending on the card type or use case, may include additional fields such as a nickname, order reference, or reissue details. On success, the card is linked to Google Wallet and ready for use in transactions.

Endpoint

POST /api/paymentCards/addToGoogleWallet

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a customer wants to add one of their Netevia payment cards (Physical, Virtual, or Burner) to Google Wallet for mobile contactless payments. This is typically triggered from a card management screen within your partner application after the customer has an active card. All card types supported by Netevia can be provisioned into Google Wallet using this endpoint.

Request Body

The request body accepts one of the following schemas. In all cases, paymentCardId is required as the base field.

Base Request (paymentcardrequest)

With Nickname (paymentcardnicknamerequest)

Extends base request with:

With Order ID (paymentcardorderrequest)

Extends base request with:

With Period (paymentcardwithperiodrequest)

Extends base request with:

Reissue Request (reissuepaymentcardrequest)

Extends base request with:

orderPhysicalPaymentCard — delivery details object:

Obsolete Reissue Request (obsoletereissuepaymentcardrequest)

Extends base request with:

{
  "paymentCardId": "card_a1b2c3d4e5f6",
  "nickName": "My Google Pay Card"
}

Response

200 OK

A successful response confirms that the payment card has been provisioned to Google Wallet. The response body returns a confirmation with masked card details.

{
  "success": true,
  "message": "Payment card successfully added to Google Wallet.",
  "cardId": "card_a1b2c3d4e5f6"
}

Error Codes

Common Mistakes

• Omitting paymentCardId — this field is required in all request variants; the request will fail with 400 if absent
• Sending a postalCode that is not exactly 5 digits — the schema enforces the pattern ^\d{5}$
• Sending a region code that is not exactly 2 characters — both minLength and maxLength are 2 for the state code
• Sending a countryCodeAlpha3 that is not exactly 3 characters — use ISO 3166-1 alpha-3 format (e.g., USA, not US)
• Using an expired or recently refreshed Bearer token — tokens expire after 10 minutes; refresh via POST /api/auth/refresh before calling this endpoint
• Providing a nickName longer than 18 characters — the schema enforces maxLength of 18

Related Endpoints

• POST /api/paymentCards/addToAppleWallet — Add a payment card to Apple Wallet
• GET /api/paymentCards — List all payment cards for the authenticated customer
• POST /api/paymentCards — Create a new payment card (Virtual, Physical, or Burner)
• PUT /api/paymentCards/{paymentCardId} — Update payment card details
• POST /api/auth/v2 — Obtain a Bearer token for authentication

Example

curl -X POST https://api.banking.netevia.dev/api/paymentCards/addToGoogleWallet \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_a1b2c3d4e5f6",
    "nickName": "My Google Pay Card"
  }'