@payfurl/client 4.9.10 → 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.
Files changed (30) hide show
  1. package/CHANGELOG.md +163 -0
  2. package/README.md +237 -42
  3. package/dist/sdk/{CloseIcon-DhsqodgI.js → CloseIcon-Ejad61tT.js} +377 -363
  4. package/dist/sdk/{DefaultThreeDsProvider-qhlEMnGb.js → DefaultThreeDsProvider-bLoDSnkd.js} +24 -24
  5. package/dist/sdk/{MetricsGlobalThreeDsProvider-BOEA6G5r.js → MetricsGlobalThreeDsProvider-C93ttqbB.js} +17 -17
  6. package/dist/sdk/{PayWayAppleButton-ziK0EEr8.js → PayWayAppleButton-BzAwlGS-.js} +1 -1
  7. package/dist/sdk/{alerts-2ShoA1hc.js → alerts-1YSRy5iI.js} +9 -9
  8. package/dist/sdk/{cxpay-B2_DeDZt.js → cxpay-DblHb5vN.js} +1 -1
  9. package/dist/sdk/{default-2G4dbyeg.js → default-C7f86Fx-.js} +1 -1
  10. package/dist/sdk/{ecentric-kLMDhKl_.js → ecentric-B3UohyO_.js} +18 -17
  11. package/dist/sdk/{epna-p_tBGPK3.js → epna-DwUg2IlB.js} +1 -1
  12. package/dist/sdk/{flashbanc-ChTsnYMc.js → flashbanc-LXs8bahL.js} +1 -1
  13. package/dist/sdk/forter-CLFaJUYa.js +30 -0
  14. package/dist/sdk/{gpayments-Sa7Ek9FT.js → gpayments-DoZug3PV.js} +16 -16
  15. package/dist/sdk/{metrics_global-CxURr43F.js → metrics_global-BM-ooge-.js} +1 -1
  16. package/dist/sdk/{nmi-Bq5IGnP2.js → nmi-BA3ZTdQa.js} +1 -1
  17. package/dist/sdk/{nuvei-BDdU_s1G.js → nuvei-DIWsLlLz.js} +30 -30
  18. package/dist/sdk/{payabli-4-XnuYBw.js → payabli-DgrTI1Et.js} +1 -1
  19. package/dist/sdk/payfurl.d.ts +456 -0
  20. package/dist/sdk/payfurl.es.js +1885 -1601
  21. package/dist/sdk/payfurl.umd.js +8 -8
  22. package/dist/sdk/{payglocal-9n0hrZAf.js → payglocal-ezp0MsaZ.js} +36 -35
  23. package/dist/sdk/{payway_rest-vCmhadiN.js → payway_rest-D8-T-ULx.js} +1 -1
  24. package/dist/sdk/redact-Bn_hfytX.js +46 -0
  25. package/dist/sdk/{skybank-BIJrZVJd.js → skybank-BgDLlFXX.js} +1 -1
  26. package/dist/sdk/{strings-ahZ6LOKg.js → strings-Dp6oE-U1.js} +18 -14
  27. package/dist/sdk/style.css +1 -1
  28. package/dist/sdk/whenRendered-jR4Jls4M.js +12 -0
  29. package/package.json +9 -2
  30. package/dist/sdk/forter-BKH-4F0d.js +0 -26
package/CHANGELOG.md ADDED
@@ -0,0 +1,163 @@
1
+ # Changelog
2
+
3
+ What changed in each version of the payFURL Client SDK. The `@payfurl/client` npm package and the
4
+ script on `assets.payfurl.com` share version numbers, so this covers both. The changelog starts with
5
+ version 4.9.3.
6
+
7
+ ## Unreleased
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
+
63
+ ## 4.10.0 (2026-11-04)
64
+
65
+ ### Added
66
+
67
+ - TypeScript types. The package now includes type definitions for every method, option and handler,
68
+ so your editor suggests them and the TypeScript compiler checks your calls. Import the types by
69
+ name, for example `import payfurl, { type DropInOptionsType, type SuccessResponseType } from "@payfurl/client"`.
70
+ - `setCurrency()` changes the currency of the card, Google Pay, Apple Pay and saved payment method
71
+ components already on the page, as `setAmount()` does for the amount. Add PayPal, PayTo and Checkout
72
+ components again for a new currency.
73
+ - `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.4.0 use these types for their props and events,
74
+ and their own type definitions now load.
75
+
76
+ ### Fixed
77
+
78
+ - Google Pay errors now reach your failure handler. Closing the Google Pay sheet is still not a
79
+ failure.
80
+ - The close button of the Ecentric 3-D Secure challenge now closes it.
81
+ - `@payfurl/react-plugin` 1.4.0: `PayfurlDropin` no longer fails when it mounts, and no longer rebuilds
82
+ the drop-in, losing what the shopper typed, each time its parent re-renders. A new `amount` or
83
+ `successMessage` updates the drop-in in place.
84
+
85
+ ## 4.9.10 (2026-10-29)
86
+
87
+ ### Added
88
+
89
+ - Forter fraud screening for Google Pay and Apple Pay payments, on accounts that use Forter.
90
+
91
+ ### Fixed
92
+
93
+ - When you add several components at once, each now uses its own options and provider. A component
94
+ added while another was still loading used to take the first one's.
95
+ - The loading spinner no longer reappears after a failed Forter 3-D Secure challenge.
96
+
97
+ ## 4.9.9 (2026-10-25)
98
+
99
+ ### Fixed
100
+
101
+ - PayID through Azupay now appears in the Drop In UI. A Drop In with PayID as its only payment method
102
+ never finished loading.
103
+
104
+ ## 4.9.8 (2026-10-22)
105
+
106
+ ### Added
107
+
108
+ - Forter fraud screening for `tokeniseWith3Ds`, `tokeniseCard`, `addThreeDsWithToken` and
109
+ `addSavedPaymentMethods`, on accounts that use Forter. A payment that Forter declines stops when your
110
+ account is set to stop declined payments.
111
+
112
+ ### Fixed
113
+
114
+ - PayPal payments on accounts that use Forter no longer fail at the fraud check.
115
+ - A card that skips 3-D Secure through network token authentication still gets the fraud check.
116
+ - A payment no longer waits forever when the fraud check or a Forter 3-D Secure result never answers:
117
+ your failure handler is called instead.
118
+
119
+ ## 4.9.7 (2026-10-21)
120
+
121
+ ### Fixed
122
+
123
+ - A Forter 3-D Secure challenge no longer fails when Forter's script loads after the challenge starts.
124
+
125
+ ## 4.9.6 (2026-10-19)
126
+
127
+ ### Added
128
+
129
+ - Google Pay for CyberSource and NAB Gateway.
130
+ - The `billingDetailsRequired` Google Pay option, for `addGooglePay` and the Drop In's
131
+ `googlePayOptions`: `true` asks the shopper for their email address and full billing address.
132
+ CyberSource and NAB Gateway need it unless you pass the customer's name, email and billing address
133
+ yourself.
134
+
135
+ ## 4.9.5 (2026-10-13)
136
+
137
+ ### Changed
138
+
139
+ - Internal improvements. Nothing changes in how you use the SDK.
140
+
141
+ ## 4.9.4 (2026-10-12)
142
+
143
+ ### Security
144
+
145
+ - 3-D Secure on a saved card token (`addThreeDsWithToken`) no longer brings the card's details into the
146
+ browser: it runs on the card your gateway stores.
147
+
148
+ ### Fixed
149
+
150
+ - Nuvei 3-D Secure stops after it reports a failure, instead of opening the challenge as well.
151
+
152
+ ## 4.9.3 (2026-10-08)
153
+
154
+ ### Added
155
+
156
+ - The Apple Pay button now appears in Chrome, Firefox and Edge, where Apple lets shoppers pay with
157
+ their iPhone. It used to appear in Safari only.
158
+ - Forter as a 3-D Secure provider on its own, without Forter fraud screening.
159
+
160
+ ### Fixed
161
+
162
+ - A Forter 3-D Secure challenge whose result is anything but a success now fails the payment.
163
+ - Forter's scripts use your account's Forter site ID.
package/README.md CHANGED
@@ -1,65 +1,260 @@
1
- # PayFURL Client SDK
1
+ # payFURL Client SDK
2
2
 
3
- The Client SDK is used to securely collect payment details in the browser. It seamlessly integrates into your existing payment page.
3
+ Collect payment details in the browser and turn them into a payFURL payment token that your server
4
+ charges through the [payFURL API](https://docs.payfurl.com/guides). Cards, PayPal, Google Pay, Apple
5
+ Pay, PayTo, Click to Pay and more, through one integration.
4
6
 
5
- When initialized, the SDK securely loads an iframe hosted by payFURL.
6
- This iframe collects the payment details, which are then submitted to payFURL and converted to a payment token.
7
- The payment token is added as a hidden input to the form. For PayPal or Buy Now Pay Later payments, the payment details are converted to a transactionId, which is also added as a hidden input to the form.
8
- Payment detail collection is triggered when the form is submitted.
7
+ Card details are typed into fields that payFURL hosts in an iframe, so card numbers never reach your
8
+ page's code.
9
9
 
10
- ## Integrate with your app
10
+ [Documentation](https://docs.payfurl.com/client_sdk/overview) ·
11
+ [API reference](https://docs.payfurl.com/client_sdk/reference) ·
12
+ [Changelog](https://docs.payfurl.com/client_sdk/changelog) ·
13
+ [Support](https://docs.payfurl.com/support)
11
14
 
12
- If you want to use the published PayFURL Client SDK in your application, install it from npm:
15
+ ## Install
13
16
 
14
- ```bash
15
- npm install @payfurl/client
16
- ```
17
-
18
- Import the SDK into your application:
17
+ ```bash
18
+ npm install @payfurl/client
19
+ ```
19
20
 
20
- ```javascript
21
- import payfurl from '@payfurl/client';
22
- ```
21
+ To load the SDK from a `<script>` tag instead, see
22
+ [Get started](https://docs.payfurl.com/client_sdk/get_started).
23
23
 
24
- ## Usage
24
+ ## Quick start
25
25
 
26
- To initialize the SDK, use the following code:
26
+ Add a container inside your payment form:
27
27
 
28
- ```javascript
29
- import payfurl from '@payfurl/client';
30
- const pf = payfurl.init(
31
- "sandbox", // environment name
32
- "<public-key>", // your public key
33
- true // enable debug mode
34
- );
35
- ```
28
+ ```html
29
+ <form method="POST" action="/pay">
30
+ <div id="payment"></div>
31
+ <button type="submit">Pay</button>
32
+ </form>
33
+ ```
36
34
 
37
- To create a drop-in UI:
35
+ Then add the Drop In UI, which shows every payment method your account has for the amount and
36
+ currency:
38
37
 
39
- ```javascript
40
- pf.addDropIn('<id-of-div-container>', 20, 'AUD');
41
- ```
38
+ ```javascript
39
+ import payfurl from "@payfurl/client";
42
40
 
43
- ## Local development
41
+ payfurl
42
+ .init("sandbox", "<your public key>")
43
+ .addDropIn("payment", 20, "AUD");
44
+ ```
44
45
 
45
- If you are working in this repository, install the project dependencies with:
46
+ When the shopper submits the form, the SDK collects the payment details, adds the result to the form
47
+ as a hidden input, and submits it to your server: `token` for a card, `transactionId` for PayPal and
48
+ other payment types that complete the payment themselves. To keep the shopper on the page, handle the
49
+ result yourself:
46
50
 
47
- ```bash
48
- npm install
51
+ ```javascript
52
+ payfurl
53
+ .onSuccess((message) => {
54
+ // message.token for a card, message.transactionId for PayPal and other payment types
55
+ // that complete the payment themselves
56
+ })
57
+ .onFailure((message) => console.error(message.error));
49
58
  ```
50
59
 
51
- ## Local testing
60
+ Your public key is on **Account Info** in the payFURL dashboard. Use `"production"` and a production
61
+ key to go live.
52
62
 
53
- To serve the SDK locally for testing, run:
63
+ ## Payment methods
54
64
 
55
- ```bash
56
- npm run server
65
+ | Method | Adds |
66
+ |---|---|
67
+ | `addDropIn` | Every payment method on your account, in one component |
68
+ | `addCard` | A card form |
69
+ | `addPaypal` | PayPal buttons |
70
+ | `addGooglePay` | A Google Pay button |
71
+ | `addApplePay` | An Apple Pay button |
72
+ | `addPayTo` | A PayTo agreement form |
73
+ | `addCheckout` | A third-party checkout, such as Afterpay or Affirm |
74
+ | `addSavedPaymentMethods` | A customer's saved cards |
75
+
76
+ Each has its own page in the [documentation](https://docs.payfurl.com/client_sdk/overview), with its
77
+ options.
78
+
79
+ ## TypeScript
80
+
81
+ The package includes its type definitions. Every option type can be imported by name:
82
+
83
+ ```typescript
84
+ import payfurl, { type DropInOptionsType, type SuccessResponseType } from "@payfurl/client";
85
+
86
+ const options: DropInOptionsType = { allowedPaymentTypes: ["card", "googlepay"] };
87
+ payfurl.init("sandbox", "<your public key>")
88
+ .addDropIn("payment", 20, "AUD", options)
89
+ .onSuccess((message: SuccessResponseType) => console.log(message.token));
57
90
  ```
58
91
 
59
- This starts a local HTTP server on port `3001`.
92
+ ## React and Vue
93
+
94
+ [`@payfurl/react-plugin`](https://www.npmjs.com/package/@payfurl/react-plugin) and
95
+ [`@payfurl/vue-plugin`](https://www.npmjs.com/package/@payfurl/vue-plugin) wrap the Drop In UI in a
96
+ component: see [React](https://docs.payfurl.com/client_sdk/frameworks/react) and
97
+ [Vue](https://docs.payfurl.com/client_sdk/frameworks/vue).
98
+
99
+ ## Changelog
100
+
101
+ What changed in each version of the payFURL Client SDK. The `@payfurl/client` npm package and the
102
+ script on `assets.payfurl.com` share version numbers, so this covers both. The changelog starts with
103
+ version 4.9.3.
104
+
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
+
160
+ ### 4.10.0 (2026-11-04)
161
+
162
+ #### Added
163
+
164
+ - TypeScript types. The package now includes type definitions for every method, option and handler,
165
+ so your editor suggests them and the TypeScript compiler checks your calls. Import the types by
166
+ name, for example `import payfurl, { type DropInOptionsType, type SuccessResponseType } from "@payfurl/client"`.
167
+ - `setCurrency()` changes the currency of the card, Google Pay, Apple Pay and saved payment method
168
+ components already on the page, as `setAmount()` does for the amount. Add PayPal, PayTo and Checkout
169
+ components again for a new currency.
170
+ - `@payfurl/react-plugin` and `@payfurl/vue-plugin` 1.4.0 use these types for their props and events,
171
+ and their own type definitions now load.
172
+
173
+ #### Fixed
174
+
175
+ - Google Pay errors now reach your failure handler. Closing the Google Pay sheet is still not a
176
+ failure.
177
+ - The close button of the Ecentric 3-D Secure challenge now closes it.
178
+ - `@payfurl/react-plugin` 1.4.0: `PayfurlDropin` no longer fails when it mounts, and no longer rebuilds
179
+ the drop-in, losing what the shopper typed, each time its parent re-renders. A new `amount` or
180
+ `successMessage` updates the drop-in in place.
181
+
182
+ ### 4.9.10 (2026-10-29)
183
+
184
+ #### Added
185
+
186
+ - Forter fraud screening for Google Pay and Apple Pay payments, on accounts that use Forter.
187
+
188
+ #### Fixed
189
+
190
+ - When you add several components at once, each now uses its own options and provider. A component
191
+ added while another was still loading used to take the first one's.
192
+ - The loading spinner no longer reappears after a failed Forter 3-D Secure challenge.
193
+
194
+ ### 4.9.9 (2026-10-25)
195
+
196
+ #### Fixed
197
+
198
+ - PayID through Azupay now appears in the Drop In UI. A Drop In with PayID as its only payment method
199
+ never finished loading.
200
+
201
+ ### 4.9.8 (2026-10-22)
202
+
203
+ #### Added
204
+
205
+ - Forter fraud screening for `tokeniseWith3Ds`, `tokeniseCard`, `addThreeDsWithToken` and
206
+ `addSavedPaymentMethods`, on accounts that use Forter. A payment that Forter declines stops when your
207
+ account is set to stop declined payments.
208
+
209
+ #### Fixed
210
+
211
+ - PayPal payments on accounts that use Forter no longer fail at the fraud check.
212
+ - A card that skips 3-D Secure through network token authentication still gets the fraud check.
213
+ - A payment no longer waits forever when the fraud check or a Forter 3-D Secure result never answers:
214
+ your failure handler is called instead.
215
+
216
+ ### 4.9.7 (2026-10-21)
217
+
218
+ #### Fixed
219
+
220
+ - A Forter 3-D Secure challenge no longer fails when Forter's script loads after the challenge starts.
221
+
222
+ ### 4.9.6 (2026-10-19)
223
+
224
+ #### Added
225
+
226
+ - Google Pay for CyberSource and NAB Gateway.
227
+ - The `billingDetailsRequired` Google Pay option, for `addGooglePay` and the Drop In's
228
+ `googlePayOptions`: `true` asks the shopper for their email address and full billing address.
229
+ CyberSource and NAB Gateway need it unless you pass the customer's name, email and billing address
230
+ yourself.
231
+
232
+ ### 4.9.5 (2026-10-13)
233
+
234
+ #### Changed
235
+
236
+ - Internal improvements. Nothing changes in how you use the SDK.
237
+
238
+ ### 4.9.4 (2026-10-12)
239
+
240
+ #### Security
241
+
242
+ - 3-D Secure on a saved card token (`addThreeDsWithToken`) no longer brings the card's details into the
243
+ browser: it runs on the card your gateway stores.
244
+
245
+ #### Fixed
246
+
247
+ - Nuvei 3-D Secure stops after it reports a failure, instead of opening the challenge as well.
248
+
249
+ ### 4.9.3 (2026-10-08)
250
+
251
+ #### Added
60
252
 
61
- To open the SDK main page in your browser, go to `http://localhost:3001/sdk.html`.
253
+ - The Apple Pay button now appears in Chrome, Firefox and Edge, where Apple lets shoppers pay with
254
+ their iPhone. It used to appear in Safari only.
255
+ - Forter as a 3-D Secure provider on its own, without Forter fraud screening.
62
256
 
63
- ## More info
257
+ #### Fixed
64
258
 
65
- For more thorough documentation, visit [the PayFURL Client SDK docs](https://docs.payfurl.com/client_sdk/).
259
+ - A Forter 3-D Secure challenge whose result is anything but a success now fails the payment.
260
+ - Forter's scripts use your account's Forter site ID.