FAQ's

Account management FAQ's

We are using a Remote Store of Value product, do we need utilize Banking.live's accounts API's?

As you're on a Remote Store of Value product i.e. you're holding the balances and taking the final approve/decline decision, then you shouldn't need to use any of the API endpoints related to accounts.

Card issuance FAQ's

Can I migrate from my existing Issuer Processor?

You most certainly can! Paymentology has a multitude of experience in migration projects. If you are considering doing this, you can get in touch with our Sales Team here.

Can I customize the embossed name on a card?

You can set the name to be printed on the card using the optional emboss_name field in the Create card V2 API endpoint.

The name used is then pulled to the embossing file that's sent to your card manufacturer. You can read more on the embossing file's specification here.

How soon after I receive a successful response when creating a card is it created?

Once you receive a successful response when calling the Create card V2 API endpoint:

• Virtual cards are created instantly
• Physcial card definitions are created instantly and added to the embossing file that's sent to your card manufacturer. You will discuss with our Implementation Team dueing onboarding the frequency of sending embossing files to the card manufacturer.

Card management FAQ's

Can I view the PAN?

• For clients that are not PCI compliant, you can use the PaySecure API Get PAN V2 endpoint.
• For clients that are PCI compliant, you can use the Get PAN number endpoint.

The PAN is not accessible in Banking.Live in any other way, expecially not in PayControl.

Is there a User Interface for Banking.Live where cards can be managed?

You can view and manage multiple components of your card program via PayControl. You can read more on PayControl here.

For everything else, you can discuss with our Implementation Team during onboarding, your Client Executive once live or by raising a request on our Customer Support platform.

How do I manage cards in my card program?

Paymentology's API provides a flexible way to interface to Banking.Live to manage the cards in your program.

You can also utilize PayControl for certain functions.

You'll find guides on what you need to manage on this Developer Portal.

Does Banking.live or Paymentology issue cardholder statements?

No. Banking.Live offers data via multiple means to assist our clients in compiling and issuing their cardholder statements.

For clients using our Local Store of Value: Credit product, we provide you with the Credit statement file.

You can read more on these here.

How to FAQ's

Does Banking.live offer multi-currency card programs?

You can read more on how Banking.Live enables multi-currency on card products here.

Tokenization FAQ's

🗒️

Tokenization FAQ's are in relation to clients using Paymentology's tokenization services.

Where the cardholder name is sent, does Banking.live perform any name check?

No name checks are performed.

Are there any additional tokenization flows or documentation I should look at?

You can check out MeaWallet's developer documentation here.

Is there a link between ABU function and MDES i.e. PAN to token mapping on scheme side?

PAN updates will be included in the ABU report. These are updates to the fPAN after digitization.

Is there a separate SLA form payment auths or is it one and the same?

The SLA will be the same.

Does Banking.live ever decline an auth on our behalf based on any conditions of the FPAN card e.g. state, expiry etc.?

The auth will be declined in the following scenarios:

• Card status, expiry date or CVC is invalid.
• Velocity rule – 30 min. (default setting): Cardholder enters CVV incorrectly 5 times getting an “Invalid card” message each attempt – as currently from 6 attempt and onwards, cardholder is unable to provision their card for 30 minutes irrespective of whether they enter the correct/incorrect CVV, they receive a message “Card not Added” after each attempt.
  After the 30 minutes timeframe, cardholder is able to provision their card if correct CVV is implemented.

How do I identify that a token was used in a transaction?

You can identify this based on indicators in the FAST message sent to you. These indicators form part of the **ISO** node of the FAST message:

• DE48_26 : Wallet Program Data (e.g. 103 indicates Apple, 216 indicates Google).
• DE48_33_02: contains the DPAN used.