@rebilly/framepay-vue 12.246.4 → 12.246.6

package/CHANGELOG.md

@@ -1,5 +1,5 @@
-## 12.246.4 (2026-10-21)
+## 12.246.6 (2026-10-21)
 
 ### 🧱 Updated Dependencies
 
-- Updated framepay-npm to 5.246.4
+- Updated framepay-npm to 5.246.6

package/README.md

@@ -218,7 +218,7 @@ whereas:
 
 #### With rebilly-form
 
-The default behavior of `RebillyForm` is to intercept the regular submit event, execute `Rebilly.createToken()`, and then submit the form with the newly created token attached. Any inputs that include `data-rebilly` attribute with the appropriate value will be sent to `Rebilly.createToken()`.
+The default behavior of `RebillyForm` is to intercept the regular submit event, execute `Framepay.createToken()`, and then submit the form with the newly created token attached. Any inputs that include `data-rebilly` attribute with the appropriate value will be sent to `Framepay.createToken()`.
 
 ```html
 <rebilly-form @error="" @token-ready="" :extraData="{}">
@@ -241,7 +241,7 @@ The default behavior of `RebillyForm` is to intercept the regular submit event,
 
 Any DOM attributes you attach to `RebillyForm` will automatically be passed to the base `form` element.
 
-`@error` will expose the error message returned if the `Rebilly.createToken()` request failed. You can inspect `error.message` and `error.code`.
+`@error` will expose the error message returned if the `Framepay.createToken()` request failed. You can inspect `error.message` and `error.code`.
 
 `@token-ready` will expose the token object, if a Google/Apple Pay element was mounted in the form.
 
@@ -280,7 +280,7 @@ If you want to perform your own logic after token creation but before form submi
 
 #### With rebilly-token
 
-If you prefer to call `createToken()` manually, use the example below. Note that you don't want to use the `Framepay` object directly, but rather the proxied `createToken` method provided by `framepay-vue`. This method returns a promise that waits for the FramePay script to be loaded before calling `Rebilly.createToken()`. Using the pattern below will help eliminate errors due to race conditions.
+If you prefer to call `createToken()` manually, use the example below. Note that you don't want to use the `Framepay` object directly, but rather the proxied `createToken` method provided by `framepay-vue`. This method returns a promise that waits for the FramePay script to be loaded before calling `Framepay.createToken()`. Using the pattern below will help eliminate errors due to race conditions.
 
 ```html
 <form @submit="submitHandler">
@@ -445,7 +445,7 @@ Because this will only change the ID of the element you are mounting Framepay to
 
 #### `createToken` Proxy Method
 
-`framepay-vue` exports a single method: `createToken()`. This method simply wraps the Framepay method `Rebilly.createToken()` in a promise to ensure that the Framepay script has loaded and the object is available. Be sure to import `createToken` from `@rebilly/framepay-vue` instead of using `Rebilly.createToken()`, otherwise you may run into errors due to race conditions.
+`framepay-vue` exports a single method: `createToken()`. This method simply wraps `Framepay.createToken()` in a promise to ensure that the Framepay script has loaded and the object is available. Be sure to import `createToken` from `@rebilly/framepay-vue` instead of using `Framepay.createToken()`, otherwise you may run into errors due to race conditions.
 
 Again, you don't need to use `createToken` at all if you choose to use the `RebillyForm` component.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@rebilly/framepay-vue",
   "type": "module",
-  "version": "12.246.4",
+  "version": "12.246.6",
   "description": "Official Vue wrapper for Rebilly FramePay",
   "author": "Rebilly",
   "repository": {