Skip to content
/
Overview
Last updated

Cards

Use this section to implement the issuing and managing of debit cards for your customers.

Guides

Creation & servicing

Issue cards, generate cardholder details, and manage lifecycle events like blocking or reporting theft.

3D Secure (3DS)

Implement 3D Secure authentication for safer online transactions.

Cards Smart Agent

Implement the Solaris card fraud detection feature.

Card spending controls

Limit customer transactions based on type, amount, frequency, and more.

Credit cards

Issue and manage consumer, business, and freelancer credit cards.

Decoupled cards

Issue debit cards to consumers that are linked to an external bank account.

Encrypted PIN change

Securely change a customer's card PIN.

FX mark-up

Display mandatory information to customers for non-Euro transactions.

Prepaid cards

Issue prepaid Visa buffer cards to business customers.

Tokenization & push provisioning

Enable customers to add cards to Apple Wallet or Google Pay.

Transactions

Understand how Solaris processes and settles card transactions.

API reference

The Solaris API offers dedicated endpoints for creating and managing debit cards.

PCI compliance and sensitive information

The Solaris API does not expose PCI-relevant information. Therefore, you are not required to be PCI compliant.

However, you must not log or store sensitive data that the customer passes to the Solaris API.

Sensitive data includes:

  • Full Primary Account Number (PAN). Note: The masked PAN is not sensitive.
  • PIN
  • CVV
  • API authentication token

If sensitive data passes through your system, ensure that you do not log or store it in any way.

Warning
  • Never include sensitive data in any form (including images) in your customer support requests.
  • Never ask your customers to include sensitive data in their support requests to you.

If you receive sensitive data from a customer:

  1. Inform the customer that they should not include sensitive data in communications with you.
  2. Instruct the customer to close the affected card. They can order a new one if they wish.
  3. Delete the sensitive data from your entire system immediately.
  4. Inform Solaris about the incident as soon as the card is closed, or if the customer does not act within five days.

What to do if sensitive data is exposed

If sensitive data is exposed or logged in your solution, you must inform Solaris about the incident immediately. Solaris will provide further instructions, which will include closing the affected cards.

Previous page
Next page