Stablecoin API v1.0.3 — Release Notes

🚀 Stablecoin API Update v1.0.3 is now live! 🎉

This release renames a fee response field, clarifies fee estimate documentation, and adds international wire support for USD payouts.

✨ What's New

• ⚠️ unblock_fee → bakkt_fee on fee estimate and on-ramp quote responses
• 🌍 International USD wire (INT_WIRE) for USD remote bank accounts
• 💰 GET /fees — payment_method documented as optional; total_fee added to response schema
• 📖 USD remote bank account transfer-method docs corrected (ACH, WIRE, INT_WIRE)
• 🔒 Disabled capabilities return HTTP 403 (FEATURE_DISABLED) instead of ambiguous errors

⚠️ Breaking Change — Fee Response Field Renamed

The public response field unblock_fee has been renamed to bakkt_fee. Request payloads are unchanged.

Affected endpoints

Migration

Clients parsing unblock_fee must update to bakkt_fee.

🌍 International USD Wire (INT_WIRE)

USD remote bank accounts now support INT_WIRE as a transfer_method value for international SWIFT wires.

Field requirements by rail

Example — international wire

{
  "account_details": {
    "currency": "USD",
    "transfer_method": "INT_WIRE",
    "swift_code": "BOFAUS3N",
    "iban": "GB82WEST12345698765432"
  },
  "recipient_type": "THIRD_PARTY",
  "third_party_details": {
    "recipient_first_name": "Jane",
    "recipient_last_name": "Doe",
    "recipient_address_line": "10 Downing Street",
    "recipient_city": "London",
    "recipient_country": "GB"
  }
}

Behaviour notes

• ACH / WIRE — unchanged from v1.0.2. Domestic WIRE with THIRD_PARTY requires full US address (recipient_state and recipient_postal_code required).
• INT_WIRE — routing_number must not be provided. recipient_state and recipient_postal_code are optional for third-party international wires.
• See Create remote bank account for the full schema.

💰 Fee Estimate Documentation

• payment_method on GET /user/fees and GET /corporate/fees is now correctly documented as optional. Omit it to receive a fee estimate not scoped to a specific payment rail.
• total_fee is now documented on fee estimate responses alongside existing percentage fields.

Existing integrations that do not send payment_method continue to work without modification.

🔒 Disabled Features Return 403

When a requested capability is turned off for your merchant, the API now returns HTTP 403 with a FEATURE_DISABLED error. Use this to distinguish "not available for this merchant" from transient server failures.

🙌 Let us know if you need help integrating these updates!