@payfurl/client 4.10.0 → 4.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +54 -0
- package/README.md +54 -0
- package/dist/sdk/{CloseIcon-B65NDIbM.js → CloseIcon-Ejad61tT.js} +377 -363
- package/dist/sdk/{DefaultThreeDsProvider-CzqbXEws.js → DefaultThreeDsProvider-bLoDSnkd.js} +24 -24
- package/dist/sdk/{MetricsGlobalThreeDsProvider-B-EQQsEV.js → MetricsGlobalThreeDsProvider-C93ttqbB.js} +16 -16
- package/dist/sdk/{PayWayAppleButton-C-XfcgNS.js → PayWayAppleButton-BzAwlGS-.js} +1 -1
- package/dist/sdk/{alerts-BvNnAm_q.js → alerts-1YSRy5iI.js} +9 -9
- package/dist/sdk/{cxpay-VbaQA3_P.js → cxpay-DblHb5vN.js} +1 -1
- package/dist/sdk/{default-Diji0SXY.js → default-C7f86Fx-.js} +1 -1
- package/dist/sdk/{ecentric-BlNDCZo_.js → ecentric-B3UohyO_.js} +11 -11
- package/dist/sdk/{epna-CxmJ_mqR.js → epna-DwUg2IlB.js} +1 -1
- package/dist/sdk/{flashbanc-BAxvqtBB.js → flashbanc-LXs8bahL.js} +1 -1
- package/dist/sdk/forter-CLFaJUYa.js +30 -0
- package/dist/sdk/{gpayments-B5KWQV4S.js → gpayments-DoZug3PV.js} +13 -13
- package/dist/sdk/{metrics_global-HMMDzPlb.js → metrics_global-BM-ooge-.js} +1 -1
- package/dist/sdk/{nmi-Ch7qQ6Av.js → nmi-BA3ZTdQa.js} +1 -1
- package/dist/sdk/{nuvei-DRmlfpTL.js → nuvei-DIWsLlLz.js} +29 -29
- package/dist/sdk/{payabli-CiBJ1-vC.js → payabli-DgrTI1Et.js} +1 -1
- package/dist/sdk/payfurl.d.ts +18 -1
- package/dist/sdk/payfurl.es.js +1117 -830
- package/dist/sdk/payfurl.umd.js +8 -8
- package/dist/sdk/{payglocal-uAPlijwL.js → payglocal-ezp0MsaZ.js} +18 -18
- package/dist/sdk/{payway_rest-CjgIP42z.js → payway_rest-D8-T-ULx.js} +1 -1
- package/dist/sdk/{skybank-D7uRF17E.js → skybank-BgDLlFXX.js} +1 -1
- package/dist/sdk/{strings-BthDdeA6.js → strings-Dp6oE-U1.js} +13 -13
- package/dist/sdk/style.css +1 -1
- package/dist/sdk/whenRendered-jR4Jls4M.js +12 -0
- package/package.json +1 -1
- package/dist/sdk/forter-R2alfHeE.js +0 -26
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,60 @@ version 4.9.3.
|
|
|
6
6
|
|
|
7
7
|
## Unreleased
|
|
8
8
|
|
|
9
|
+
## 4.11.0 (2026-11-06)
|
|
10
|
+
|
|
11
|
+
### Added
|
|
12
|
+
|
|
13
|
+
- `isApplePayAvailable()` returns a promise of whether the shopper's browser can pay with Apple Pay:
|
|
14
|
+
the same check `addApplePay()` and `addDropIn()` use to decide whether to show the Apple Pay button.
|
|
15
|
+
- `onPaymentMethodStatus()` tells you when a Google Pay, Apple Pay, PayPal, PayTo, checkout (such as
|
|
16
|
+
PayID or Zip) or UPI button or form has rendered, or that it won't and why: no provider for it on your
|
|
17
|
+
account, not supported in the shopper's browser, or an error, such as a checkout that couldn't be
|
|
18
|
+
created or invalid PayTo options. Before, these showed on the page only, or nowhere.
|
|
19
|
+
- `onThreeDsProgress()` tells you when 3-D Secure starts, when the shopper is shown a challenge, and
|
|
20
|
+
when it completes, successfully or not.
|
|
21
|
+
- `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.5.0: `PayfurlDropin` takes `onPaymentMethodStatus`
|
|
22
|
+
and `onThreeDsProgress` (in Vue, the `@onPaymentMethodStatus` and `@onThreeDsProgress` events), and
|
|
23
|
+
`customer`, `billingAddress` and `order` props, which it could not receive before. Its Vue events are
|
|
24
|
+
typed. They need this version of `@payfurl/client` or later.
|
|
25
|
+
- You can call `setCustomerInfo()` after `addCard()` or `addDropIn()`, for example when the shopper
|
|
26
|
+
changes their email: the new email is used for 3-D Secure, and the card form hides its own Email field
|
|
27
|
+
once it has a valid one. The same email now also reaches the fraud check and the card token.
|
|
28
|
+
`setCustomerInfo()` is now the preferred way to pass the shopper's email; `threeDSEmail` still works and
|
|
29
|
+
is used when `setCustomerInfo()` has no email.
|
|
30
|
+
|
|
31
|
+
### Changed
|
|
32
|
+
|
|
33
|
+
- If your code reads `onFailure`'s `error` text to detect a 3-D Secure failure, read
|
|
34
|
+
`errorDetails.reason` instead. When 3-D Secure fails, the card form and `onFailure`'s `error` now say
|
|
35
|
+
"Your bank couldn't verify this card. Please try again or use a different card." in place of a technical
|
|
36
|
+
message such as "3D Secure failed", which is now in `errorDetails.reason`.
|
|
37
|
+
- For PayPal, `onLoaded` is now called once the PayPal buttons have rendered, rather than when they
|
|
38
|
+
were requested, and not at all if they fail to render.
|
|
39
|
+
|
|
40
|
+
### Fixed
|
|
41
|
+
|
|
42
|
+
- A shopper known to Click to Pay gets one passcode per checkout, not one each time your page calls
|
|
43
|
+
`setCustomerInfo()`. Click to Pay looks the shopper up again only when their email or phone changes to one not
|
|
44
|
+
yet looked up, a second after the last change; a call without an email keeps the email it had. The passcode is
|
|
45
|
+
sent only once the card form is on screen. Details set before `addCard()` or
|
|
46
|
+
`addCardLeastCost()` start Click to Pay no longer start it early (`preloadClickToPay()` still loads it ahead).
|
|
47
|
+
- The card form no longer grows to a large blank area while 3-D Secure runs: it keeps its height, with
|
|
48
|
+
the loading spinner, until a challenge actually appears, and does not grow at all when the card passes
|
|
49
|
+
without one.
|
|
50
|
+
- The card form's Email field, a PayTo PayID email and Click to Pay sign-in now accept email addresses
|
|
51
|
+
whose domain ends in more than three letters, such as `shopper@example.online`.
|
|
52
|
+
- PayTo now calls your failure handler when the agreement can't be created from what the shopper
|
|
53
|
+
entered ("Invalid payment details", with `errorDetails` when available), and checkout providers and
|
|
54
|
+
UPI when the payment fails after the shopper opened the provider's page ("Checkout has been
|
|
55
|
+
cancelled"). Before, these errors only showed on the page.
|
|
56
|
+
- In TypeScript, `providerId` and `options` of `addApplePay()` are now optional, as documented.
|
|
57
|
+
- In the Drop In UI, `allowedPaymentTypes: ['payglocal']` now shows PayGLocal. It used to need `'zip'`,
|
|
58
|
+
which also showed Zip.
|
|
59
|
+
- Adding Google Pay or PayPal again after its script failed to load now loads it again.
|
|
60
|
+
- A checkout payment (such as PayID or Zip) no longer calls your success handler twice, or your failure
|
|
61
|
+
handler after your success handler, when payFURL's status check answers slowly.
|
|
62
|
+
|
|
9
63
|
## 4.10.0 (2026-11-04)
|
|
10
64
|
|
|
11
65
|
### Added
|
package/README.md
CHANGED
|
@@ -103,6 +103,60 @@ script on `assets.payfurl.com` share version numbers, so this covers both. The c
|
|
|
103
103
|
version 4.9.3.
|
|
104
104
|
|
|
105
105
|
|
|
106
|
+
### 4.11.0 (2026-11-06)
|
|
107
|
+
|
|
108
|
+
#### Added
|
|
109
|
+
|
|
110
|
+
- `isApplePayAvailable()` returns a promise of whether the shopper's browser can pay with Apple Pay:
|
|
111
|
+
the same check `addApplePay()` and `addDropIn()` use to decide whether to show the Apple Pay button.
|
|
112
|
+
- `onPaymentMethodStatus()` tells you when a Google Pay, Apple Pay, PayPal, PayTo, checkout (such as
|
|
113
|
+
PayID or Zip) or UPI button or form has rendered, or that it won't and why: no provider for it on your
|
|
114
|
+
account, not supported in the shopper's browser, or an error, such as a checkout that couldn't be
|
|
115
|
+
created or invalid PayTo options. Before, these showed on the page only, or nowhere.
|
|
116
|
+
- `onThreeDsProgress()` tells you when 3-D Secure starts, when the shopper is shown a challenge, and
|
|
117
|
+
when it completes, successfully or not.
|
|
118
|
+
- `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.5.0: `PayfurlDropin` takes `onPaymentMethodStatus`
|
|
119
|
+
and `onThreeDsProgress` (in Vue, the `@onPaymentMethodStatus` and `@onThreeDsProgress` events), and
|
|
120
|
+
`customer`, `billingAddress` and `order` props, which it could not receive before. Its Vue events are
|
|
121
|
+
typed. They need this version of `@payfurl/client` or later.
|
|
122
|
+
- You can call `setCustomerInfo()` after `addCard()` or `addDropIn()`, for example when the shopper
|
|
123
|
+
changes their email: the new email is used for 3-D Secure, and the card form hides its own Email field
|
|
124
|
+
once it has a valid one. The same email now also reaches the fraud check and the card token.
|
|
125
|
+
`setCustomerInfo()` is now the preferred way to pass the shopper's email; `threeDSEmail` still works and
|
|
126
|
+
is used when `setCustomerInfo()` has no email.
|
|
127
|
+
|
|
128
|
+
#### Changed
|
|
129
|
+
|
|
130
|
+
- If your code reads `onFailure`'s `error` text to detect a 3-D Secure failure, read
|
|
131
|
+
`errorDetails.reason` instead. When 3-D Secure fails, the card form and `onFailure`'s `error` now say
|
|
132
|
+
"Your bank couldn't verify this card. Please try again or use a different card." in place of a technical
|
|
133
|
+
message such as "3D Secure failed", which is now in `errorDetails.reason`.
|
|
134
|
+
- For PayPal, `onLoaded` is now called once the PayPal buttons have rendered, rather than when they
|
|
135
|
+
were requested, and not at all if they fail to render.
|
|
136
|
+
|
|
137
|
+
#### Fixed
|
|
138
|
+
|
|
139
|
+
- A shopper known to Click to Pay gets one passcode per checkout, not one each time your page calls
|
|
140
|
+
`setCustomerInfo()`. Click to Pay looks the shopper up again only when their email or phone changes to one not
|
|
141
|
+
yet looked up, a second after the last change; a call without an email keeps the email it had. The passcode is
|
|
142
|
+
sent only once the card form is on screen. Details set before `addCard()` or
|
|
143
|
+
`addCardLeastCost()` start Click to Pay no longer start it early (`preloadClickToPay()` still loads it ahead).
|
|
144
|
+
- The card form no longer grows to a large blank area while 3-D Secure runs: it keeps its height, with
|
|
145
|
+
the loading spinner, until a challenge actually appears, and does not grow at all when the card passes
|
|
146
|
+
without one.
|
|
147
|
+
- The card form's Email field, a PayTo PayID email and Click to Pay sign-in now accept email addresses
|
|
148
|
+
whose domain ends in more than three letters, such as `shopper@example.online`.
|
|
149
|
+
- PayTo now calls your failure handler when the agreement can't be created from what the shopper
|
|
150
|
+
entered ("Invalid payment details", with `errorDetails` when available), and checkout providers and
|
|
151
|
+
UPI when the payment fails after the shopper opened the provider's page ("Checkout has been
|
|
152
|
+
cancelled"). Before, these errors only showed on the page.
|
|
153
|
+
- In TypeScript, `providerId` and `options` of `addApplePay()` are now optional, as documented.
|
|
154
|
+
- In the Drop In UI, `allowedPaymentTypes: ['payglocal']` now shows PayGLocal. It used to need `'zip'`,
|
|
155
|
+
which also showed Zip.
|
|
156
|
+
- Adding Google Pay or PayPal again after its script failed to load now loads it again.
|
|
157
|
+
- A checkout payment (such as PayID or Zip) no longer calls your success handler twice, or your failure
|
|
158
|
+
handler after your success handler, when payFURL's status check answers slowly.
|
|
159
|
+
|
|
106
160
|
### 4.10.0 (2026-11-04)
|
|
107
161
|
|
|
108
162
|
#### Added
|