Categorii: Tot - challenge - payment - risk - verification

realizată de jevinna senjaya 2 ani în urmă

143

Lazada Card

The process for handling payments involves multiple steps, including risk assessment and verification methods such as 3DS and PIN. When a user initiates a payment, the system checks various configurations and routes the request accordingly.

Lazada Card

pay cc dc - Parama Ilegal pay balance/coupon - no risk challange

requestId={acquirementId} scenario = 3DS status = INIT

payquery with method = payquery
verify 3ds

payquery with method = redirectCallback

uniqidentifier={acquirementId} scenario = 3DS status = INIT

after get s07 from fluxnet

pay balance coupon cc dc

no risk url, cc dc always MOTO !!

Lazada Card

Gray Test

Component Test

user get pin and 3DS
1. agreementPay Merchant -> get riskUrl PIN 2. h5 open riskURL PIN 3. mobile / h5 send agreementPay with securityId 4. acquiring will return riskURL with verificationMethod = 3DS 5. acquiring wait for payResultDTO (s07/s08)
check agreementPayWithRiskSchemaConfig
first priority is request, if request null / didn't send supportRiskChallange, check whitelist

dataItem: AgreementPayWithRiskSchemaConfig

if merchant exist in agreementPayWithRiskSchemaConfig but request supportRiskChallange on request is false

no risk url

risk challange failed PIN / s08 from fluxnet
idt_user_biz_order

isFilter = 1

aqc_ext

RISK_SCHEMA_INFO

status will success

order query will compose closeReason

pin close reason pay timeout

expired

cc/dc close reason pay_receipt_fail

order will close

Bussiness Scenario

AgreementPay
1. RegisterUser 2. Binding User - oauth, access token, get OTT 3. Binding card 4. AgreementPay for get URL 5. Challange 3ds / PIN 6. if PIN (get securityId from aphome) 3ds ( get S07 from ifcfluxnet) 7. check order query 8. check database

SNAP

APIGEE

requestId={acquirementId} scenario / type = PASSWORD status: INIT

ifcsupergw

additionalInfo.supportRiskChallange

pay cc / dc

pay balance / coupon

risk url PIN

dbCheck: aqc_ext - RISK_SCHEMA_INFO

uniqidentifier={acquirementId} scenario / type = PASSWORD status: INIT SecurityId

after hit agreementPay with securityId

order query has response "supportRiskChallange"

order pay success

status risk will be success

OPEN API - MOBILE BTS

new request on agreementPay

autoRouting

set balance not enough

user support autorouting merchant support autorouting supportRiskChallenge=false

no risk challange

user support autorouting merchant support autorouting supportRiskChallenge=true

routing to CC / DC will get risk url for 3ds

supportRiskChallange

null

false

true

pay with cc / dc

put PaymentPreference on agreementPay request payOptionBills.cardCacheToken !=null

risk url for 3ds

pay with balance / coupon

non lazada

get risk challange PIN

dbcheck: aqc_ext -RISK_SCHEMA_INFO

uniqidentifier={acquirementId} scenario = PASSWORD status = INIT securityId :

didn't get any risk

agreementPay normal