Skip to content

feat!: add device 3DS2 fields and remove unsupported features - #20

Open
tomasz-pazdziurek-cko wants to merge 1 commit into
masterfrom
feat/POS-1692/ruby-3ds2-fields
Open

feat!: add device 3DS2 fields and remove unsupported features#20
tomasz-pazdziurek-cko wants to merge 1 commit into
masterfrom
feat/POS-1692/ruby-3ds2-fields

Conversation

@tomasz-pazdziurek-cko

@tomasz-pazdziurek-cko tomasz-pazdziurek-cko commented Aug 20, 2026

Copy link
Copy Markdown

Caution

BREAKING CHANGE

Title: feat: Update library to 4.0.0 (device/3DS fields, card chaining, submerchants; remove legacy subscriptions API)

Body:

Summary

  • Regenerated bindings from 4.0.06.0.0 of the ProcessOut API spec.
  • Adds device/3DS SDK selection, card network-token/scheme-chaining fields, and submerchant support.
  • Removes the legacy Subscriptions/Plans/Coupons/Discounts/Addons/Activity resources, which are no longer part of the public API surface.

Added

  • Device / 3DS: Device.ThreedsSdk, Device.Platform, and InvoiceDevice.Platform — explicit 3DS SDK type (web/ios/android/other) and device platform metadata.
  • Card scheme chaining & network tokens: new CardSchemeDetails type (transaction_id, transaction_link_id) wired into CardCreateRequest/CardUpdateRequest; Card.PreferredCardType, Card.InitialSchemeTransactionID, Card.PaymentAccountReference, Card.BillingCountryCode; CardContact.BillingCountryCode (new preferred field, CountryCode now documented as deprecated alias); Token.ProvisionNetworkToken sticky opt-in/out flag, also added to Invoice.Authenticate/Authorize/Capture params.
  • Submerchants: new Submerchant and SubmerchantMapping types, plus Invoice.SubmerchantID on invoice creation.
  • Invoice: new Invoice.Authenticate action; TransactionLinkID and ProvisionNetworkToken added to Authenticate/Authorize/Capture; Metadata added to Payout; PaymentConfiguration added to Create.
  • Misc smaller additions: TransactionOperation.CaptureType, UnsupportedFeatureBypass.SplitPayments, Transaction.Origin, InvoiceExternalFraudTools.Riskified.

Removed

  • Activity, Addon, Coupon, Discount, Plan, Subscription types and all associated client methods (NewActivity, NewAddon, NewCoupon, NewDiscount, NewPlan, NewSubscription, Customer.FetchSubscriptions, Project.FetchSupervised, etc.).
  • Invoice.Subscription/SubscriptionID, Transaction.Subscription/SubscriptionID, Customer.Subscriptions fields.

Breaking changes

  • Removed types/methods above will break any caller still using the Subscriptions/Plans/Coupons/Discounts/Addons/Activity API.
  • Changed method signatures: Invoice.Authorize, Invoice.AuthorizeWithContext, Invoice.Capture, Invoice.CaptureWithContext now return an additional value (extra string return, e.g. a webhook/redirect-type field) — signature changes from (*Transaction, *CustomerAction, error) to (*Transaction, *CustomerAction, string, error). Callers must update to handle the new return value.

@datadog-eu-processout

datadog-eu-processout Bot commented Aug 20, 2026

Copy link
Copy Markdown

Pipelines

⚠️ Warnings

🚦 2 Pipeline jobs failed

CodeQL | Analyze (actions)

View in Datadog · View in GitHub Actions

CodeQL could not process any code written in GitHub Actions. Configuration error encountered during the database finalization.

CodeQL | Analyze (ruby)

View in Datadog · View in GitHub Actions

CodeQL could not process any code written in Ruby due to configuration error. See troubleshooting guide for resolution.

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 96924b4 | Docs | View more details | Give us feedback!

@tomasz-pazdziurek-cko
tomasz-pazdziurek-cko force-pushed the feat/POS-1692/ruby-3ds2-fields branch from 96924b4 to 2470b3f Compare August 20, 2026 14:54
@tomasz-pazdziurek-cko
tomasz-pazdziurek-cko force-pushed the feat/POS-1692/ruby-3ds2-fields branch from 2470b3f to 9101b36 Compare August 20, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants