Product Hangout: Cards

Please prepare your Admin Dashboard and Cards Cheatsheet to do this post test

Link to the cheatsheet: https://docs.google.com/spreadsheets/d/1b1oqDyTEfB36acUqjrgnKoO01FjpplDGA57dTgH0VoY/edit#gid=0

If you're ready, just type anything for the response and go to the next question

Good luck on the post test~

What parameter should CS look into, to check the reason of a failed cards transaction?

• failure_reason_details inside eye payload

• failure reason outside eye payload (when you hover on the exclamation point button)

• failure_reason inside the eye payload

• failure_reason in the API response

What parameter should CS look into, to check the specific reason behind Xenshield's blocking?

• is_blocked_by_fraud?

• fds_decision_context

• risk_factor

• processor_response

What parameter should CS look into, to check the specific reason behind failed cards transaction (NOT due to Xenshield's blocking)?

• processor_response

• failure_reason

• risk_factor

• eci

Merchant claimed that they encountered an issue during 3DS authentication as per image, how can CS validate whether the authentication request was indeed failed via AD?

• Ask for the charge ID and check in Cards tab (charge section)

• Ask for the charge ID and check in Cards tab (token section)

• Ask for the masked card number and check in Cards tab (token section)

• Ask for the masked card number and check in Cards tab (charge section)

[Open Your Admin Dashboard & Cards cheatsheet] Check what is the next step for this failed transaction (Charge ID 655307d736690b001611ea72)

• Allow the card from their dashboard by clicking the 3 dots button

• Advise them to contact the issuing bank to check / resolve the issue from their side

• Advise them to use other PG

• Ask for their use case and escalate it to #cc-settings-request so the Xenshield rules can be removed.

[Open Your Admin Dashboard & Cards cheatsheet] Check what is the specific reason behind this failed transaction (Charge ID 6555e23536690b0016138030)

• Security violation

• Expired card

• Processor error

• Blocked by Xenshield as they have used too many different cards on the same IP in a day

What CS needs to provide when we're advising merchant to suggest their user to contact their issuing bank directly to check on a certain issue?

• RRN and Xendit reference ID

• RRN and Payment network transaction ID

• RRN and Charge ID

• Masked card number and Xendit reference ID

When there is a case where the transaction failed due to INVALID CVV, and the user claimed that their balance / credit limit was deducted, what CS needs to do next?

• Escalate the ticket to L2

• Tell merchants that the transaction was failed due to INVALID CVV and it should not deduct cardholder balance / credit limit. If there's a deduction, cardholder needs to check/resolve the issue with their issuing bank

What is NOT the characteristic of a Virtual Credit Card (VCC)?

• No 3DS performed

• Can be used only once

• Has low acceptance rate

• Has limited amount