@payfurl/client 4.10.0 → 4.11.1

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.
Files changed (29) hide show
  1. package/CHANGELOG.md +76 -0
  2. package/README.md +76 -0
  3. package/dist/sdk/{CloseIcon-B65NDIbM.js → CloseIcon-Ejad61tT.js} +377 -363
  4. package/dist/sdk/{DefaultThreeDsProvider-CzqbXEws.js → DefaultThreeDsProvider-bLoDSnkd.js} +24 -24
  5. package/dist/sdk/{MetricsGlobalThreeDsProvider-B-EQQsEV.js → MetricsGlobalThreeDsProvider-C93ttqbB.js} +16 -16
  6. package/dist/sdk/{PayWayAppleButton-C-XfcgNS.js → PayWayAppleButton-B1Ttj4J_.js} +1 -1
  7. package/dist/sdk/{alerts-BvNnAm_q.js → alerts-1YSRy5iI.js} +9 -9
  8. package/dist/sdk/{cxpay-VbaQA3_P.js → cxpay-DblHb5vN.js} +1 -1
  9. package/dist/sdk/{default-Diji0SXY.js → default-C7f86Fx-.js} +1 -1
  10. package/dist/sdk/{ecentric-BlNDCZo_.js → ecentric-B3UohyO_.js} +11 -11
  11. package/dist/sdk/{epna-CxmJ_mqR.js → epna-DwUg2IlB.js} +1 -1
  12. package/dist/sdk/{flashbanc-BAxvqtBB.js → flashbanc-LXs8bahL.js} +1 -1
  13. package/dist/sdk/forter-CLFaJUYa.js +30 -0
  14. package/dist/sdk/{gpayments-B5KWQV4S.js → gpayments-DoZug3PV.js} +13 -13
  15. package/dist/sdk/{metrics_global-HMMDzPlb.js → metrics_global-BM-ooge-.js} +1 -1
  16. package/dist/sdk/{nmi-Ch7qQ6Av.js → nmi-BA3ZTdQa.js} +1 -1
  17. package/dist/sdk/{nuvei-DRmlfpTL.js → nuvei-DIWsLlLz.js} +29 -29
  18. package/dist/sdk/{payabli-CiBJ1-vC.js → payabli-DgrTI1Et.js} +1 -1
  19. package/dist/sdk/payfurl.d.ts +35 -3
  20. package/dist/sdk/payfurl.es.js +1121 -834
  21. package/dist/sdk/payfurl.umd.js +8 -8
  22. package/dist/sdk/{payglocal-uAPlijwL.js → payglocal-ezp0MsaZ.js} +18 -18
  23. package/dist/sdk/{payway_rest-CjgIP42z.js → payway_rest-4Pjb1c7k.js} +1 -1
  24. package/dist/sdk/{skybank-D7uRF17E.js → skybank-BgDLlFXX.js} +1 -1
  25. package/dist/sdk/{strings-BthDdeA6.js → strings-DyifLS9r.js} +13 -13
  26. package/dist/sdk/style.css +1 -1
  27. package/dist/sdk/whenRendered-jR4Jls4M.js +12 -0
  28. package/package.json +1 -1
  29. package/dist/sdk/forter-R2alfHeE.js +0 -26
package/CHANGELOG.md CHANGED
@@ -6,6 +6,82 @@ version 4.9.3.
6
6
 
7
7
  ## Unreleased
8
8
 
9
+ ## 4.11.1 (2026-11-11)
10
+
11
+ ### Added
12
+
13
+ - `paypalButtonStyle`, in `addPaypal()` and `addDropIn()`, also takes PayPal's button style as an object, such as
14
+ `{ color: 'black', shape: 'pill', label: 'pay' }`, to set the buttons' shape, label, layout and height as well as
15
+ their colour.
16
+ - `addDropIn()` takes `paypalHideShipping`, which redacts the shipping address from the PayPal site, as
17
+ `hideShipping` does in `addPaypal()`.
18
+
19
+ ### Changed
20
+
21
+ - In TypeScript, `paypalButtonStyle` is now typed as one of the colours (`gold`, `blue`, `silver`, `white`,
22
+ `black`) or a button style object, in place of any string. If you pass a variable typed `string`, type it as
23
+ `PaypalButtonColor`, exported by `@payfurl/client`.
24
+
25
+ ### Fixed
26
+
27
+ - `addDropIn()` now uses `paypalButtonStyle` and `paypalEnablePayIn4`. Before, the drop-in always showed a gold
28
+ PayPal button without Pay Later, whatever you passed.
29
+ - When PayPal rejects the button style, `onPaymentMethodStatus()` now reports PayPal as `unavailable`.
30
+
31
+ ## 4.11.0 (2026-11-06)
32
+
33
+ ### Added
34
+
35
+ - `isApplePayAvailable()` returns a promise of whether the shopper's browser can pay with Apple Pay:
36
+ the same check `addApplePay()` and `addDropIn()` use to decide whether to show the Apple Pay button.
37
+ - `onPaymentMethodStatus()` tells you when a Google Pay, Apple Pay, PayPal, PayTo, checkout (such as
38
+ PayID or Zip) or UPI button or form has rendered, or that it won't and why: no provider for it on your
39
+ account, not supported in the shopper's browser, or an error, such as a checkout that couldn't be
40
+ created or invalid PayTo options. Before, these showed on the page only, or nowhere.
41
+ - `onThreeDsProgress()` tells you when 3-D Secure starts, when the shopper is shown a challenge, and
42
+ when it completes, successfully or not.
43
+ - `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.5.0: `PayfurlDropin` takes `onPaymentMethodStatus`
44
+ and `onThreeDsProgress` (in Vue, the `@onPaymentMethodStatus` and `@onThreeDsProgress` events), and
45
+ `customer`, `billingAddress` and `order` props, which it could not receive before. Its Vue events are
46
+ typed. They need this version of `@payfurl/client` or later.
47
+ - You can call `setCustomerInfo()` after `addCard()` or `addDropIn()`, for example when the shopper
48
+ changes their email: the new email is used for 3-D Secure, and the card form hides its own Email field
49
+ once it has a valid one. The same email now also reaches the fraud check and the card token.
50
+ `setCustomerInfo()` is now the preferred way to pass the shopper's email; `threeDSEmail` still works and
51
+ is used when `setCustomerInfo()` has no email.
52
+
53
+ ### Changed
54
+
55
+ - If your code reads `onFailure`'s `error` text to detect a 3-D Secure failure, read
56
+ `errorDetails.reason` instead. When 3-D Secure fails, the card form and `onFailure`'s `error` now say
57
+ "Your bank couldn't verify this card. Please try again or use a different card." in place of a technical
58
+ message such as "3D Secure failed", which is now in `errorDetails.reason`.
59
+ - For PayPal, `onLoaded` is now called once the PayPal buttons have rendered, rather than when they
60
+ were requested, and not at all if they fail to render.
61
+
62
+ ### Fixed
63
+
64
+ - A shopper known to Click to Pay gets one passcode per checkout, not one each time your page calls
65
+ `setCustomerInfo()`. Click to Pay looks the shopper up again only when their email or phone changes to one not
66
+ yet looked up, a second after the last change; a call without an email keeps the email it had. The passcode is
67
+ sent only once the card form is on screen. Details set before `addCard()` or
68
+ `addCardLeastCost()` start Click to Pay no longer start it early (`preloadClickToPay()` still loads it ahead).
69
+ - The card form no longer grows to a large blank area while 3-D Secure runs: it keeps its height, with
70
+ the loading spinner, until a challenge actually appears, and does not grow at all when the card passes
71
+ without one.
72
+ - The card form's Email field, a PayTo PayID email and Click to Pay sign-in now accept email addresses
73
+ whose domain ends in more than three letters, such as `shopper@example.online`.
74
+ - PayTo now calls your failure handler when the agreement can't be created from what the shopper
75
+ entered ("Invalid payment details", with `errorDetails` when available), and checkout providers and
76
+ UPI when the payment fails after the shopper opened the provider's page ("Checkout has been
77
+ cancelled"). Before, these errors only showed on the page.
78
+ - In TypeScript, `providerId` and `options` of `addApplePay()` are now optional, as documented.
79
+ - In the Drop In UI, `allowedPaymentTypes: ['payglocal']` now shows PayGLocal. It used to need `'zip'`,
80
+ which also showed Zip.
81
+ - Adding Google Pay or PayPal again after its script failed to load now loads it again.
82
+ - A checkout payment (such as PayID or Zip) no longer calls your success handler twice, or your failure
83
+ handler after your success handler, when payFURL's status check answers slowly.
84
+
9
85
  ## 4.10.0 (2026-11-04)
10
86
 
11
87
  ### Added
package/README.md CHANGED
@@ -103,6 +103,82 @@ 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.1 (2026-11-11)
107
+
108
+ #### Added
109
+
110
+ - `paypalButtonStyle`, in `addPaypal()` and `addDropIn()`, also takes PayPal's button style as an object, such as
111
+ `{ color: 'black', shape: 'pill', label: 'pay' }`, to set the buttons' shape, label, layout and height as well as
112
+ their colour.
113
+ - `addDropIn()` takes `paypalHideShipping`, which redacts the shipping address from the PayPal site, as
114
+ `hideShipping` does in `addPaypal()`.
115
+
116
+ #### Changed
117
+
118
+ - In TypeScript, `paypalButtonStyle` is now typed as one of the colours (`gold`, `blue`, `silver`, `white`,
119
+ `black`) or a button style object, in place of any string. If you pass a variable typed `string`, type it as
120
+ `PaypalButtonColor`, exported by `@payfurl/client`.
121
+
122
+ #### Fixed
123
+
124
+ - `addDropIn()` now uses `paypalButtonStyle` and `paypalEnablePayIn4`. Before, the drop-in always showed a gold
125
+ PayPal button without Pay Later, whatever you passed.
126
+ - When PayPal rejects the button style, `onPaymentMethodStatus()` now reports PayPal as `unavailable`.
127
+
128
+ ### 4.11.0 (2026-11-06)
129
+
130
+ #### Added
131
+
132
+ - `isApplePayAvailable()` returns a promise of whether the shopper's browser can pay with Apple Pay:
133
+ the same check `addApplePay()` and `addDropIn()` use to decide whether to show the Apple Pay button.
134
+ - `onPaymentMethodStatus()` tells you when a Google Pay, Apple Pay, PayPal, PayTo, checkout (such as
135
+ PayID or Zip) or UPI button or form has rendered, or that it won't and why: no provider for it on your
136
+ account, not supported in the shopper's browser, or an error, such as a checkout that couldn't be
137
+ created or invalid PayTo options. Before, these showed on the page only, or nowhere.
138
+ - `onThreeDsProgress()` tells you when 3-D Secure starts, when the shopper is shown a challenge, and
139
+ when it completes, successfully or not.
140
+ - `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.5.0: `PayfurlDropin` takes `onPaymentMethodStatus`
141
+ and `onThreeDsProgress` (in Vue, the `@onPaymentMethodStatus` and `@onThreeDsProgress` events), and
142
+ `customer`, `billingAddress` and `order` props, which it could not receive before. Its Vue events are
143
+ typed. They need this version of `@payfurl/client` or later.
144
+ - You can call `setCustomerInfo()` after `addCard()` or `addDropIn()`, for example when the shopper
145
+ changes their email: the new email is used for 3-D Secure, and the card form hides its own Email field
146
+ once it has a valid one. The same email now also reaches the fraud check and the card token.
147
+ `setCustomerInfo()` is now the preferred way to pass the shopper's email; `threeDSEmail` still works and
148
+ is used when `setCustomerInfo()` has no email.
149
+
150
+ #### Changed
151
+
152
+ - If your code reads `onFailure`'s `error` text to detect a 3-D Secure failure, read
153
+ `errorDetails.reason` instead. When 3-D Secure fails, the card form and `onFailure`'s `error` now say
154
+ "Your bank couldn't verify this card. Please try again or use a different card." in place of a technical
155
+ message such as "3D Secure failed", which is now in `errorDetails.reason`.
156
+ - For PayPal, `onLoaded` is now called once the PayPal buttons have rendered, rather than when they
157
+ were requested, and not at all if they fail to render.
158
+
159
+ #### Fixed
160
+
161
+ - A shopper known to Click to Pay gets one passcode per checkout, not one each time your page calls
162
+ `setCustomerInfo()`. Click to Pay looks the shopper up again only when their email or phone changes to one not
163
+ yet looked up, a second after the last change; a call without an email keeps the email it had. The passcode is
164
+ sent only once the card form is on screen. Details set before `addCard()` or
165
+ `addCardLeastCost()` start Click to Pay no longer start it early (`preloadClickToPay()` still loads it ahead).
166
+ - The card form no longer grows to a large blank area while 3-D Secure runs: it keeps its height, with
167
+ the loading spinner, until a challenge actually appears, and does not grow at all when the card passes
168
+ without one.
169
+ - The card form's Email field, a PayTo PayID email and Click to Pay sign-in now accept email addresses
170
+ whose domain ends in more than three letters, such as `shopper@example.online`.
171
+ - PayTo now calls your failure handler when the agreement can't be created from what the shopper
172
+ entered ("Invalid payment details", with `errorDetails` when available), and checkout providers and
173
+ UPI when the payment fails after the shopper opened the provider's page ("Checkout has been
174
+ cancelled"). Before, these errors only showed on the page.
175
+ - In TypeScript, `providerId` and `options` of `addApplePay()` are now optional, as documented.
176
+ - In the Drop In UI, `allowedPaymentTypes: ['payglocal']` now shows PayGLocal. It used to need `'zip'`,
177
+ which also showed Zip.
178
+ - Adding Google Pay or PayPal again after its script failed to load now loads it again.
179
+ - A checkout payment (such as PayID or Zip) no longer calls your success handler twice, or your failure
180
+ handler after your success handler, when payFURL's status check answers slowly.
181
+
106
182
  ### 4.10.0 (2026-11-04)
107
183
 
108
184
  #### Added