After initializing a 3-D Secure transaction with POST /moneyins/card/direct/3dinit, you can choose not to debit the card, and only check if the user has successfully authenticated.
This is not a payment.
You can not use both POST /moneyins/card/direct/{transactionid}/3dauthenticate and PUT /moneyins/card/direct/{transactionid}/3dconfirm
- If you only want to check if the user was correctly authenticated use POST /moneyins/card/direct/{transactionid}/3dauthenticate)
- If you want to receive the payment using 3-DS use PUT /moneyins/card/direct/{transactionid}/3dconfirm
A typical use-case: you want to allow your user to save a card for rebills (RegisterCard), but first, you want to make sure that the card belongs to the user and that the user can authenticate successfully.
Authentication‑Only (No Debit) After 3‑D Secure Initialization
-
Initialize 3‑D Secure
Call:POST /moneyins/card/direct/3dinitThis returns an Authentication URL and a Transaction Id, but does not debit the card.
-
Check Authentication (No Charge)
-
To simply verify that the user can complete 3‑D Secure (and that the card belongs to them), call:
POST /moneyins/card/direct/{transactionId}/3dauthenticate -
Note: This step is not a payment—it only confirms successful authentication.
-
-
Confirm Payment (With Charge)
-
If, instead, you want to complete the payment, call:
PUT /moneyins/card/direct/{transactionId}/3dconfirm -
Important: You must not call both endpoints. Use 3dauthenticate for authentication‑only checks, or 3dconfirm to finalize the payment—never both.
-
Typical Use Case
-
You want to register a card for future rebills (
registerCard=true) but first ensure the card really belongs to the user and that they can authenticate successfully. -
Flow:
- 3dinit ➔ get Authentication URL & Transaction Id
- 3dauthenticate ➔ verify access (no funds debited)
- Save the card for later rebills with confidence that authentication will succeed.