#D: P#ym#nt #PI V3

What Payments API solution (type) that is suitable for merchant that has a use case where their end user do one-time payment for their service?

• PAY
• PAY AND SAVE
• REUSABLE PAYMENT CODE
• SAVE

What should merchant pay attention to before they're calling payments API v3 endpoint?

• Type of request
• Request endpoint
• Channel code and channel properties
• Payment session ID

Merchant receives a url of channel hosted page in the response after creating a payment request, and redirect their end user to that url so end user can proceed to pay. What kind of action type is that?

• PRESENT_TO_CUSTOMER
• NO ACTION
• REDIRECT_CUSTOMER
• REUSABLE_PAYMENT_CODE

What Payments API solution (type) that is suitable for merchant that has a use case where their end user can pay to the same Virtual Account or QR Code multiple times for their services?

• PAY
• PAY AND SAVE
• REUSABLE PAYMENT CODE
• PAY WITH TOKEN

What id would merchant get when they receive successful payment confirmation webhook after creating payment request with PAY AND SAVE type?

• Payment request id
• Payment token id
• Payment request id and payment token id
• Payment request id, payment token id, and payment id

What id would merchant get when they receive successful linking confirmation webhook after creating request with SAVE type?

• Payment request id
• Payment token id
• Payment request id and payment token id
• Payment request id, payment token id, and payment id

Merchant receives a "payment code" in the response after creating a payment request, and present the code so the end user can proceed to pay. What kind of action type is that?

• PRESENT_TO_CUSTOMER
• NO ACTION
• REDIRECT_CUSTOMER
• REUSABLE_PAYMENT_CODE

What id needs to be submitted when merchant wants to collect card information with card session js?

• Payment request id
• Payment session id
• Payment token id
• Payment token id and payment session id

What Payments API solution (type) that is suitable for merchant that has a use case where they allow end user to save payment information for future use separately in their platform?

• PAY
• PAY AND SAVE
• REUSABLE PAYMENT CODE
• SAVE

What is the recommended way for merchant to collect cards payment where end user already save their card information before?

• Use v3/payment_request endpoint, input PAY as the type, and input payment token in the request
• Create payment session with PAY as the type, and input payment token. Then use card session JS to collect CVN