Wallet Cards & Templates

Overall Managing Process

The following image illustrates the process of managing wallet cards:



Create Wallet Cards (Draft status)

Partners can create and manage their wallet cards with this step-by-step guide.

Manage Wallet Cards


  • You can manage all registered wallet cards.
  • You can edit wallet cards and check their status.

General Information

The General Information page allows the partner to enter administrative details to manage their cards, as well as to define common parameters for the wallet.

Item

Description

Testing mode

All data generated in Testing mode is periodically deleted.
Be sure to turn off the "Testing mode" setting after the test is over.

Wallet Card name

Representative title of the wallet card

Wallet Card ID

Unique wallet card domain name

Partner app package name

Partner application package name

Wallet Card Template

Pre-defined partner wallet card template

Partner Get card data

URL for the partner API call to receive card data.
If the partner uses this API, enter the URL. Otherwise leave it blank.

Partner Send card state

URL for the partner API call to send a card state notification.
If the partner uses this API, enter the URL. Otherwise leave it blank.

Samsung Server IPs

Samsung Wallet Server IPs which need to be allowed by the partner’s firewall, separately described for inbound and outbound

Wearable Wallet assistance

Whether to support the Wearable Wallet service

Support ‘No Network’ status

Whether to support wallet card opening during the ‘No Network’ status

Description

Description of the wallet card

Select Template

You can choose from various types of wallet card templates optimized for partners such as boarding pass, ticket, coupon, and digital ID. You can select the type of wallet card from the Select Wallet Card Template pop-up window. First, select the one you want in the Wallet Card Type drop-down menu and then click Wallet Card Sub Type to select one of the templates belonging to the card type.

  • Wallet card type: Boarding pass


  • Wallet card type: Tickets


  • Wallet card type: Coupons


  • Wallet card type: Digital ID


  • Wallet card type: Gift card


  • Wallet card type: Loyalty (Membership)


View Wallet Card

You can view all registered information for a wallet card, as well as edit and delete it.



Launch Wallet Cards (Verifying status)

You can launch and activate cards, at which point they move to verification.




  • You can activate a card by clicking the "Launch" button.
  • Once a card is launched, the button text changes to 'Launched'. The activation cannot be canceled.
  • When a card is launched, its status changes to 'Verifying', and then to ‘Active’ after administrator approval.

Launch Wallet Cards (Rejected status)

If the wallet card is rejected after launching, you can modify the card and re-launch.




  • The administrator registers the reason for rejection when rejecting the launched wallet card.
  • It is sent to the partner by email from the system, including the reason for rejection.
  • Partners can apply for launch again by checking the reason for rejection and modifying the wallet card information.

Testing Mode

You can test a card internally to make sure everything works before you officially expose it to users.


  • By default, the ‘Testing mode’ option is enabled.
  • All data generated in testing mode is periodically deleted.
  • Card exposure is not affected even when the testing mode is enabled.
  • Be sure to turn off the testing mode after the test is over. (Testing mode ON → Testing mode Off)

Admin Approval (Active status)

All launched cards are activated after the administrator's approval.

  • When a card is launched, its status changes to 'Verifying' and then to 'Active' after administrator approval.
  • When the card is activated, it is made visible to the user.


"Add To Wallet" Integration

For Wallet integration, you need to insert an "Add to Wallet" script to your system. The "Add to Wallet" script is available for Web, Android, and Email/MMS. Each system has different script composition. To implement an "Add to Wallet" button, follow the procedure below:

  1. Create the tokenized card data (Cdata). Card data is the actual content data of wallet card and it has several formats based on the card type. Refer to CData Generation Sample Code for details.
  2. Copy the sample "Add to Wallet" script from the Partners Portal’s Wallet Card page and replace "cdata" with the data token created above.
  3. Apply the script to your system. See Partners Portal’s Wallet Card and Android Integration Sample Code for details.

Below is the "Add to Wallet" script guide in the Partners Portal.

For "Add to Wallet" integration, you may need some base data. You can find that and other necessary information on Partners Portal and Wallet API Spec. You can also add image beacon in the script for tracking effect analysis.

Merchant Push Notification

Partners can create a Message template for sending pushes on each of their Wallet cards.

Type

  • Partners can only choose the Merchant Push type.

Message Type

  • You can choose a Message Type from marketing or others.

Rejected Comment

  • If the merchant push notification is rejected after request approval, you can modify the Message Template.
  • The administrator registers the reason for rejection when rejecting the merchant push notification
  • It is sent to the partner by email from the system, including the reason for rejection.
  • Partners can request for approval again by checking the reason for rejection and modifying the Message Template.

Approved Date

  • Displays the date and time when the push message is approved by the administrator.

Message Template

  • You can create the contents of the push, and it is also possible to put the available variables in '{{}}'
  • After configuring the content, click Harmfulness Verification to verify whether there is a harmful expression in the content.
  • The verified result is displayed as Pass or Fail, and if it is Fail, it shows the filtered harmful expression together.
  • Even if the verified result is Fail, an approval request can be made, but it can be rejected by the administrator.
  • If a different language is added to the default language in General Information, the Message Template must also be entered for each added language.

Request Approval Button

  • After completing the Message Template, click this button to send an e-mail requesting approval to the administrator.