FAQs

Q: What are Issuer group, issuer plan and Card product?

Each merchant may be associated with multiple issuer plans. Typically, a single entity holds one issuer plan, and each issuer plan can be linked to multiple card products.

Issuer group	Issuer plan	Card product
The main entity as the users of our service	An Issuer Plan serves as a namespace, enabling you to act as a card issuing service for your own merchants or subsidiaries	a Card Product refers to a configured card program within certain bin range that define a particular card type for the end user.

Q: Should I create unique issuer plan for each of my onboarded client?

It’s up to you. You can treat each company that you onboard to have its own issuer plan. This way you are able to have fine grain control over what card product is offered to different client. You can also only have one issuing plan and each company will be differentiated in the customer level.

Q: Will StraitsX pre-configure the card product for me? Or will I be the one to create card product?

StraitsX will configure the card product for you. We'll share with you the details so that you can explore our sandbox api.

Q: What is "Create Now, Print Later"?

It is a feature StraitsX developed, once the feature enabled, a user can use the physical card as a digital card until it got requested for printing.

Currently, only StraitsX can toggle this feature.

Q: If I have "Create Now, Print Later" feature activated, how should I prevent Card Present transactions before they have received their physical card?

You can toggle Card Present Transaction off here

Q: What type of cards does StraitsX provide?

We support both virtual and physical card.

Virtual Card:

It can be create and activate the card directly without requesting card printing.

Even if the card is stored as a physical type in the system, it can still be used as a virtual card for online or digital transactions.
Physical Card:

If you wish to obtain a physical copy need to call the request-card-for-printing API after card creation to request the physical card to be printed and delivered.

Q: I want to style the iframe for display full PAN and setting PIN, what should I do? Also, may I use plain text to display the setting PIN?

Please request for the template code, we shall share it with you in our integration slack channel. Once you receive it, you will be required to make modification and share the updated code back to us. We will then deploy it to staging to confirm your changes.

As for the PIN display when setting, according to PCI-DSS policy, since it's part of the cardholder sensitive data, the PIN should not be visible when entered, which means it's should be masked.

Q: For create card, what's the difference between cardholder_name and the [first_name, second_name, surname]?

cardholder_name is the name that prints on the card.
cardholder_surname/cardholder_first_name is used in the card's magnetic stripe track 2 data.
cardholder_second_name will be saved into the database.

Both cardholder_name and the combination of cardholder_surname/cardholder_first_name need to fulfill a minimum character of 2 and a maximum character of 26.
You can apply validation on your side if you want to make sure cardholder_name and first_name + second_name + surname as the same value.
There is no constraint on cardholder_name needs to be equal to first_name + second_name + surname.
If the full name is more than 26 characters, you need to shorten it when inputting it into the cardholder_name to fit 26 characters.

Q: Can we change embossed name after requesting card printing?

For assigned cards, there shall be no manual intervention for changing the embossed name for card printing.