Digital Wallet Cards icon

Digital Wallet Cards

Interact with Digital Wallet Cards loyalty program API

Overview

The node interacts with a Digital Wallet Cards loyalty program API, specifically managing "Card" resources among others. The Block Card operation allows users to block a specific loyalty card by its unique identifier. Blocking a card typically prevents it from being used in transactions or earning/redeeming points, stamps, or rewards.

This operation is useful in scenarios such as:

  • Temporarily disabling a lost or stolen loyalty card.
  • Preventing fraudulent use of a compromised card.
  • Managing card lifecycle states within a loyalty program.

Example use case: A retailer wants to block a customer's loyalty card after the customer reports it lost, ensuring no further points or benefits can be accrued until the card is unblocked or replaced.

Properties

Name Meaning
Card ID The unique identifier of the card to be blocked (e.g., card_12345...). This is required.

Output

The output JSON contains the response from the API after attempting to block the specified card. It typically includes confirmation of the card's new status or any relevant metadata returned by the API.

The structure generally looks like:

{
  "success": true,
  "cardId": "card_12345",
  "status": "blocked",
  "updatedAt": "2024-06-01T12:00:00Z"
}

(Note: Exact fields depend on the API response but will confirm the card has been blocked.)

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Digital Wallet Cards API.
  • The base URL for API requests is https://api.digitalwallet.cards.
  • The node uses internal utility functions for making HTTP requests, validating required fields, and transforming API responses.
  • No additional external dependencies are needed beyond the configured API credentials.

Troubleshooting

  • Missing Card ID: If the Card ID is not provided or invalid, the node will throw an error indicating that the Card ID is required.
  • API Errors: Errors returned from the API (e.g., card not found, permission denied) will be surfaced as error messages. Ensure the Card ID exists and the API key has sufficient permissions.
  • Network Issues: Connectivity problems may cause request failures. Verify network access and API endpoint availability.
  • Continue On Fail: If enabled, the node will continue processing other items even if blocking one card fails, returning error details in the output.

Links and References


This summary focuses exclusively on the "Block Card" operation of the "Card" resource as requested.

Discussion