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 operations related to loyalty cards. The "Transfer Amount" operation under the "Card" resource allows transferring a monetary amount from one card to another within the system.

This operation is useful in scenarios where funds or balances need to be moved between customer cards, such as refunding a purchase to a different card, consolidating balances, or transferring credits between users.

Example use cases:

  • Transferring gift card balance from one card to another.
  • Moving prepaid amounts between loyalty cards of the same customer.
  • Adjusting balances during customer account merges.

Properties

Name Meaning
From Card ID The unique identifier of the card from which the amount will be transferred (source).
To Card ID The unique identifier of the card to which the amount will be transferred (destination).

Note: Although your provided properties JSON only includes these two fields, the actual code snippet does not explicitly show the implementation for "transferAmount" operation details. However, based on naming and typical usage, these are the required inputs.

Output

The output JSON structure after executing the transfer operation typically contains the API response transformed into a simplified object format. This usually includes confirmation of the transfer, updated card balances, transaction IDs, timestamps, or error messages if any.

Since the exact response structure for "transferAmount" is not detailed in the source, expect a JSON object confirming success or failure of the transfer along with relevant transaction details.

No binary data output is indicated for 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 fields, and transforming responses.
  • No additional external dependencies beyond the configured API credentials and network access to the service.

Troubleshooting

  • Missing Required Fields: If either "From Card ID" or "To Card ID" is missing, the node will throw an error indicating required fields are not provided.
  • Invalid Card IDs: Providing invalid or non-existent card IDs may result in API errors; verify card IDs before running the operation.
  • Insufficient Balance: Attempting to transfer an amount greater than the source card's balance may cause the API to reject the request.
  • API Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Network Issues: Connectivity problems to the API endpoint will cause failures; check network and firewall settings.
  • Error Messages: The node returns error messages from the API in the output JSON under an error flag, helping diagnose issues.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion