@vrplatform/api 1.3.1-stage.6312 → 1.3.1-stage.6317
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/package.json
CHANGED
package/src/generated/v1.ts
CHANGED
|
@@ -1285,7 +1285,7 @@ export interface paths {
|
|
|
1285
1285
|
get?: never;
|
|
1286
1286
|
put?: never;
|
|
1287
1287
|
/**
|
|
1288
|
-
* @description Send owner ACH details to the single eligible Ramp push-vendor flow for verification. This action requires ach-payment-methods:write rather than general contact write access. The server resolves the connection; clients do not select one. First use activates a flow that has never been configured, while an explicitly inactive flow remains unavailable. Raw routing and account numbers are write-only and are never stored by VRPlatform. The contact becomes ready only after Ramp confirms the account. Requested and processing payments remain bound to their scheduled destination, so an update affects future payments only.
|
|
1288
|
+
* @description Send owner or vendor ACH details to the single eligible Ramp push-vendor flow for verification. This action requires ach-payment-methods:write rather than general contact write access. The server resolves the connection; clients do not select one. First use activates a flow that has never been configured, while an explicitly inactive flow remains unavailable. Raw routing and account numbers are write-only and are never stored by VRPlatform. The contact becomes ready only after Ramp confirms the account. Requested and processing payments remain bound to their scheduled destination, so an update affects future payments only. Owners can update only their own contact.
|
|
1289
1289
|
*
|
|
1290
1290
|
* Required scope: ach-payment-methods:write
|
|
1291
1291
|
*/
|