You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the following callback objects provided by Xendit to receive callbacks (also known as webhooks) that Xendit sends you on events, such as successful payments. Note that the example is meant to illustrate the contents of the callback object -- you will not need to instantiate these objects in practice
Copy file name to clipboardexpand all lines: docs/payment_method/CardChannelProperties.md
+1
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ Card Channel Properties
10
10
|**successReturnUrl**|string || URL where the end-customer is redirected if the authorization is successful |||
11
11
|**failureReturnUrl**|string || URL where the end-customer is redirected if the authorization failed |||
12
12
|**cardonfileType**|string || Type of “credential-on-file” / “card-on-file” payment being made. Indicate that this payment uses a previously linked Payment Method for charging. |||
Copy file name to clipboardexpand all lines: docs/payment_method/EWalletChannelProperties.md
+1
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ EWallet Channel Properties
9
9
|**successReturnUrl**|string || URL where the end-customer is redirected if the authorization is successful |||
10
10
|**failureReturnUrl**|string || URL where the end-customer is redirected if the authorization failed |||
11
11
|**cancelReturnUrl**|string || URL where the end-customer is redirected if the authorization cancelled |||
12
+
|**pendingReturnUrl**|string || URL where the end-customer is redirected if the authorization is pending |||
12
13
|**mobileNumber**|string || Mobile number of customer in E.164 format (e.g. +628123123123). For OVO one time payment use only. |||
13
14
|**redeemPoints**|string || REDEEM_NONE will not use any point, REDEEM_ALL will use all available points before cash balance is used. For OVO and ShopeePay tokenized payment use only. |||
14
15
|**cashtag**|string || Available for JENIUSPAY only |||
|**maskedCardNumber**|string |☑️| 1st 6 and last 4 digits of the card |||
9
+
|**tokenId**|string |||||
10
+
|**maskedCardNumber**|string || 1st 6 and last 4 digits of the card |||
11
11
|**cardholderName**|string || Cardholder name is optional but recommended for 3DS 2 / AVS verification |||
12
-
|**expiryMonth**|string | ☑️ | Card expiry month in MM format |||
13
-
|**expiryYear**|string | ☑️ | Card expiry month in YY format |||
14
-
|**fingerprint**|string | ☑️ | Xendit-generated identifier for the unique card number. Multiple payment method objects can be created for the same account - e.g. if the user first creates a one-time payment request, and then later on creates a multiple-use payment method using the same account. The fingerprint helps to identify the unique account being used. |||
15
-
|**type**|string | ☑️ | Whether the card is a credit or debit card |||
|**country**|string | ☑️ | Country where the card was issued ISO 3166-1 Alpha-2 |||
18
-
|**issuer**|string | ☑️ | Issuer of the card, most often an issuing bank For example, “BCA”, “MANDIRI” |||
12
+
|**expiryMonth**|string || Card expiry month in MM format |||
13
+
|**expiryYear**|string || Card expiry month in YY format |||
14
+
|**fingerprint**|string || Xendit-generated identifier for the unique card number. Multiple payment method objects can be created for the same account - e.g. if the user first creates a one-time payment request, and then later on creates a multiple-use payment method using the same account. The fingerprint helps to identify the unique account being used. |||
15
+
|**type**|string || Whether the card is a credit or debit card |||
Copy file name to clipboardexpand all lines: docs/payment_request/CardChannelProperties.md
+1
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ Card Channel Properties
11
11
|**failureReturnUrl**|string || URL where the end-customer is redirected if the authorization failed |||
12
12
|**cardonfileType**|string || Type of “credential-on-file” / “card-on-file” payment being made. Indicate that this payment uses a previously linked Payment Method for charging. |||
13
13
|**merchantIdTag**|string || Tag for a Merchant ID that you want to associate this payment with. For merchants using their own MIDs to specify which MID they want to use |||
0 commit comments