Changelog
New features, improvements and fixes for developers building on COPE, newest first. Each entry is labelled New, Improved, Changed, Fixed, Deprecated or Removed; entries that need you to do something say so.Week of November 9, 2026
Checkout
-
New — The checkout that
POST /v1/commerce/checkoutsandGET /v1/commerce/checkouts/{id}answer statestotals.due_now_minor_units: what the buyer pays at checkout. It equalstotals.total_minor_unitsunless a line starts with a free trial, which is charged on its own when its trial ends; a checkout whose only product starts with a free trial reads0. A checkout created before this change does not carry it. -
Changed —
mixed_vat_mode_cartnow refuses at checkout exactly what it refuses when a product is added to a cart: a Non-ESS product together with one that is not.checkout(),createPrefilledCheckout(),POST /v1/commerce/checkoutsand paying decide it on the products alone, so a cart whose products are all Non-ESS, or all not, is no longer refused because of where the buyer is or how the seller’s VAT is set up.
Webhooks
- Fixed · 2026-11-13 —
payment_methodoncart.order.completednames the method the buyer paid with: itstype, and for a card alsobrandandlast4. It could sayotherinstead, most often for a card and also for iDEAL, EPS, Bancontact and Afterpay payments, and a free-trial order’s card came withoutbrandandlast4. Webhooks already delivered are not sent again.
Checkout SDK & MCP server
-
New —
cope-sdk0.1.7.^0.1.0takes it on your next install.plan_idonaddLine()andupdateLine(), and a prefilled checkout line’splanId, are declared to take a plan’splan_ID frompayment_plans[].uuidas well as its integerid, andCartLine.payment_plannames a line’s plan by that ID.CartTotalsdeclaresdue_now_minor_unitsand its parts, what the buyer pays today, andCartLinedeclaresline_type.Cartdeclaresinstallment_restricted_buyer_countries, andApiErrorCodedeclaresinstallment_not_available_in_countryandtax_location_locked, whichsetBuyerIdentity()answers when a payment has started and the change would move the buyer’s tax. Its MCP endpoint’sget_productalso names each plan by itsplan_ID, aspaymentPlanId, whichadd_lineandupdate_linetake asplanId, and its cart and checkout results state what the buyer pays today, asdueNowMinorUnits. -
Deprecated —
one_click_charge_consenton the Checkout SDK’sCart. The cart API no longer sends it, socope-sdkreads it as{ applicable: false, terms_version: null }on every cart, and 0.2.0 removes it from the types. The buyer agrees to a one-click upsell’s charge on the upsell itself, so your checkout page needs no box for it. -
New —
cope-mcp0.1.7.create_offertakeshasNetPriceon itspricing:truemakes the offer’s amounts net of tax, with the tax added on top at checkout, andfalsemakes them include tax; left out, the product’s own setting decides, as before. Until now it was dropped without a word. A key the tool does not take is named in the confirmation you are asked, as not used, and is not sent.send_offer,resend_offerandcancel_offersay when an offer’s prices are net of tax. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.7; 0.1.6 keeps working. See MCP server for your store. -
Changed — In the Checkout SDK,
pending_approvalinpurchase_block_reasonand in a422 not_saleable’sblock_reasoncan now also mean an approved product that is not available for purchase yet. The newpurchase_block_detailandblock_detailbeside them saynon_ess_not_enabledin that case and repeat the reason otherwise.POST /v1/commerce/checkoutsnow refuses such a product withnot_saleabletoo. Action required — if your Checkout SDK integration tells buyers apending_approvalproduct awaits approval, readpurchase_block_detailorblock_detailfirst.
Documentation
-
Fixed · 2026-11-12 — The errors reference and the
422description ofPOST /v1/commerce/checkoutssaid itsnot_saleablerefusal carriesblock_reason. It carries neitherblock_reasonnorblock_detail. Nothing changes in how COPE behaves.Details
errors[].paramnames the refused line’slines.N.product_idorlines.N.plan_id; aplan_idrefusal can be for the plan sent or, when none was sent, for the product’s default plan.errors[].detailis human-readable text and may not name the reason.- The Checkout SDK’s
not_saleablecarriesblock_reasonandblock_detailwhen a block reason applies, and neither for an inactive product.
-
Fixed · 2026-11-09 — The order states and the
cart.order.completedpage no longer say a completed order can be reconciled. Fulfill the order or grant access once it issucceeded, and reconcile money onpayment.sale.succeeded, which can arrive after it: until that event, the order’spayments[].statusreadspending, each line’spayments_madereads0, andGET /v1/commerce/payments/{id}withoutstatusanswers404. An order whose every line starts with a free trial charges nothing at checkout: its sale readstrial, and its firstpayment.sale.succeededcomes when the trial converts. Nothing changes in how COPE behaves.
Week of November 2, 2026
Checkout
- Changed — A checkout keeps the free trial it opened with. If a seller ends, shortens or lengthens a product’s free trial while a buyer’s checkout is open, that checkout still charges what the buyer was shown, at the trial the buyer was shown, and the next checkout takes the change. An offer keeps its trial the same way. A checkout whose product was given a free trial after it opened is no longer refused when the buyer pays; it sells without that trial.
-
New — An installment plan can be refused because of where the buyer is: a checkout for a buyer whose country does not allow a new installment plan answers
422installment_not_available_in_country, and the cart lists those countries ininstallment_restricted_buyer_countriesso your checkout can hide installment plans first. Action required — if you sell installment plans, handle the code by letting the buyer choose another plan.Details
- The buyer’s billing country, tax country and
countryare all checked; any one of them on the list refuses.UKandELare read asGBandGR; while any country is restricted, a country that is no two-letter ISO 3166-1 code is refused the same way, when the checkout or offer is created. POST /v1/commerce/checkoutsanswers the code as the problem’scode, witherrors[].paramnaming the line, for examplelines.1.plan_id. In the Checkout SDK,checkout(),createPrefilledCheckout()and paying answer it withfield: "plan_id".POST /v1/commerce/offersanswers422 validation_failed, withinstallment_not_available_in_countryaserrors[].codeonpricing.plan_type; matcherrors[].code, not the top-levelcode.installment_restricted_buyer_countriesis[]when no country is listed andnullwhen it cannot be read; then show every plan, the refusal still applies.- One-time and subscription plans, and installment plans already running, are not affected. A product’s
installment_sales_enableddoes not change: it says whether the seller sells installment plans, not whether a given buyer can start one.
- The buyer’s billing country, tax country and
-
Changed — A cart with two or more products offers only the payment methods every product accepts.
lines[].payment_methodsandpayable_payment_method_typesnarrow to that set, because one payment pays for the whole cart.Details
- Before,
payable_payment_method_typeslisted a method any one product accepted, and each line listed its own product’s methods. A cart mixing a product that accepts Klarna with one that does not now omits Klarna from both, so read these fields from the cart, not from a product. - An installment plan beside other products holds the whole cart to what an installment plan accepts: card, and PayPal where it can bill again.
- Each line keeps its product’s own name for a method, so
lines[].payment_methodscan spell one method differently across lines. Compare onpayable_payment_method_typeswhen you need one list. - A cart with one product answers as before. Card is never removed.
- Before,
-
Changed — A buyer outside the European Union, the United Kingdom and Switzerland no longer needs
withdrawal_waiver, whatever the product: no payment for them is refused with422 missing_withdrawal_waiver. COPE’s checkout page shows them only the terms box, which no longer mentions a right of withdrawal. See the consents table.Details
- A
withdrawal_waiveryou send for such a buyer is still recorded and refuses nothing. - The same rules apply to a checkout opened from a phone offer, by the country and customer type the seller set on the offer.
- A
Offers
- Changed — The
quantityof an offer’s product follows the product’s own rule: more than 1 only when the product lets a buyer choose a quantity, and then up to the product’s maximum. Anything else is refused with422quantity_not_allowed,errors[].paramquantity, and no offer is created. Before, any quantity up to 100 was accepted, and a quantity above 100 was refused with422 invalid_parameter. Action required if you create offers with aquantityabove 1: turn on quantity selection for the product, with a maximum that covers it.
Products and offers
-
Changed — An installment plan has a maximum length.
interval_countxnext_payments_count, the payments after the first, may be at most 365 for adayinterval, 52 forweek, 36 formonthand 6 foryear: a plan paid every month has at most 37 payments, one paid every 4 weeks at most 14.POST /v1/commerce/productsrefuses a longer plan with422 validation_failedandinstallment_duration_exceeds_maxaserrors[].codeonpayment_plans[0].next_payments_count, and creating an offer refuses one with the same code onpricing.installment_count, which counts the first payment too. Action required — if you create installment plans, keep them within the limit and handle the code.Details
- Match
errors[].code, not the top-levelcode. When one billing period alone is longer than the limit, for exampleweekwith aninterval_countof 53, the code is oninterval_countinstead, because no number of payments fits.second_payment_inis not counted. - A request another rule already refuses gets only that rule’s code: more than 120 payments after the first answers
less_than_or_equal_to, and a billing period longer than 2 years answersinterval_exceeds_max. The length is checked once that is fixed. - An installment plan saved before the limit keeps selling, and a product holding one still saves. Changing that plan’s
plan_type,interval,interval_countornext_payments_countapplies the limit to it. - One-time and subscription plans are not affected.
- Match
Webhooks
-
New —
totals.chargedoncart.order.completedstates what the checkout took: the lines not in a free trial, with any shipping they carry, and0when every line is in a free trial. It carriesgross_minor_units,net_minor_units,tax_minor_unitsandcurrency.totals.totalstill states every line’s first payment, charged today or not, so usetotals.chargedfor what the buyer paid today.line_items[].trial_daysstates a trial’s length, on every line sold with a free trial; to tell which lines are in a free trial, read it.line_items[].is_trialis unchanged. A replay of an order placed before this change has neithertotals.chargednortrial_days. -
New — The payment and order webhooks carry the refund period the buyer was promised:
line_items[].product.refund_period_days, in days, onpayment.sale.succeeded,payment.refund.created,payment.refund.reversed,payment.chargeback.created,payment.chargeback.reversed, the fourpayment.dispute.*events andcart.order.completed.-1and0both mean no refund was promised: do not compute a deadline from a value of0or less. It isnullwhen the sale recorded no refund period.
Checkout SDK & MCP server
- New —
cope-sdk0.1.6.^0.1.0takes it on your next install.ApiErrorCodedeclaresmixed_trial_cart, andCartLinedeclaresproduct_type,withdrawal_period_b2c_daysandwithdrawal_period_b2b_days, which decide whether the buyer is asked forwithdrawal_waiver(see consents).missing_auto_renewal_consentleavesApiErrorCode, because no payment is refused with it any more; code that compareserror.codewith that string still compiles. Its MCP endpoint tells the agent that the buyer waives their right of withdrawal only if the checkout page asks them to. Nothing else changes. - New —
cope-mcp0.1.6.create_productandupdate_producttake a product’s withdrawal periods:withdrawalPeriodB2cDaysandwithdrawalPeriodB2bDaysfor buyers in the European Union, the United Kingdom and Switzerland, and the fourrestOfWorld*withdrawal and refund periods for buyers elsewhere, sent all four together or all four asnullto clear them. Every period accepts-1, none, where the product may offer it; the refund periods refused it before. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.6; 0.1.5 keeps working. See MCP server for your store.
Week of October 26, 2026
Webhooks
-
New — Send a test webhook of any event type COPE sends.
POST /v1/webhooks/endpoints/{id}/test-eventstakes an optionalevent_type, and the test arrives as that type, filled with example data and your own business. See test events.Details
- Every test event,
webhook.testincluded, now ends its envelope with"test": true. Production deliveries do not carry it, so a receiver can tell a test apart and skip fulfilment. - An
event_typeCOPE does not send answers422 validation_failedand sends nothing. - A test delivery cannot be replayed:
POST /v1/webhooks/deliveries/{delivery_id}/replayanswers422 test_delivery_not_replayable(it answered404 not_foundbefore), and replay jobs leave test deliveries out. Send a new test instead. - The test-event
201response gainsevent_type, the type that went out. - The example bodies on every event page now show realistic values, the same data a test event sends.
- Every test event,
Checkout
-
Changed · 2026-10-30 — A product with a free trial is bought on its own. A cart that holds a line with a free trial and any other line is refused with
422mixed_trial_cart: byPOST /v1/commerce/checkouts, and in the Checkout SDK byaddLine(),checkout()andcreatePrefilledCheckout(). Before, the whole cart started as a free trial and the other products were never charged. Action required — if you sell a product with a free trial together with other products, send it in a checkout of its own.Details
addLine()refuses the second line, whichever of the two has the trial. Two products that both have a free trial cannot share a checkout either.POST /v1/commerce/checkoutsnames the refused line inerrors[].param, for examplelines.1.product_id.- A checkout whose product was given a free trial after the checkout was opened is refused when the buyer pays, before anything is charged.
-
Fixed · 2026-10-30 — While a business is on a checkout hold, buyers can no longer buy its products from a product link or the 1-click checkout link. Opening the checkout (
POST /carts/{id}/checkout) and starting the payment are now refused with403business_checkout_holdfor every cart that holds the business’s products. A cart created with the business’s publishable key, as the Checkout SDK creates it, was already refused and still is; a cart a buyer opened from one of those links was not.
Checkout consents
-
Changed — Whether a payment needs
withdrawal_waivernow depends on where and as whom the buyer buys. A person in the European Union, the United Kingdom or Switzerland needs it when a cart line’s product promises them no withdrawal right (-1) or 0 days, or has no withdrawal period yet and does not ship; a company there never needs it; a buyer anywhere else needs it, as before, when a line does not ship. Without it the payment is refused with422 missing_withdrawal_waiver. Action required if your page asks every buyer of a digital product for the waiver: ask for it only when the consents table requires it.Details
- Where the buyer buys is the country of the buyer identity’s
billing_address, or itscountrywhen the address names none.buyer_type: "b2b"buys as a company. - Cart lines carry
product_type,withdrawal_period_b2c_daysandwithdrawal_period_b2b_days, so your page can decide which boxes to show. A withdrawal period is in days,-1for no withdrawal right,nullwhile the seller has not chosen one. - A
withdrawal_waiveryou send when it is not required is recorded like any other consent and refuses nothing.
- Where the buyer buys is the country of the buyer identity’s
-
Removed — A subscription no longer requires
auto_renewal_consent: no payment is refused withmissing_auto_renewal_consent, and COPE’s checkout page no longer shows the auto-renewal box. One you send is still recorded. - Improved — COPE’s checkout page shows a person buying in the European Union, the United Kingdom or Switzerland their right of withdrawal before the consent boxes, and asks them to agree to the Terms & Conditions and the Buyer Terms, with one waiver box for each wording the cart needs. A company there sees a notice that no statutory right of withdrawal applies. Buyers elsewhere see the page as before, without the auto-renewal box.
Checkout SDK
-
New — Metadata and attribution is one page for passing your own data and marketing attribution into a checkout and reading them back. It covers
metadata,external_reference, UTM parameters, ad click ids and affiliate links, for every way into checkout.Details
- It shows which of
metadata,external_referenceandattributioneach way into checkout takes, and what an offer or a checkout from your server locks. - It says what happens when a buyer comes back on another link, and which webhooks and thank-you page parameters return each value.
- The Checkout SDK overview keeps a short summary under its existing headings and links to it.
- It shows which of
-
Fixed · 2026-10-27 — Webhooks carry the affiliate code of the buyer’s link click as
first_click_ref, not asattribution.affiliate_idas the description of the thank-you page’saffiliateparameter said:attributionholds only UTM parameters and ad click ids. Neitherfirst_click_refnoraffiliateis necessarily the promoter credited with the sale. See affiliate links.Details
- Earlier examples put
affiliate_idandpromo_codein theattributionobject ofcreateCart()andcreatePrefilledCheckout(). Neither is applied there.
- Earlier examples put
-
Changed —
checkout()(POST /carts/{id}/checkout) is refused with409 price_changedwhen the cart’s lines, currency or promo code change while the checkout is being created: another request changed them, for example the buyer in a second tab, or a promo code that no longer applies was removed when the cart was priced. Nothing is created. Before,price_changedcame only withexpected_total_minor_units, whichCheckoutPayloaddoes not declare, and such a checkout opened anyway. Action required if your page treats everycheckout()error as final: onprice_changed, show the buyer the new total fromgetCart()and callcheckout()again. See errors.
Offers
-
Changed — The
buyer.localeyou name when you create an offer now sets the buyer’s language: the checkout opens in it, the offer emails are written in it, and the order records the language the checkout shows when the buyer pays. A regional or differently cased code is read as its language (de-DEisde). Action required if you send"en"only because it was documented as the default: omitbuyer.localeto keep the checkout following the buyer’s browser.Details
- The buyer can still switch the checkout to another language, and their choice wins, for the order and for the offer emails sent after it.
- A language your checkout does not offer is ignored, as is a value that is not a language COPE supports. Neither is refused.
- Omitting
buyer.localekeeps the previous behaviour: the checkout follows the buyer’s browser and the offer emails are in English, except that an offer email sent after the buyer picked a language in the checkout is in that language. buyer_profile.localein offer responses still reads"en"for an offer that named no language.- A language you enable or disable for your checkout while a buyer has it open can make the order’s language differ from the one the checkout showed.
Products
-
New —
POST /v1/commerce/productscreates products undertax_codeSB046004(manicures and pedicures) as physical services. Sendproduct_location_attributeswith them: without it the request is refused with422 validation_failed.Details
SB046004maps toproduct_typephysical_serviceandtax_groupphysical_services.
-
Fixed · 2026-10-29 —
POST /v1/commerce/productswithtax_codeST050100orSD036434now creates a digital service, which needs noproduct_location_attributes. These creates were refused with422 validation_failedwhen they sent no location. Action required if you sendproduct_typeortax_groupwith either code: senddigital_serviceanddigital_services, or the request is refused with400 invalid_request.Details
- Both codes map to
product_typedigital_serviceandtax_groupdigital_services. - The
400 invalid_requestfor aproduct_typeortax_groupthat does not match thetax_codehas anerrorsentry with thecodedoes_not_match_tax_code.
- Both codes map to
-
New — Products carry a withdrawal period beside their refund period, for a person (B2C) and for a company (B2B):
withdrawal_period_b2c_daysandwithdrawal_period_b2b_daysonPOST /v1/commerce/products,PATCH /v1/commerce/products/{id}and every product response.-1means no withdrawal right, and on a refund period it means no refund. A refund period may not be shorter than the withdrawal period for the same customer type; a write that would leave it shorter is refused with422 validation_failed.Details
- The withdrawal options depend on
product_type. A person can be offered-1(no withdrawal) only on adigital_product, and otherwise0,14,30,60or90days; a company can be offered-1or0,7,10,14,30,60or90days. -1as a refund period is accepted only with a withdrawal period of-1.- Both withdrawal fields are optional on a write, and
nullon a product that has none. Existing products keep their refund periods unchanged. payment_chunks[].refund_period_dayson payments can now be-1: the buyer was promised no refund, as with0. Do not compute a deadline from a value of0or less. Webhooks carry the period from the week of November 2.
- The withdrawal options depend on
-
New — A product can give buyers outside the European Union, the United Kingdom and Switzerland their own withdrawal and refund periods:
rest_of_world_withdrawal_period_b2c_days,rest_of_world_refund_period_b2c_days,rest_of_world_withdrawal_period_b2b_daysandrest_of_world_refund_period_b2b_daysonPOST /v1/commerce/products,PATCH /v1/commerce/products/{id}and every product response. While the four arenull, the other four periods apply to every buyer. A sale freezes the periods that applied to its buyer.Details
- Send all four together, or all four as
nullto apply the other four periods to every buyer again. Sending some of them is refused with422 validation_failed. - The options do not depend on
product_type: a withdrawal period of-1or7,10,14,30,60or90days, for a person and a company alike, and a refund period at least as long.-1as a refund period is accepted only with a withdrawal period of-1; there is no 0-day option.
- Send all four together, or all four as
Week of October 19, 2026
Subscriptions
- Changed — A card renewal is now charged at the subscription’s
next_billing_at, as soon as COPE finalises the renewal, instead of about an hour later. A declined renewal is still retried about 1, 4 and 11 days after its first attempt. PayPal renewals are unchanged: they are charged within the hour afternext_billing_at. Seenext_billing_aton the Subscription object.
Subscription webhooks
-
Improved — Every
subscription.*webhook (subscription.paused,subscription.resumed,subscription.cancelled,subscription.amount_changedandsubscription.plan_changed) now carries the subscription’s state as of the event:status,currency,amount_minor_units,net_amount_minor_units,tax_minor_units,has_net_price,next_billing_atandpending_change, read from the same state asGET /v1/commerce/subscriptions/{id}, with timestamps to the second like the events’ other fields. You no longer need to call back after each event to learn what the subscription now is.subscription.amount_changedandsubscription.plan_changedalso carryold_recurring_amount_minor_unitsandnew_recurring_amount_minor_units, the same values as their_centsfields, which stay. Nothing was removed or renamed.Details
- An instalment plan, which the Subscription API does not serve, carries no state:
subscription.pausedandsubscription.cancelledcarry none of it, andsubscription.resumed,subscription.amount_changedandsubscription.plan_changedkeep only thenext_billing_atorcurrencythey always carried. A delivery of an event that happened before this change carries none either. - On
subscription.amount_changedandsubscription.plan_changed,effective_atis still the prediction recorded when the change was made;pending_change.effective_atis the next renewal as of the event.
- An instalment plan, which the Subscription API does not serve, carries no state:
Net and gross amounts
- New —
POST /v1/commerce/offerstakes an optionalpricing.has_net_price:truewhenprice_minor_units,recurring_amount_minor_unitsandshipping_price_minor_unitsare net of tax and the tax is added at checkout,falsewhen they include it. Left out, the product’shas_net_priceapplies, as before. The offer records the value inpayment_plan_snapshot.has_net_price, so changing the product later no longer changes an offer already made. - New —
POST /v1/commerce/subscriptions/{id}/pricetakes an optionalhas_net_price:truestatesamount_centsnet of tax, and the tax is added at the rate the subscription was sold at;falsestates it with the tax included.no_changeis decided in that basis. - Changed — Action required if you change subscription prices: when
has_net_priceis left out,amount_centsis now read in the basis the subscription’s terms are set in, shown ashas_net_priceon the Subscription object, instead of always as including tax, as it was before. On a subscription sold net, anamount_centsof 10000 now bills 10000 plus tax. Sendhas_net_price: falseto keep stating the amount with tax included. - Fixed —
POST /v1/commerce/subscriptions/{id}/planprices the plan in the basis its product lists it in, the product’shas_net_price. A plan on a product priced net now bills its amount plus tax, as checkout does; before, it billed the plan’s net amount with the tax taken out of it. You send no amount here, so nothing changes in your request. It also takes an optionalhas_net_priceto state the plan’s basis yourself. The plan list your buyers switch from shows the same amount, so it now agrees with checkout for that plan. - New — The Subscription object and its
pending_changegainnet_amount_minor_units,tax_minor_unitsandhas_net_pricebesideamount_minor_units, which keeps its meaning: the recurring amount with tax included.
Checkout consents
- Removed · 2026-10-19 — COPE’s checkout page no longer offers the optional “subscribe to updates” box, on any checkout. Action required if you relied on it for marketing opt-in: ask for opt-in on your page and send
marketingincheckout.consentswhen the buyer opts in. See consents.
Offers
- Fixed · 2026-10-19 —
POST /v1/commerce/offersnow judges a product’s status and approval the same way checkout does. A published product edited in the dashboard, which stays on sale while COPE reviews the change (approval_statusapproved_changed), now takes new offers instead of being refused with422 product_unavailable. An edit throughPATCH /v1/commerce/products/{id}is unchanged: it still takes the product off sale and back to review, so offers are refused until COPE approves it and it is published again. As before, the one exception is anapprovedproduct of a business COPE trusts to skip re-review, which keeps its status and approval. A product that is inactive or archived, or whoseapproval_statusisreview,deniedordenied_changed, is still refused.
Commerce API
-
Changed —
GET /v1/commerce/paymentsnow lists sales newest first bycreated_at, then by ID, with or withoutstatus: the same order asGET /v1/commerce/refunds,GET /v1/commerce/chargebacksand the Transactions list in your dashboard. It used to order bycash_flow_at, and withstatusit listed sales without a funds date after the dated ones. Which payments the list returns is unchanged. Action required if you collect newly settled sales by reading the list until you reach a payment you already hold: instead passcash_flow_fromset to your last sync time (andcash_flow_toif you want a window) and read every page of that response. Do not stop at the first payment you already hold, because a sale created earlier can settle later and is listed by its creation time.Details
- Without
statusthe list holds settled sales only, so a sale whose funds date arrives while you page joins the list at itscreated_atposition and moves the later pages along by one. - A sale with
cash_flow_at: null, which only a request namingstatusreturns, now sits among the others by itscreated_at.
- Without
-
Removed · 2026-10-21 — The API reference no longer lists
customer_balanceandstripe_balanceas payment methods: they are gone from thepayment_methodfilter ofGET /v1/commerce/payments,GET /v1/commerce/refundsandGET /v1/commerce/chargebacks, and frompayment_methodsonPOSTandPATCH /v1/commerce/products. That product list also dropscard_present,interac_presentandcustom; a product sold on a card reader namesterminal. Nothing you send is refused that was accepted before: the filter still takes both balance names, and a product could not be saved with any of the five before this change. -
New — Read the currencies a business can price products in,
GET /v1/commerce/currencies. It returnssellable_currencies(whatpayment_plans[].currencyaccepts onPOST /v1/commerce/products),default_currency(the one COPE stamps on a plan sent without one),platform_currencies, andexchange_ratesfrom each platform currency the business cannot sell in into each one it can, at the rate checkout uses. It requires theproductspermission atread. See the API reference.Details
- Use it to pick a valid plan currency before creating a product, and to convert a catalog held in another currency instead of relabelling its amounts.
exchange_ratesis empty when the business already sells in every platform currency, and also when the rate provider is unavailable; the currency facts are still returned with a 200.rateis a decimal string at full precision andquoted_atis the time of the answer. Convert and round on your side; COPE’s checkout rounds up to the minor unit.
Checkout SDK & MCP server
- New —
cope-sdk0.1.5.^0.1.0takes it on your next install.ApiErrorCodedeclaresemail_domain_not_found, and its MCP endpoint tells the agent to ask the buyer for the correct address. Nothing else changes. - New —
cope-mcp0.1.5. It addsget_currencies, which readsGET /v1/commerce/currencies.COPE_API_BASE_URLnow accepts onlyhttps://api.cope.comandhttp://localhost; leave it unset, as the setup says. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.5; 0.1.4 keeps working. See MCP server for your store.
Documentation
Nothing in this section changes how COPE behaves; each entry documents a rule that already applied.- Improved — Send a
User-Agentheader on every API request. COPE’s network edge may refuse a request without one with a403whose body is not a COPE error and which carries noX-Request-Id. Action required if your HTTP client sends noUser-Agent: set one that names your integration. See Errors. - Improved — The webhook pages now name one deduplication key everywhere: the envelope’s
id, which the signature covers and every retry and replay repeats. TheX-Cope-Event-Idheader carries the same value but is not signed. Read header names case-insensitively; many frameworks lowercase them. See Webhook signing. - Improved — The API reference describes more fields:
refund_deadline_at(refunds through the API are possible for 180 days after a payment, whatever the product promises) andrefund_period_days,refund_period_b2c_daysandrefund_period_b2b_days(the money-back period promised to the buyer, which does not limit your refunds); the Subscription object’samount_minor_units(fixed for the subscription’s life, with the tax recalculated from it at each renewal) andnext_billing_at(when a renewal is charged); and a product’spayment_plans(editing a plan never changes a subscription already sold). The subscription price and plan changes state that a new change replaces a pending one, and that PayPal subscriptions and subscriptions with a quantity above 1 cannot be changed through the API. - Improved —
metadataoncart.order.completed, andorder.metadataon the payment events, state that the buyer can change the metadata only on a cart created with your publishable key or from a checkout link; on a cart created from an offer or with a secret API key it is locked. Embedded checkout says where to register an embed origin in the dashboard, and the Checkout SDK overview that the 1-click checkout link is available once COPE has enabled it for your business. - Improved —
POST /v1/commerce/subscriptions/{id}/priceand/plannow state when a change applies and when it is refused: it applies from the next renewal with nothing charged, credited or prorated now, and is refused with422 too_close_to_renewalwhen that renewal is 60 minutes away or less or already due, or withsubscription_not_eligibleandrenewal_date_unknownwhen no renewal date is known.too_close_to_renewalstates the 60 minutes. - Improved — Webhook deliveries state the retry schedule: up to 20 attempts, waiting 30 seconds and doubling to one hour between them, about 13 hours in all, with 10 seconds for your endpoint to respond to each.
- Improved —
POST /v1/commerce/offersstates that an offer withoutpricing.trial_daysgives the buyer the product’s own trial, under everyplan_type,one_timeincluded. Sendtrial_days: 0for no trial. - Improved —
POST /v1/commerce/offersstates whichcurrencya seller can be paid in: a currency COPE charges in that is also the currency of one of the seller’s payout bank accounts. The product’s own payment plans are not considered. Any other currency is refused with422 validation_failedonpricing.currency.
Week of October 12, 2026
Buyer email
-
Changed — A buyer email whose domain does not exist, such as
buyer@yahoo.con, is refused with422 email_domain_not_found, and the message names the domain: onPATCH /carts/{id}/buyer-identity(fieldemail), onPOST /prefilled-checkoutsandPOST /v1/commerce/checkouts(buyer_identity.email), and when the buyer starts paying.POST /v1/commerce/offersanswersvalidation_failedwitherrors[].codeemail_domain_not_foundonbuyer.email. COPE’s checkout page shows the buyer the message. Action required if you collect the email on your own page: show this refusal so the buyer can correct the address.Details
- A domain is refused only when DNS answers that it does not exist, or that it has no mail (MX) and no address (A or AAAA) record. When DNS cannot answer in time, the email is accepted.
- An email you set on a checkout or an offer is checked when you create it, not again when the buyer pays, because the buyer cannot change it.
Tax location
- Fixed · 2026-10-17 — Changing
billing_address.regiononPATCH /carts/{id}/buyer-identity(setBuyerIdentity()) now requires a reprice, as changingcountryorpostal_codealready did, so a reprice refused because the region did not match the postal code succeeds once the region is corrected. The region is the tax calculation’s state or province: when you changepostal_code, send the matchingregion, orregion: null. See Checkout SDK.
Recurring promo codes
- Fixed · 2026-10-15 — A promo code that is not limited to the first payment discounts every renewal and every instalment again, priced and taxed after the discount like the first payment. On those orders
line_items[].plan.next_payment_gross_centsinpayment.sale.succeededandcart.order.completedis the discounted renewal, and each renewal’spayment.sale.succeededcarriesline_items[].discount. Applying such a code is refused withbelow_minimum_chargewhen it would bring a renewal under the minimum charge. - Changed · 2026-10-15 — On a subscription with such a discount,
POST /v1/commerce/subscriptions/{id}/priceand the dashboard’s “Change price” treat the undiscounted amount as the current price: sending it is refused withno_changeand the discount stays; any other amount, the discounted one included, ends the discount.
Payment update links
- Changed —
POST /v1/commerce/subscriptions/{id}/payment-recovery-linksnow creates a link for any subscription that is trialing, active or overdue, so your buyer can replace their payment method before a card expires, without logging in. The link works once: after the buyer replaces the method through it, it stops working, and a second use at the same time is refused. On an overdue subscription it still pays what is overdue; if that payment waits for the buyer’s bank to confirm it, the link still lets the buyer confirm it, and nothing else. Create a new link for the buyer whenever that payment does not go through: it is declined, the buyer’s bank refuses or the buyer abandons the confirmation, or a bank debit or PayPal payment fails later. On an instalment plan that has ended with instalments still owed, the link pays one of them. A subscription that is not live (paused, cancelling, cancelled or ended) is refused withpayment_recovery_not_availableand the reasonnot_active;not_overdueis no longer answered. The “Copy payment update link” action on an order works the same way.
Checkout theme
- New — Force the checkout page’s colour theme.
theme(auto,lightordark; defaultauto, the buyer’s device setting) is taken when a checkout is created (POST /carts/{id}/checkout, and insidecheckoutonPOST /prefilled-checkoutsandPOST /v1/commerce/checkouts) and answered on the checkout object;?theme=on the checkout or embed URL sets it per load and works with the currentcope-sdk.cope-sdk0.1.4 declares it asCheckoutPayload.theme. It works inside the embedded checkout iframe, where your page cannot reach the buyer’s colour scheme.
Consents passed through the API
- Fixed · 2026-10-15 — The checkout page now honours consents you send in
checkout.consentsoncheckout()andcreatePrefilledCheckout(): it shows them ticked and locked and asks only for the required ones you did not send, so a buyer who accepted everything on your page can pay without ticking anything. The checkout lists what it holds inaccepted_consents(acceptedConsentsincope-sdk0.1.4). See consents. - Changed — The optional “subscribe to updates” box is offered only on a checkout created without consents. If you send consents, collect marketing opt-in on your page and send
marketingwhen the buyer opts in. - Changed — A subscription requires
auto_renewal_consent, as the checkout page always asked; the payment is refused with422 missing_auto_renewal_consentwithout it. COPE’s checkout page asks for it when you do not send it, so nothing changes for you unless you send consents for a subscription and want the buyer to skip the box: then send it too.
Payments, refunds, chargebacks and disputes
-
New — A chargeback now gets a credit note, and a won dispute, or a card refund that failed after it was paid out, gets a debit note that cancels the credit note. Debit notes are numbered in their own series (
DN-2026-000001). You download them from the order’s transaction activity, beside the invoice and the refund’s credit note; your buyer is not sent them. -
New —
payment.chargeback.created,payment.chargeback.reversedandpayment.refund.reversedcarryinvoice_number, the document’s number, and withpayment.refund.createdthey carrycorrected_documentandoriginal_invoice: the number and date of the document it corrects and of the sale’s invoice. -
Improved — A credit note now states the invoice it corrects, by number and date.
Details
- A chargeback’s credit note is issued only where the sale has a numbered invoice, and a debit note only where the credit note it cancels is numbered. A sale whose tax document you issue yourself gets neither from COPE. A refund keeps its credit-note number as before.
original_invoiceis sent only where the sale’s invoice is numbered. - The chargeback’s credit note is issued when the disputed amount is taken from your balance; a won dispute issues the debit note.
- An invoice’s
document_typecan now also readdebit_note. - Events sent before this change carry none of the new fields.
- A chargeback’s credit note is issued only where the sale has a numbered invoice, and a debit note only where the credit note it cancels is numbered. A sale whose tax document you issue yourself gets neither from COPE. A refund keeps its credit-note number as before.
-
New —
GET /v1/commerce/paymentsandGET /v1/commerce/payments/{id}takestatus(trial,pending,succeeded,failed), and the list takespayment_methodtoo. Each takes one value or several separated by commas. Withoutstatusyou get exactly what you got before: settled sales only. -
New —
GET /v1/commerce/chargebacksandGET /v1/commerce/chargebacks/{id}list chargebacks and the reversals that returned their money when a dispute was won, withtype,status,payment_methodandcreated_from/created_tofilters. Each names its dispute. -
New —
GET /v1/commerce/disputes/{id}retrieves a dispute by its processor’s id (Stripedu_…, PayPalPP-D-…): its state, reason, evidence deadline, and the sale and chargeback it concerns. -
Improved —
GET /v1/commerce/refundstakestype,status,payment_methodandcreated_from/created_to. Withouttypeit still lists refunds only;type=refund,refund_reversaladds the reversals, each the money of a refund that failed after it was paid out coming back to you. Every refund now saysreversed, and names itsreversalwhen it has one.Details
- Every
payment_methodname the filters take is listed in the API reference. - With
status, a sale can havecash_flow_at: null(no funds date yet); dated sales come first. Withoutstatus, it is always set, as before. - Chargebacks and disputes follow the API convention: references are
{object, id}, amounts areamount_minor_units, timestamps carry milliseconds. A chargeback’sdisputeis{object: "dispute", processor_id}; COPE publishes no id of its own for a dispute. - A refund reversal’s
amount_centsis positive; a refund’s stays negative.
- Every
-
Fixed · 2026-10-15 — A sale that is
pendingorfailednow reads as not refundable on Retrieve a payment and List payments (withstatus):refund_eligibility_stateisnot_refundable,total_refundable_amount_centsis0andrefund_deadline_atisnull, on the payment and on each entry ofpayment_chunks. It used to readrefundablein full, although no refund of a sale that has not succeeded is possible. See the API reference. -
Fixed · 2026-10-15 — A
pendingorfailedsale now carries inpayment_methodthe method Stripe reports for it: the one the buyer submitted (a Klarna redirect, a SEPA debit in processing) or the one that was declined. A sale the buyer never submitted a method for readsother. It used to readcarduntil the payment succeeded, whatever the buyer used, sopayment_method=klarnamissed every unpaid Klarna sale. Sales created from the release onwards are recorded this way.Details
- Unpaid sales that already exist are refiled when the release ships, from the Stripe responses COPE recorded for them at the time; COPE does not query Stripe again. An existing unpaid sale with no method in those responses reads
other. - A subscription’s first sale keeps the method it was recorded with (typically
card), because the subscription’s renewal fees are priced from it. - A PayPal or terminal sale keeps
paypalorterminal, and a paid sale is unchanged.
- Unpaid sales that already exist are refiled when the release ships, from the Stripe responses COPE recorded for them at the time; COPE does not query Stripe again. An existing unpaid sale with no method in those responses reads
Failed subscription payments
-
New — When an automatic retry of a card renewal fails and another retry is scheduled, the buyer receives an email in their language: the retry failed, when the next attempt is, that the subscription ends and access stops if the last attempt also fails, and a link to update their payment method and pay. The first failure keeps its own email, and the last failure is followed by the “subscription ended” email instead. The
payment.failedandpayment.attempt.failedwebhooks are unchanged.Details
- The email goes to the buyer only, never to your additional recipients, because its link lets the buyer change their payment method without logging in.
- Each failed retry sends at most one email. When several invoices of one subscription are unpaid, only the invoice the buyer was first told about sends it.
- An instalment’s email says the payment stays outstanding after the last attempt, since instalment plans are not cancelled for non-payment.
- A renewal waiting for 3-D Secure keeps its own reminders instead. PayPal subscriptions keep their earlier reminders until the PayPal change below is in production.
-
Changed — A PayPal renewal that fails is retried on days 1, 4 and 11 after its first attempt, as a card renewal is. If the last retry fails, COPE ends the subscription: access ends and
subscription.cancelledis sent. Paying at any point keeps the subscription running. -
Changed — PayPal buyers receive the same failed-payment emails as card buyers: the email for the first failure, with a link to update their payment method and pay, and the email after each failed retry. A payment the buyer starts by updating their PayPal account sends no such email, because they see its result on the page, and it does not use up a retry.
Details
- A PayPal instalment plan is never cancelled for non-payment. An instalment whose last retry fails stays outstanding, and the plan’s later instalments are still charged on their dates.
- The
payment.failedandpayment.attempt.failedwebhooks keep their shape;next_attempt_atfollows the new schedule.
PayPal
- New — PayPal checkout, and Venmo for eligible USD purchases, is available in production to the businesses COPE enables for PayPal, for one-time purchases and recurring plans. Sellers can refund a PayPal sale in full or in part from the COPE dashboard. Businesses not enabled for PayPal see no change.
Subscriptions
- Changed — Changing, pausing, resuming and cancelling a live subscription through the Commerce API is now available to every business by default, and buyers can switch an active subscription to another plan of the same product by default.
Webhooks
- Changed — The delivery log now keeps a delivery for 30 days after it succeeded or failed for good, which is also how far back you can replay it. A delivery that is still being retried is never removed. See Retention.
Dashboard
- New — Orders: “Pause payments” on an active subscription pauses it, and “Resume payments” on a paused one resumes it, each after you confirm. They follow the rules of the Commerce API’s pause and resume: nothing is refunded, and a paused subscription stays paused until you resume it. PayPal subscriptions do not offer them.
- New — Payouts: a payout refused because COPE’s platform balance could not fund it shows Retrying and is attempted again on each of the next three days; if the third retry is refused too, it is marked failed. A seller paid daily is not retried: their next daily payout pays them. A waiting retry is cancelled, and the payout marked failed, if the seller has since moved to daily payouts, their payout account changed, or their balance no longer covers the amount.
- Changed — Balances: a refund or chargeback of a sale whose money is still incoming or in reserve now takes it from that sale’s own incoming and reserve amounts, in proportion, instead of from your available balance, which therefore no longer goes negative for it. Refunds and chargebacks recorded before this release are unchanged.
Checkout SDK & MCP server
-
New —
cope-sdk0.1.4 is on npm (2026-10-15).^0.1.0takes it on your next install. It declaresCheckoutPayload.theme(theme),acceptedConsentsonCheckoutResultandPrefilledCheckoutResult(consents), and themissing_auto_renewal_consenterror code. Action required only if you build aCheckoutResultorPrefilledCheckoutResultyourself, for example in a test: addacceptedConsents, which is not optional. -
New —
cope-mcp0.1.4 is on npm (2026-10-15). It addslist_chargebacks,get_chargebackandget_dispute;statusandpaymentMethodonlist_payments, andstatusonget_payment; andtype,status,paymentMethod,createdFromandcreatedToonlist_refunds, whosetypeadds refund reversals. To use them, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.4; 0.1.3 keeps working. See MCP server for your store. -
New —
cope-sdk0.1.3 is on npm (2026-10-13).^0.1.0takes it on your next install.Details
- Action required if your page sets
baseUrlto anhttp://origin other thanlocalhost,127.0.0.1or[::1]: usehttps. Such an origin now throwsCopeErrorwhen the client is constructed. - Requests no longer follow redirects; the cart API never redirects, and a redirect now surfaces as a network error.
- The SDK’s MCP endpoint (
cope-sdk/mcp) now offers only the payment methods the cart can actually be paid with: every cart result carriespaymentMethodsfrom the cart’spayable_payment_method_types, and each line carriesplanType. A subscription, instalment or trial cart therefore no longer lists methods that cannot pay its later charges. Cart.payable_payment_method_typesandCart.recurring_payment_method_typesare now declared in the SDK’s types.
- Action required if your page sets
-
Improved —
cope-mcp0.1.3 is on npm (2026-10-13). Email addresses in error results are masked unless you setCOPE_MCP_PII=full, error results carry the same untrusted-data notice as other results, and requests no longer follow redirects. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.3; 0.1.2 keeps working. See MCP server for your store.
October 12, 2026 — production release
Everything listed under the week of October 5 is now live in production. These changes are what sellers and buyers notice.Failed subscription payments
- Changed — A card renewal that fails is retried on days 1, 4 and 11 after the first failure. If the last retry fails, the subscription ends: its open invoices are cancelled, access ends, and the business owner receives a “Subscription cancelled” email. A subscription is no longer paused after a failed payment. The buyer keeps access while the payment is being retried, and paying at any point keeps the subscription running.
- Changed — When the buyer’s bank asks them to confirm a renewal with 3-D Secure, the buyer receives reminders on days 1 and 4. If they have not confirmed by day 11, the subscription ends as above.
- Improved — On the payment page linked from a payment-failed email, a buyer asked for 3-D Secure confirms the payment with the card already saved, instead of entering a new card. “Use a different card” is still offered.
- Improved — A buyer whose instalment plan has ended with an unpaid instalment can pay it on the same page. Instalment plans are never cancelled for non-payment.
- PayPal subscriptions keep their current retry schedule.
Checkout
- Changed — A subscription, instalment plan or free trial offers only payment methods that can be charged again: cards, Link, and bank debits (SEPA, ACH, BACS, Canadian pre-authorized debit, Australian BECS). Methods that can only pay once, such as iDEAL, Bancontact, EPS and buy-now-pay-later, stay available for one-time purchases.
Dashboard
- New — Orders: “Copy payment update link” on an overdue subscription gives you a link to send the buyer. They open it without logging in, update their payment method and pay what is overdue.
- Changed — Team settings moved from Settings to Scale. A member with Team = Manage can create roles with any permission, invite people into them and change anyone’s role; the owner is always protected.
Seller emails
- New — The business owner receives “New sale”, “Payment received”, “Refund issued” and “Subscription cancelled” emails, in all 9 COPE languages. Invoice copies have their own notification, Invoice issued. See the week of October 5 for when each is sent.
Week of October 5, 2026
Commerce API
-
New — Create a checkout from your server with your secret API key.
POST /v1/commerce/checkoutsfixes the product, plan, buyer email and your reference, returns acheckoutobject with achk_id and acheckout_urlto send the buyer to, andGET /v1/commerce/checkouts/{id}reads it back. See Checkout from your server.Details
checkout_urlis in the create response only, and in a replay of it with the sameIdempotency-Key.Idempotency-Keyis required, and aplan_idmust be the plan’splan_id.- The buyer cannot change the email you set, or add, change or remove a line (
422 lines_locked). Yourmetadataandexternal_referencecannot be changed and arrive on the order’s webhooks. - An unregistered
success_urlorcancel_urlis refused withinvalid_redirect_url, and a reserved key insidemetadatawithreserved_metadata_key. - Once the buyer has paid, the checkout names its
order: confirm the order by that id.
-
New — List subscriptions,
GET /v1/commerce/subscriptions, returns your subscriptions in the order they last changed, oldest change first, so a sync can ask what changed since it last looked. It requires thesubscriptionspermission atread. See the API reference.Details
- Subscriptions are ordered by when their
updated_atmoved.updated_since(inclusive) andupdated_until(exclusive) bound the window, andstatusandproduct_idnarrow it. - Only changes at least 120 seconds old are served:
updated_untildefaults to now minus 120 seconds, a later value is refused with 422validation_failed, and the response returns theupdated_untilit served. - Pages hold up to
limitsubscriptions (default 25, at most 100). Whenhas_moreis true, passnext_cursorasstarting_after. - The cursor is opaque and carries the first request’s window and filters, so every subscription in the window is returned exactly once, including many that share one
updated_at. One that changes while you page is returned by your next window instead. - For a nightly sync, store the
updated_untilof the last walk you finished and pass it as the next walk’supdated_since. Read the window withoutstatus:statusfilters on the status a subscription has now, so a filtered window does not report a subscription that left that status. - Each entry is the subscription object Retrieve a subscription returns, without
amount_cents(readamount_minor_units). - An unknown query parameter,
pageandper_pageincluded, is refused with 422.
- Subscriptions are ordered by when their
-
New — Retrieve a subscription (
GET /v1/commerce/subscriptions/{id}) and every subscription change now returnupdated_at, in UTC with milliseconds (2026-10-08T09:30:00.123Z). Nothing else in the response changes.Details
- It moves whenever another field of the subscription changes, and can also move when none visibly did, for example after a change attempt that was refused.
- A change can become visible with an
updated_atslightly earlier than the moment you read it (by up to the time a write takes to commit), and changes can share one value. If you sync by time, overlap your window rather than starting exactly at the last value you saw.
-
New — Offers take your own
external_reference(1 to 255 characters) andmetadataonPOST /v1/commerce/offers, return them on the offer, and send them on the order’s webhooks once the buyer pays. Both are optional. See Prices: payment plans and offers.Details
metadatais an object of your own keys with the same limits as a cart’s metadata: 50 entries, 4 levels, 64-character keys, 8 KB.- They arrive in
metadataoncart.order.createdandcart.order.completed, and inorder.metadataon everypayment.*event. Webhook payloads do not change shape. - The buyer cannot change them on the offer’s checkout. Identify the order by
order.id, which retrieving the offer returns once it is paid, since a checkout link can carry the same reference. external_referenceis reserved: sending it, or a key COPE writes itself such asintended_payment_method, insidemetadatais refused with 422reserved_metadata_key.- An offer that carries neither is returned exactly as before, with neither key.
-
New — List payments takes
subscription_id, a subscription’sps_id, and returns only that subscription’s payments: the first charge and every renewal. Retrieve a payment now numbers each entry ofpayment_chunksand names its subscription. See the API reference.Details
subscription_idcombines with the other payment filters and paginates as before. An id that is not one of your subscriptions, including an instalment plan’s, is refused with 422validation_failed.- Each
payment_chunksentry carriespayment_number(1for the checkout purchase, then one more per renewal or instalment) and, on a subscription line,subscription: {object: "subscription", id}.subscriptionis left out on a one-time or instalment line. - Nothing else in either response changes.
-
New — List orders and Retrieve an order take
state(one or more ofdraft,pending,succeeded,failed, comma-separated) to reach orders that have not completed, with each one’s latest card decline inlast_payment_error. The order list also takescreated_fromandcreated_to, with the same grammar as the payment list’s. See the API reference.Details
- Example:
?state=draft,pending,failed. Withoutstatenothing changes: only completed (succeeded) orders are listed, and any other order answers 404 on retrieve. - Naming
stateaddslast_payment_errorto each order that has one: the latest card decline recorded on any of its payments (payment_id,attempt,failure_code,decline_code,failure_message,failed_at). It is left out of an order with no recorded decline. - An unknown state is refused with 422
validation_failed.
- Example:
-
Changed —
state,created_fromandcreated_toon the order endpoints used to be ignored and are now applied. Action required if you already send them:created_fromorcreated_tonow narrows the order list and a malformed value answers 422, andstateon Retrieve an order restricts which order can be found, so?state=drafton a completed order answers 404. See the API reference. -
New — Retrieve a payment returns
attempts, every declined attempt to charge it, and Retrieve an order returns the sameattemptson each entry of itspayments. Stripe payments only. See the API reference.Details
- Attempts are listed oldest first, each with
payment_id,attempt(counted from 1),failure_code,decline_code,failure_messageandfailed_at. The list is empty when no attempt was declined. - List payments serves settled payments only, so read a payment that is still being declined on its order.
- Attempts are listed oldest first, each with
-
New — Send a buyer a payment recovery link for an overdue subscription:
POST /v1/commerce/subscriptions/{id}/payment-recovery-links. The buyer opens it without logging in, replaces the payment method and pays what is overdue, on the same page COPE’s payment-failed email links to. See the API reference.Details
- Requires
subscriptions: writeand anIdempotency-Key. urlcarries a secret and is shown once: do not log or store it.- A link expires after 7 days, or earlier, once the subscription is no longer overdue.
- A repeat under the same key returns the same link under a new
url, and the earlierurlstops working. Earlier links, including the ones COPE emailed, keep working. - A subscription with nothing to recover is refused with
422 payment_recovery_not_available. - At most 10 links are created for one subscription in 24 hours.
- Instalment plans are not covered.
- Requires
-
Improved — A refund refused with 422 by
POST /v1/commerce/payments/{id}/refundsnow explains its code indetail, for example “The seller’s balance cannot fund a refund right now.” forinsufficient_seller_balanceand “The amount is more than is left to refund on this payment.” forrefund_exceeds_limit. Keep branching oncode:detailis written for people and its wording may change. See the API reference.Details
- Every code used to answer the same text, “The refund was refused for this payment.”.
- The codes, the HTTP status and the rest of the body are unchanged.
-
New — The subscription object, and its
pending_change, carryamount_minor_units: the same value asamount_cents, under the name every other COPE money field uses. See the API reference. -
Deprecated —
amount_centson the subscription object, and on itspending_change, is deprecated. Action required: readamount_minor_units, which carries the same value under the name every other COPE money field uses.Details
- Retrieve a subscription and every subscription change still return
amount_cents. - List subscriptions does not carry
amount_centsat all, top level or inpending_change.
- Retrieve a subscription and every subscription change still return
-
Changed — Every timestamp on the subscription object now carries milliseconds:
2026-10-09T09:30:00.000Zwhere it was2026-10-09T09:30:00Z. The instants are unchanged. Action required if you compare these strings to stored ones or match them with a pattern: allow the fraction.Details
- Applies to
next_billing_at,paused_at,cancel_at,cancelled_at,created_atandpending_change.effective_at, on Retrieve a subscription, on List subscriptions and on every subscription change. - Until now one object mixed two precisions:
updated_atalready carried milliseconds while the others carried whole seconds. - The shape is still ISO 8601 / RFC 3339 in UTC with
Z; only fractional seconds are added. A parser that reads RFC 3339 reads both.
- Applies to
-
Fixed · 2026-10-11 — A 422
validation_failedproblem now carries a machine code in eacherrors[].code, as Errors documents, and a top-leveldetail. Action required if you matched the old sentence incode: match the new code instead.Details
- Before, a rule such as a product description’s minimum length answered its sentence as the code (
"code": "Description must be at least 250 characters"), repeated the field name indetail("Description Description must…") and left the top-leveldetailnull. It now answers"code": "too_short"with"detail": "Description must be at least 250 characters". - The top-level
detailjoins theerrors[].detailsentences with;. - Every
errors[].codeis snake_case. A rule with no more specific code answersinvalid. - Other codes introduced:
inclusionandnot_enabled(productpayment_methods),too_many(images,product_attachments),invalid_scheme,invalid_host,userinfo,not_an_origin,backslash,local_hostandimmutable(an embed domain’sorigin), andunsupported_content_typeandtoo_large(an attachment’sfile). - The HTTP status, the top-level
code,typeandparamare unchanged.detailis written for people and its wording may change.
- Before, a rule such as a product description’s minimum length answered its sentence as the code (
-
Fixed · 2026-10-10 — A payment that has been charged back now reads as not refundable on Retrieve a payment and List payments:
refund_eligibility_stateisnot_refundable,total_refundable_amount_centsis0andrefund_deadline_atisnull, on the payment and on each entry ofpayment_chunks. See the API reference.Details
- It used to read
refundablewith its full amount and a deadline, while a refund of it was refused with 422refund_not_available(“Already charged back”). The refusal is unchanged. not_refundableis a value these fields already carried; every other payment reads as before.
- It used to read
Checkout SDK & cart API
-
New —
cope-sdk0.1.2 is on npm (2026-10-11). It reads RFC 9457 problem errors and adds types for the new cart fields and error codes below;^0.1.0takes it on your next install, and nothing else changes. See the package’sCHANGELOG.mdon npm.Details
- Every request sends
X-Cope-Sdk-Versionwith the SDK’s version. COPE records it from its next production release, to tell when no integration still runs an earlier version. A cross-origin page already sends a preflight forX-Cope-Key, and the new header adds no round trip. - An
application/problem+jsonerror body is read:CopeApiError.codeis the problem’scode,messageitsdetailandfieldtheparamof its first field-level member, where 0.1.1 reportedcode: "unknown". The cart API does not answer problem+json yet. - The types gain
ignored_keyson the cart,payment_plans[].uuid, and the error codesinvalid_request,metadata_locked,attribution_locked,buyer_identity_locked,lines_lockedandcheckout_release_retry.
- Every request sends
-
New — Cart responses carry
payable_payment_method_types: the payment methods the cart can be paid with, as COPE decides them, as Stripe payment-method types andpaypal. The checkout page can offer fewer, for the buyer’s country, currency and business status, never more.Details
- It applies the seller’s selection (card is always included), card alone on an instalment cart, only methods that renew on a subscription, instalment or trial cart, and any method blocked for the seller.
- The field is additive. The MCP endpoint in
cope-sdk0.1.3 reports it to the agent aspaymentMethods.
-
Changed — Subscription, instalment and trial carts now offer and accept only payment methods that can pay their later charges: cards, the bank debits SEPA, ACH, BACS, Canadian pre-authorized debit and BECS, and Link. Cart responses list the Stripe types in
recurring_payment_method_types. A one-time cart offers what it offered before.Details
- Hosted checkout no longer offers such a cart iDEAL, Bancontact, EPS, buy-now-pay-later methods or other one-off methods, which could take the first payment but not the next.
recurring_payment_method_typesholdscard,kr_card,sepa_debit,us_bank_account,acss_debit,au_becs_debitandbacs_debit. Link pays such a cart but is not listed. PayPal, not a Stripe type, is not listed either: whether it is offered is decided as before.- The field is the same on every cart and is additive.
cope-sdk0.1.1 and 0.1.2 return it on the cart without declaring it in their types.
-
New —
setBuyerIdentity()(PATCH /api/cart/v1/carts/{id}/buyer-identity) now lists the keys it ignored inignored_keys. Action required: checkignored_keysnow; a later release will refuse such keys with an error, on a date not yet set. See Basic redirect flow.Details
- A key it does not take was, and still is, dropped while the rest of the payload is saved. Before, a cart could leave the call without the buyer’s tax location and fail only at
reprice()with422 missing_tax_location. ignored_keyslists each key by its path, at most five:tax_locationfor a nestedtax_location: { country, postal_code },billing_address.statefor a key inside an address,consents.0.versionfor a key inside a consent,shipping_addressfor an address sent asnull(which does not clear the stored one), andconsentsforconsents: null. It is absent when nothing was ignored.- A body that is not a JSON object is refused with
400 invalid_request(it previously saved nothing and answered 200, or failed with a 500), and acountrythat is not a string with422 validation_error. cope-sdk0.1.0 and 0.1.1 returnignored_keyson the cart without declaring it in their types; 0.1.2 declares it.
- A key it does not take was, and still is, dropped while the rest of the payload is saved. Before, a cart could leave the call without the buyer’s tax location and fail only at
-
Changed — On an offer’s checkout, the buyer can no longer change what the offer was created with: the cart API refuses it with
422 metadata_locked,422 attribution_lockedor422 buyer_identity_locked. Action required if your code writes to an offer’s cart: handle these refusals. See What the buyer cannot change on an offer.Details
metadata_locked: a request that would change the offer cart’smetadata.attribution_locked: one that would re-attribute it (attribution,?aff=); anyattributionis refused.buyer_identity_locked: one that would change a buyer detail the seller set, other than the checkout language.- Re-sending the stored metadata or a stored buyer detail is still accepted, and a detail the seller left empty can still be filled in.
- Cart responses carry
buyer_email_locked,truewhen the seller set the email. cope-sdk0.1.1 reports each asCopeApiError.code; 0.1.2 adds the three to theApiErrorCodetype.- Carts created from a product link, a checkout link, a prefilled checkout or the SDK are unchanged.
-
Changed — On an offer’s checkout, and on a checkout created from your server, the buyer can no longer add, change or remove a line: the cart API refuses it with
422 lines_locked, whichcope-sdk0.1.2 adds toApiErrorCode. Action required if your code changes lines on such a cart: handlelines_locked. See What the buyer cannot change on an offer and Checkout from your server. -
New — Cancelling a checkout (
POST /api/cart/v1/checkouts/{checkout_id}/cancel) can now answer503 checkout_release_retrywhen Stripe or PayPal did not answer in time. Action required if you cancel checkouts from your code: handle503 checkout_release_retry. See Core methods.Details
- The cart API also takes an optional
release_open_checkoutquery parameter, used by COPE’s checkout pages. Integrators normally omit it, andcope-sdkdoes not send it. release_open_checkoutis accepted onPOST /api/cart/v1/carts/{cart_id}/checkout, on the line writes (POST /api/cart/v1/carts/{cart_id}/lines, andPATCHandDELETE /api/cart/v1/carts/{cart_id}/lines/{line_id}) and onPATCH /api/cart/v1/carts/{cart_id}.- Without it nothing changes: a request on a cart whose checkout is open still answers
422 cart_not_active. - Only the value
trueopts in. Then a checkout the buyer abandoned is cancelled and the request applies, unless a payment is moving (409 checkout_payment_in_flight) or Stripe did not answer in time (503 checkout_release_retry: retry the same request). cope-sdk0.1.2 addscheckout_release_retrytoApiErrorCode.
- The cart API also takes an optional
-
Removed —
payment_plans[].public_idwas removed from cart API product responses (getProduct(),GET /api/cart/v1/products/{id}) on 2026-10-04; this notice should have been published then. It was a deprecated alias ofpayment_plans[].uuidwith the sameplan_value. Action required: readpayment_plans[].uuidinstead; nothing you stored needs to change, and code that still readspublic_idgetsundefined. -
New —
cope-sdk0.1.1 is on npm. The class is nowCope:import { Cope } from "cope-sdk", or the globalCopeon a script tag.CopeCartstays exported as a deprecated alias of the same class, so code written against 0.1.0 keeps working, and the Checkout SDK examples now useCope. -
Changed — In
cope-sdk0.1.1,CartLine.idis typednumber, which is what the API always sent;updateLine()andremoveLine()take that number and still accept a string of its digits. Action required if you keep a line id in astring-typed variable: that code stops compiling. -
Changed — In
cope-sdk0.1.1, the insecure-page error readsCOPE SDK requires HTTPS...(wasCopeCart SDK requires HTTPS...). Action required: update any code that matches on the message. -
New — In
cope-sdk0.1.1,createPrefilledCheckout()takescollectBuyerIdentityAtCheckoutand returnsfieldErrorswhen the API attaches any, andsetBuyerIdentity()takesphoneandlocale. -
Fixed · 2026-10-05 — In
cope-sdk0.1.1, an asctimeRetry-Afteris read as GMT, soCopeApiError.retryAfterno longer shifts by the host’s time-zone offset. A value that is neither seconds nor an HTTP date isnull. -
Improved — In
cope-sdk0.1.1,cope-sdk/mcp’supdate_lineandremove_lineaccept the line idget_cartreturns (0.1.0 refused it),get_cartreturns the lines withtotalsPendinginstead of failing when the cart has no buyer location yet, andstart_checkoutreturnsbuyerNext, which tells the agent what the buyer does on the checkout page. See MCP for AI shopping agents. -
Fixed · 2026-10-10 — A cart line id in
PATCHandDELETE /api/cart/v1/carts/{cart_id}/lines/{line_id}must now be exactly the integer the cart returns: any other value, such as12abcor012, answers404 not_found, where before it was read by its leading digits and12abccould reach line 12. Action required if you sent non-integer line ids: check thosePATCHandDELETErequests. See Core methods.Details
- Ids written as the cart returns them are unaffected.
- COPE’s dashboard and buyer-account requests that name a record by a numeric id read it the same way.
-
Fixed · 2026-10-10 — While Stripe still needs an action on a payment (
requires_action: true,order_status: requires_action, for example a 3-D Secure challenge),POST /api/cart/v1/orders/{id}/confirm_paymentno longer returns the success page or your thank-you page:redirect_urlis left out andcustom_thank_you_pageisnull. Action required: act onnext_action, then confirm again.Details
statusis stillsuccessthere, as before: it says the payment intent checked out, not that the payment is made, so readorder_status.- Nothing else in the response changes.
-
Fixed · 2026-10-09 — A prefilled checkout now drops
clerk_user_idfrom themetadatayou send, as creating a cart already did, and refuses a body that is not a JSON object (for example[1]ornull) with422 validation_errorinstead of failing with a 500. The rest of your metadata is stored unchanged;clerk_user_idis a key COPE reserves for its own use (see your own reference on an order). -
Fixed · 2026-10-11 — Confirming a card payment on the server (
POST /api/cart/v1/checkouts/{checkout_id}/payment-sessions/{payment_session_id}/server-confirmation) with anIdempotency-Keyalready used for a different request now answers422 idempotency_body_mismatch, not503 payment_provider_error. Action required: send a newIdempotency-Keyfor each new card.Details
- A typical case is reusing the key of the card that was just declined.
422 idempotency_body_mismatchis the answer the cart API already gives when a key is reused with a different body. The old503 payment_provider_errorread as a Stripe outage to retry.- A Stripe outage still answers
503 payment_provider_error.
Webhooks
-
New — New event
payment.attempt.failed: one for every declined attempt to charge a Stripe payment, the first included.payment.failedis still sent once per payment, at its first decline, so subscribe to one of the two: with both, the first decline reaches you twice.Details
- At checkout, that is each card the buyer tries. On a renewal or instalment, it is each attempt Stripe makes.
attemptcounts the payment’s declines from 1.will_retryandnext_attempt_atsay whether and when Stripe tries again; at checkout they are alwaysfalseandnull.payment_methodnames the method that was declined.- A decline reported after the payment already succeeded is still sent.
- It carries the same
order(with itsmetadata),line_itemsand decline fields aspayment.failed. - PayPal payments did not send it when it was introduced; PayPal renewals and instalments now do (see below).
-
New —
payment.failedgainsattempt, which declined attempt the event reports, andin_checkout, whether the buyer was on the payment page. Events sent before this change carry neither field.Details
attemptis counted from 1. It is normally1, because the event is sent once per payment at its first recorded decline, and it is left out when COPE has no record of the decline.in_checkoutistruefor a checkout charge declined on a card, not a renewal or instalment invoice. It isfalsefor an invoice charge, for any other payment method, and when the decline does not name the method.
-
Improved — PayPal renewals and instalments now send what card payments send:
payment.failedonce per declined cycle,payment.attempt.failedfor every declined attempt, andsubscription_renewal: trueonpayment.sale.succeeded. No payload changes shape.Details
payment.failedcarriesprocessor: "paypal",order.metadataandline_items[](product,payment_number, andsubscriptionon a subscription line).payment.attempt.failedcarrieswill_retryandnext_attempt_at, giving COPE’s next attempt.- On PayPal every attempt is a payment of its own, so
attemptcounts the declines COPE has published for that renewal or instalment, from 1, your buyer’s own retries after updating PayPal included. Eachpayment.attempt.failednames its ownpayment.id, andpayment.failednames the cycle’s first. subscription_renewal: trueis set on a paid PayPal renewal, subscription trial conversion or later instalment, as on a card renewal.- How often COPE retries a PayPal payment, and when it ends a subscription, is unchanged.
-
New — Each line of
payment.sale.succeededandcart.order.completednow carriespayment_plan: {object: "payment_plan", id}: the payment plan the payment was charged on, by itsplan_id.planand everything else in both payloads is unchanged.Details
- It is the same value the cart API and the Commerce API give that plan, and the same reference the
cart.cart_line.*events send. - It stays the same after the plan is deleted. After a plan switch, a renewal names the plan in force.
- It is left out when the line was not sold on a plan (an offer or a one-click upsell).
- It is the same value the cart API and the Commerce API give that plan, and the same reference the
-
Changed —
payment_method.typenow names the method a new payment was made with, such asideal,revolut_payorlink, where it used to sayotherfor every method outside eight known values. Action required: treat the field as an open string.Details
- Applies on
cart.order.completedand on everypayment.*event exceptpayment.attempt.failed, and topayment_methodon payments and refunds in the Commerce API. - The eight values
card,klarna,affirm,afterpay_clearpay,sepa,ach,paypalandterminalkeep their meaning. A Stripe Terminal reader takes cards only and staysterminal. otherremains for a method COPE does not name yet, and payments recorded earlier keep their value until they are reclassified.payment.attempt.failedkeeps naming the declined method by its Stripe type, such assepa_debitorcard_present.
- Applies on
- New — The production IP addresses webhook deliveries are sent from are published for receivers that allowlist. See Source IP addresses.
-
Changed — An endpoint is now disabled automatically after 72 hours without a successful delivery, up from 16, and re-enabling it restarts that check. See Retries.
Details
- It is disabled when a delivery failed and was first attempted at least 72 hours ago, with no successful delivery first attempted after it.
- After you re-enable an endpoint, a failure from before the re-enable no longer turns it off at the next check. Sending
active: trueto an endpoint that is already enabled does not restart the check.
Dashboard
-
Improved — The webhook details view now shows the request each delivery’s latest attempt sent: the whole envelope and the four headers COPE sets,
Content-Type,X-Cope-Signature,X-Cope-TimestampandX-Cope-Event-Id, with the digest inX-Cope-Signaturemasked. What COPE sends is unchanged. See the delivery log.Details
- Headers HTTP adds in transit, such as
HostandContent-Length, are not shown. - It previously showed only the event’s
dataand two headers, which made a correct delivery look like a different envelope. - Deliveries sent before this change still show the event data only.
- Headers HTTP adds in transit, such as
Seller emails
-
New — The business owner now receives a “New sale” email for a checkout sale, and a “Payment received” email for each later subscription or instalment payment, with the products, shipping, the total the buyer paid, any promo code and the buyer. Webhook payloads do not change.
Details
- A one-click upsell the buyer accepts is a sale of its own and gets the same email.
- Notification groups that subscribe to Sale receive this email instead of a copy of the buyer’s receipt. For a trial signup, which charges nothing, they still receive the copy.
- A copy of the buyer’s invoice now has its own notification, Invoice issued, switched on for every group that already subscribed to Sale. Credit notes stay with Refund processed.
-
New — The business owner and the notification groups that subscribe to Refund processed now receive a “Refund issued” email when a refund is made by your API integration, by COPE support, or directly at Stripe or PayPal. Refunds you make yourself in the COPE dashboard send no such email. Webhook payloads do not change.
Details
- When it is sent, those groups receive it instead of a copy of the buyer’s refund confirmation. Credit notes are still copied to them.
-
New — The business owner and the notification groups that subscribe to Subscription cancelled now receive a “Subscription cancelled” email when a buyer cancels, when COPE support cancels, or when renewal payments fail and the subscription ends. Cancellations you make yourself send no such email. Webhook payloads do not change.
Details
- When it is sent, those groups receive it instead of a copy of the buyer’s cancellation email.
MCP server for your store
-
New —
cope-mcp0.1.2 is on npm (2026-10-12). Your assistant can now read a checkout you created from your server and the order it became, list the subscriptions that changed in a time window for a sync, list one subscription’s payments (its first charge and every renewal), and list orders by state — draft, pending, succeeded or failed — with each order’s latest card decline. Without a state, orders are listed as before: completed ones only. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.2; 0.1.1 keeps working. See MCP server for your store. -
Improved —
cope-mcp0.1.1 is on npm and does what 0.1.0 did. Its README and MCP server for your store now say thatsend_offer,resend_offerandcancel_offercarry no idempotency key: the offer’s own state keeps each from happening twice, and none is retried. To use it, change the pinned version in your MCP client’s configuration tocope-mcp@0.1.1; 0.1.0 keeps working.
Documentation
-
Fixed · 2026-10-07 — Prefilled checkout: a line’s
planIdis the plan’splan_ID frompayment_plans[].uuid; the page previously told you to send the plan’s integerid. The integer is still accepted, andcope-sdk0.1.1 still declaresplanIdas a number; the page explains both. -
New — Checkout SDK overview documents
purchasableand everypurchase_block_reasonvaluegetProduct()returns, includingpending_approvalfor a product awaiting approval, which cannot be checked out. These fields were previously described only in this changelog. -
Fixed · 2026-10-07 — The docs no longer say that metadata your server sets is out of the buyer’s reach. The checkout page holds the cart’s credential, which can replace the metadata of a cart started from a link or the SDK before payment (an offer’s cart is locked), so match a paid order to your record by
order.idand never grant anything onexternal_referencealone.Details
- Corrected in Checkout SDK overview (“A link’s value belongs to the buyer”), Prefilled checkout, where it comes back, the integration quickstart, and the
order.metadataandmetadatadescriptions of thepayment.*andcart.order.completedevents. - Use metadata to group events with your own records; identify the order by
order.id. Webhook payloads do not change.
- Corrected in Checkout SDK overview (“A link’s value belongs to the buyer”), Prefilled checkout, where it comes back, the integration quickstart, and the
-
Fixed · 2026-10-05 — Checkout SDK: the field table no longer tells you to convert a line id with
String(). Fromcope-sdk0.1.1,lines[].idis typed as a number andupdateLine()andremoveLine()take it as it is.
Week of September 28, 2026
Commerce API
-
Changed — Orders and promo codes now have one ID each, the one every other COPE surface already uses (2026-10-02). The
idof an existing order on the dashboard’s order list, and of an existing promo code on the Commerce API, changed value: the prefix stays (ord_,promo_) and the value is shorter. Action required: the IDs these surfaces returned before no longer resolve, so look the object up again if you stored an old one.Details
- The old IDs kept resolving for a transition period, which has ended: an order or promo code is addressed only by the ID these surfaces return now.
-
Changed —
POST /v1/commerce/productsnow creates the product withstatus: active(previouslyinactive), the same as a product created in the dashboard.approval_statusis stillreview, and the product cannot be bought until COPE approves it. Action required if you treatstatus: activeas on sale: checkapproval_statustoo.Details
- Unchanged: a later
PATCH /v1/commerce/products/{id}or image/attachment upload on a product that is not approved still sets it back toinactiveandreview.
- Unchanged: a later
-
Fixed · 2026-10-02 —
POST /v1/commerce/productsrefuses a plan amount (first_payment_amount_cents,next_payments_amount_cents,shipping_price_cents) sent as a string or a decimal, such as"2500"or25.0, with400 invalid_requestnaming the member. Previously such a value was stored a hundred times larger:"2500"became a 2,500.00 price. Action required: send an integer number of minor units, as the reference always specified. -
Fixed · 2026-10-02 —
POST /v1/commerce/promo-codesandPATCH /v1/commerce/promo-codes/{id}refuse adiscount_centsorvanity_prices[].discount_centsthat is not an integer with422 validation_failed. Previously a decimal such as12.99was stored truncated, as 12. -
Fixed · 2026-10-02 —
POST /v1/commerce/offersrefuses a negativepricing.shipping_price_minor_unitswith422 validation_failed. Previously the offer was created with the negative fee in itspayment_plan_snapshotand charged no shipping. -
Fixed · 2026-10-02 —
GET /v1/commerce/refunds/{id}andGET /v1/commerce/refundsnow return a refund in every status; a refund the payment provider had not confirmed yet used to answer404and was missing from the list. Action required if you total refunds from the list: count onlysucceeded.Details
- That included a refund whose ID
POST /v1/commerce/payments/{id}/refundshad just returned. - Read
status:pendinguntil the provider confirms, thensucceeded, orfailedwhen nothing was returned. A refund that succeeded can still becomefailedif the provider later reports it returned. - The list is now ordered by
created_at, newest first (previously by when the money moved), so a refund that settles while you page does not change pages.
- That included a refund whose ID
-
Fixed · 2026-10-02 —
POST /v1/commerce/payments/{id}/refundsno longer reads a body of a type it does not parse as “no amount”.{"amount_cents": 500}sent astext/plain, asapplication/octet-streamor as a+jsontype used to arrive empty and issue a full refund. Action required: send the body as JSON (application/jsonor a+jsontype).Details
- A
+jsontype is now read as JSON. Any other such body, or aContent-Typethat is not a media type, is refused with 415unsupported_media_typebefore anything is refunded, and the sameIdempotency-Keycan carry the corrected request. - A query parameter, such as
?amount_cents=500beside an empty body, is refused with 422 like an unsupported body field instead of being ignored. - Everything that was already refused keeps its answer, and an empty body or a JSON object without
amount_centsstill refunds everything still refundable.
- A
-
Fixed · 2026-10-02 —
POST /v1/commerce/offersno longer puts internal IDs in thedetailof a422 vendor_not_payout_eligibleorproduct_unavailable; the product refusal names the product by itsprod_ID.codeis unchanged: branch oncode, not ondetail. -
Fixed · 2026-10-02 —
GET /v1/commerce/productslists newest first, and a tie on creation time is broken by ID, so paging through the list neither repeats nor skips a product (previously the order was unspecified).GET /v1/commerce/offers,GET /v1/commerce/promo-codesand a promo code’s redemptions gain the same tie-break.
Checkout SDK & cart API
-
New — The Checkout SDK is on npm as
cope-sdk0.1.0. It includescope-sdk/mcp, an MCP endpoint you mount on your own server so a buyer’s AI agent can build a cart in your store and hand the buyer a checkout link. See MCP for AI shopping agents. -
Changed — The Checkout SDK class is renamed
Cope, withCopeCartkept as an alias. This shipped incope-sdk0.1.1, in the week of October 5. -
Changed — A product awaiting approval (
approval_statusreview,deniedordenied_changed) now reads as not purchasable before checkout:getProductreturnspurchasable: falsewithpurchase_block_reason: "pending_approval"(previouslytrue/"none"), andaddLinerefuses it withnot_saleableandblock_reason: "pending_approval". Action required: handlepurchasable: falseand that refusal, and stop readingdenial_reason.Details
- Previously both calls succeeded and checkout then refused the cart with
product_unavailable, which checkout still returns for such a product. - The buyer product response no longer carries
denial_reason.
- Previously both calls succeeded and checkout then refused the cart with
-
Fixed · 2026-10-02 —
createPrefilledCheckout()now refuses whataddLine()andcheckout()refuse: a plan in a currency you can no longer accept payments in (plan_currency_not_settleable), a plan whose billing interval exceeds two years (interval_exceeds_max), and lines that mix products with different VAT handling (mixed_vat_mode_cart). Action required: handle these codes fromcreatePrefilledCheckout(). See Prefilled checkout.Details
- A checkout it opens for products whose VAT you handle now says so in
vat_mode, as one opened bycheckout()does.
- A checkout it opens for products whose VAT you handle now says so in
Webhooks
-
New — Every webhook delivery’s envelope gains
occurred_at: when COPE recorded the event, to the millisecond, repeated unchanged by every retry and replay, whilecreated_atstays the time of each attempt. Action required if your receiver rejects unknown envelope keys: acceptoccurred_at. See Event envelope.Details
- Use
occurred_atto judge freshness; it is not a strict order.
- Use
-
New —
payment.failednow carries your checkout metadata asorder.metadata, as the sale, refund, chargeback and dispute events do, andline_items, one entry per line the payment covered. Tie a failed renewal to your own reference, and to the subscription and cycle it belongs to, from the event alone. See payment.failed.Details
order.metadatais{}when you sent none; the top-levelmetadatais not sent.- Each
line_itemsentry has itsproduct, itspayment_number, and, when one has been opened for the line, thesubscriptionwith the sameps_ID aspayment.sale.succeeded. - A failed first purchase usually names no subscription; recognise it by
payment_number1. - Events sent before this change omit both fields.
-
New —
payment.refund.createdandpayment.refund.reversedgaininitiated_via: how the refund was started. Treat a value you do not recognise as unknown. See Who started a refund.Details
- Known values:
api(your secret API key),dashboard(a person signed in to COPE, on the web or in the COPE mobile app),support(COPE support, on your behalf) andprocessor(a refund made directly at Stripe or PayPal). - It is a string, not a closed list.
- On
payment.refund.reversedit describes the refund being reversed. - COPE fills it only when it knows, so it is often absent; Who started a refund lists when.
- Known values:
-
Fixed · 2026-10-03 — A webhook’s
id, and theX-Cope-Event-Idheader that repeats it, are now the same on every send of an event, including bulk replays (POST /v1/webhooks/replay-jobs) and a re-send from inside COPE, so deduplicating onidcatches every repeat. The format is unchanged, a lowercase UUID.Details
- This applies to newly sent events. Events already delivered keep their ids, and the delivery log shows each delivery’s id as it was sent.
MCP server for your store
- New —
cope-mcp0.1.0 is on npm: an MCP server you run on your own computer so Claude, Cursor or another MCP client can read your store with your API key, and make changes you confirm when you turn them on. See MCP server for your store.
Documentation
These corrections describe what the API already does; no behaviour changed.-
Fixed · 2026-09-28 — Rotating the signing secret no longer tells you to recreate an endpoint to get a new signing secret. Rotate it in place with
POST /v1/webhooks/endpoints/{id}/secret-rotations; the old secret stops verifying at once, with no overlap. -
New — Prices: payment plans and offers documents how to sell at a price decided per buyer, including a recurring one: a catalogue checkout sells the prices your payment plans define, and an offer (
POST /v1/commerce/offers) prices one product for one named buyer. Offers do not acceptmetadataorexternal_referenceyet. -
Fixed · 2026-10-02 — The Checkout SDK examples now match what
cope-sdk0.1.0 sends:setBuyerIdentity()takescountryandpostal_codeat the top level (not insidetax_location), andgetProduct()takes the product’sprod_ID, withproduct.uuidas a line’sproduct_id. See Checkout SDK overview.Details
- The overview now states that plan and cart line IDs on the cart API are integers, that plan amounts named
*_centsare decimal strings in major units, and the shape of the cart API’s error body.
- The overview now states that plan and cart line IDs on the cart API are integers, that plan amounts named
-
New — Prefilled checkout documents
createPrefilledCheckout(): its input, the idempotency key it derives from your reference, and who can call it. -
Fixed · 2026-10-02 —
POST /v1/commerce/payments/{id}/refundsnow lists every code it can refuse with, includinginsufficient_seller_balance, explains the seller-balance rule, and states that a refused refund is not stored against itsIdempotency-Key, so the same request can be retried later under the same key. -
Fixed · 2026-10-03 — The Checkout SDK pages show the
withdrawal_waiverconsent besidebuyer_tos. A cart holding a product that does not ship (a digital product) needs it before payment, or the payment is refused with422 missing_withdrawal_waiver. See consents. -
Fixed · 2026-10-03 — The API reference names the permission each operation requires and lists the
503 user_not_ready/tenant_not_readyanswer every operation can give. Error examples show a realrequest_id, which is also the response’sX-Request-Id. See Errors. -
Fixed · 2026-10-03 — Product create and update document every field they accept and the allowed values of
product_type,plan_type,intervalandcheckout_type.Details
- The
Idempotency-Keyheader is optional on these two operations, on the upload session and on the two media attaches. Their errors are alwaysapplication/problem+json, and a key reused with a different body is409 idempotency_conflict. - Offer create lists its
500 tax_calculation_failedand thevendor_not_payout_eligible,product_unavailableandinvalid_parameterrefusals. - Updating a product, or adding, removing or reordering its media, takes it off sale and back to review.
- The
-
Fixed · 2026-10-03 — A refund’s
amount_centsis documented as the negative number the API returns: a refund of 12.50 EUR reads-1250. -
Fixed · 2026-10-03 — List operations name the older parameter names they still accept:
itemsandlimitforper_page, andcurrent_pageforpage. -
Fixed · 2026-10-03 — Payments are documented as listed once their funds availability date is known. Chargebacks are not available through this API. On an offer,
buyer_profile.address.line1andcitycan benull. -
Fixed · 2026-10-03 — The webhook management API reference is in the navigation and no longer lists
GET /v1/openapi.jsonorGET /v1/platform/errors, which the API does not serve.Details
- It documents the
409,422,429and503answers each operation gives, the 2,048-characterurllimit, and howsinceis applied on a replay job. - Each item of a problem’s
errorsnames the refused field inparam.
- It documents the
-
Fixed · 2026-10-03 — The quickstart states that an unregistered embed origin fails checkout creation with
422 embed_origin_not_allowed, that the thank-you URL carriesorder, and that a publishable key iscope_pk_followed by 48 hexadecimal characters. -
Fixed · 2026-10-03 — Prefilled checkout lists the
buyerIdentityfields it takes, says thatconsentsandlocaleinside it are ignored, and documentsforbidden_field,cart_not_active, theIdempotency-Keyrefusals andidempotency_error. -
Fixed · 2026-10-03 —
mor_posturehas a field row on the ten event pages whose payload carries it.payouts.transfer.initiatedno longer shows a payload, because the event is not sent yet. Onpayment.failed,checkoutandsupply_classificationare marked as not populated.
Week of September 21, 2026
Checkout
- New — Thank-you pages receive the same parameters on every payment method: your checkout metadata as one
metadata[<key>]parameter per key,affiliatewhen the buyer came through an affiliate link, andorder, the order ID. The URL is kept within 2,000 characters, withmetadata_truncated=truewhen a key had to be left out. See Your own reference on an order. - Changed — The thank-you URL’s order ID is now
order(previouslyorder_id), andorder_uuidis no longer added. Action required: readorderon your thank-you page.
Commerce API
-
New —
POST /v1/commerce/subscriptions/{id}/planaccepts a plan on another billing cycle, such as monthly to yearly or every three months, on the same product and in the same currency. The period the buyer already paid for is kept: nothing is charged untilpending_change.effective_at, where the new cycle starts.Details
- The subscription stays
activethroughout, with the new plan and its cadence inpending_change.planuntil that renewal bills it. plan_not_availableis no longer answered for a different interval or interval count.
- The subscription stays
-
Changed — Every subscription operation (retrieve, and the price, plan, pause, resume and cancel writes) now answers one Subscription object. The writes no longer return the attempt, and the subscription no longer carries
latest_change. Action required: read the Subscription object from every write, and stop reading the attempt andlatest_change.Details
- Fields:
id,object, a closedstatus, thebusiness,orderandline_itemit belongs to as{object, id}, theplanandamount_centsin force,currency,next_billing_at,paused_at,cancel_at,cancelled_at,created_at, andpending_changefor a price or plan change waiting for the next renewal.
- Fields:
-
Changed — A subscription’s price or plan change is its
pending_changeuntil a renewal bills the new terms, on every payment method, andeffective_confirmed_aton the change-list entry records that renewal. A renewal that bills nothing (a 100% discount) does not count. -
Changed — Entries of
GET /v1/commerce/subscriptions/{id}/changesgaincreated_at, name plans asplan: {object, id}instead ofplan_id, carryfailureonly on afailedentry, and no longer carrysubscription_idorrequested_by. Action required: readplan.idwhere you readplan_id, and stop readingsubscription_idandrequested_by. -
Changed — A subscription’s
plan.idnow names the plan it was sold on from the start, not only after a plan change, andGET /v1/commerce/subscriptions/{id}/changesnames the plan on both sides of an entry where it is recorded. Thesubscription.plan_changedwebhook’sold_planis filled the same way.Details
- The id is
nullwhen no recorded fact names the plan: for example, a subscription sold through an offer, a plan since deleted from the product, or one sold before plans were recorded.
- The id is
-
Changed — A subscription’s plan reference now names its object
payment_plan(previouslyplan), the name thesubscription.plan_changedwebhook already uses: onplanandpending_change.planon the Subscription object, and onfrom.planandto.planonGET /v1/commerce/subscriptions/{id}/changes. The field names and theplan_…ID are unchanged. Action required if you check these references’object: expectpayment_plan.
Webhooks
- New —
cart.order.completednames the subscription each subscription line bought, asline_items[].subscriptionwith itsps_ID: the ID the subscriptions API accepts, and the one everysubscription.*event andpayment.sale.succeededcarry. It is left out on one-time and installment lines.
Week of September 7, 2026
Checkout
- New — Buyers can use PayPal for eligible installment-plan checkout and one-time trial checkout, for the first payment or trial authorization, while COPE keeps the authorization needed for the later charge.
- Improved — Direct checkout presents payment plans with selected-plan terms, installment schedules, VAT-inclusive amounts and amount-aware pay buttons, and recovers completed checkouts more steadily.
- Improved — PayPal checkout has a cleaner button handoff, clearer declined-payment guidance, trial totals that show
0.00due today, one buyer-facing message for PayPal payment failures, and payment-method details on trial success pages. - Improved — Checkout success pages for one-time trials explain that no payment is taken yet, show the scheduled charge, and use localized wording across supported languages.
- Improved — Buyer email addresses that cannot receive mail are rejected before payment, and permanent email delivery failures are no longer retried indefinitely.
- Improved — Buyers and creators in countries without postal systems are no longer blocked by a postal-code field their country does not use, in checkout and product setup.
- Fixed — Buyers can switch payment methods after abandoning one payment attempt.
- Fixed — PayPal receives one row per purchased line item, with the buyer’s selected quantity.
- Fixed — Loading states no longer cause layout jumps while direct checkout prepares payment options.
- Fixed — Eligible buyers who gave consent see post-purchase one-click offers after checkout succeeds.
Webhooks
- New —
cart.order.completedcarries your checkout metadata, so you can match completed COPE orders to your own checkout sessions.
Subscriptions & payments
- Improved — Each PayPal subscription can keep its own PayPal account, and overdue subscriptions retry promptly after the buyer updates PayPal.
Dashboard
- New — Finance views show vendor-managed promoter commissions, with a balance memo, per-payment reconciliation and clearer order-level settlement context.
- Improved — Invited admins can work in the selected business after accepting an invitation; businesses still control whether Team settings are available.
- Improved — Growth Hub commission calculations use a consistent net basis for vendor-managed promoter commissions on eligible sales and refunds.
Emails
- Improved — Order confirmation and invoice emails have simpler confirmation actions, clearer total labels, gross shipping amounts and localized payment terms on invoice lines.
- Fixed — Withdrawal decision emails show buyers either the approved or the rejected outcome, instead of contradictory decision text.
Week of August 31, 2026
Commerce API
- New — Offer writes: create, send, resend and cancel offers, with documented retry behavior for idempotent offer creation.
- New — Create full or partial refunds with
POST /v1/commerce/payments/{id}/refunds.
Checkout
- Improved — Direct checkout is enabled across supported flows, with a refined mobile checkout footer and clearer installment totals before payment.
- Improved — PayPal checkout has clearer buyer-facing errors, the official PayPal monogram, faster button readiness, stronger seller capability checks and safer returning-buyer context.
- Improved — Stripe applies its own eligibility checks for buy-now-pay-later methods offered automatically, while COPE’s checkout safeguards stay in place.
Dashboard
- New — Business team access: business owners can invite team members, manage pending invitations, and let trusted admins work in the business without sharing the owner’s login.
- Improved — Growth Hub partnership onboarding has clearer promoter invitation, acceptance, activation and post-registration recognition flows.
- Fixed — New physical products are no longer offered, while existing physical-product checkout, subscription and renewal flows keep working.
- Fixed — Unsupported payment-plan positions are rejected cleanly instead of failing during save.
Community
- Improved — Community calendar and challenges have steadier month navigation, a more consistent create-event modal, and translated challenge strings across supported locales.
Emails
- Fixed — Buyer emails and order views show course access instructions and multi-quantity installment or subscription amounts that match the purchase.
Week of August 24, 2026
Commerce API
- Improved — The payments list supports reconciliation: each payment returns
created_at(the sale timestamp) besidecash_flow_at(when funds became available), the list takescreated_from/created_toandcash_flow_from/cash_flow_todate ranges and an exact-matchbuyer_emailfilter, andper_pageon this endpoint accepts up to 100 (previously 25).
Checkout
- New — Venmo is an eligible PayPal checkout option for supported USD purchases, with wallet-specific confirmation details and saved Venmo authorization for eligible recurring carts.
- Improved — Selecting PayPal takes the buyer directly to PayPal, a cancelled checkout no longer appears as a failed payment, and confirmation pages show wallet and address details when they apply.
- Improved — Eligible buyer options stay visible for installment plans and non-card payment methods when a seller has opted into installments or payment capabilities are still loading.
- Fixed — Repricing safeguards stop buyers from completing payment against an outdated seller price.
- Fixed — Completed orders grant access whether the buyer returns through the immediate checkout path or the completion webhook.
Dashboard
- New — Phone Offer price calculations show the applied tax rate, so creators can explain the tax amount quoted to a buyer.
- Improved — PayPal seller controls show clearer account readiness messages, handle disconnects more safely, and offer refund actions that follow the seller’s current PayPal capabilities.
- Improved — PayPal refunds can be partial, and a refund PayPal rejects for insufficient balance gets a clear response.
- Fixed — Creator setup details: KYC capability alerts, product-card copy messages, optional payment-plan fields, course deadline validation, promo-code creation dates and Phone Offer plan editing.
Community
- New — Community admins choose which surfaces, such as Members, Calendar, Challenges, Leaderboards, Courses and Library, are shown and reachable in each community.
- Fixed — Course buyers who have not completed creator onboarding reach their purchased courses instead of being sent through creator setup.
Emails
- Fixed — Order confirmations, invoice emails and refund confirmations label and display the order ID consistently.
Documentation
- Fixed — The Commerce API reference matches live behavior, including dashboard and webhook identifier formats, documented error responses for invalid inputs, media-upload requirements, and fields the API already accepts or returns.
Week of August 17, 2026
Commerce API
- New — The read endpoints for orders, payments, refunds and invoices are available:
GET /v1/commerce/orders,/payments,/refunds,/invoices, plus retrieve by id for each. Existing API keys work unchanged: no new key, no settings change and no migration is needed. - New — The order list returns completed orders only; draft, pending and failed checkouts are not exposed. All four lists paginate with
pageandper_page(maximum 25; larger values are clamped) and return apaginationobject withtotal_pages,current_page,per_pageandtotal_count. A page number beyond the last page returns the last page, so iterate untilcurrent_pageequalstotal_pagesrather than untildatais empty.
Documentation
- Changed — The Commerce API reference lists only operations the API serves; operations not yet available are left out until they ship.
Week of August 11, 2026
Checkout
- Improved — Confirmation pages for trials, active subscriptions, cancelled subscriptions, and subscriptions ending after the paid-through period show accurate charge and access information.
- Improved — Trials and multi-quantity orders are clearer: trial badges before checkout, visible quantities in checkout and order views, and quantity-aware subscription amounts.
- Fixed — Buy-now-pay-later checkout for shipped orders keeps eligible payment methods available through confirmation when buyer location details are complete.
- Fixed — Buyers are not blocked by address requirements for a payment method they did not choose.
- Fixed — A delayed postal-code lookup from a previous country can no longer overwrite the new billing address.
- Fixed — Unsupported zero-value or below-minimum purchases cannot complete as paid transactions.
- Fixed — Address autocomplete is accessible, and its suggestions stay visible and attached to the correct field.
Subscriptions & payments
- New — Creators can change the recurring amount of eligible active PayPal subscriptions.
- Improved — PayPal subscriptions are more reliable across trial conversion, renewal charging, seller capability sync and recurring charge diagnostics.
- Fixed — Multi-quantity subscription and installment totals, reminder amounts, schedule entries and renewal charges match the quantity the buyer purchased.
- Fixed — First-payment-only promo codes on subscriptions return recurring amounts to the full undiscounted tax basis after the first charge.
Dashboard
- New — A standalone VAT liability addendum page, with in-portal reminders when a creator needs to re-accept current terms before liability transfer can apply.
- Improved — Promo-code setup gives clearer guidance for discounts in other currencies and warns when a fixed discount only applies to the base currency.
- Improved — Phone Offer setup disables empty currency selections and explains when settlement onboarding is needed before pricing becomes available.
- Improved — Promotions views scope promoter links, products, product stats and order context to the selected business.
- Improved — Payout reconciliation issues are isolated, and payout requests return a clear status instead of blocking unrelated sellers.
- Fixed — Vendors can resend an invite to an existing COPE user and see the resend cooldown clearly.
- Fixed — Vendors and promoters see aligned revenue, commission, status, transaction IDs and last-sale context for the same partnership.
- Fixed — Duplicate promo codes show a specific field-level rejection instead of a generic failure.
- Fixed — Promoter commission and product-stat reporting show earnings under the correct affiliate profile, and incoming amounts no longer stay hidden after invite acceptance.
- Fixed — Product creation and editing details: localized placeholders, German creator copy, thank-you-page tooltips, narrow plan cards, location autocomplete, and product-required validation for promoter invites.
Community
- New — Paid community memberships: a full community create and edit flow, buyer checkout for paid access, automatic membership grants after purchase, and access removal when an eligible withdrawal or subscription end applies.
- New — Community gamification settings, with a dedicated settings page and a master toggle for community points.
Account & sign-in
- New — Emailed sign-in codes are a supported second factor for new-device verification, so eligible users can complete sign-in without a separate authenticator or SMS factor.
Branding & links
- Changed — COPE branding in the cart app and the public API reference.
- Changed — Email footer Terms and Privacy links resolve to the current
www.cope.comlegal pages. - Changed — Buyer-facing COPE links in receipts and recovery pages use the current
cope.comandapp.cope.comdestinations.
Week of August 4, 2026
Checkout
- New — A refund policy link on checkout and public footers makes buyer-facing refund terms easier to reach before purchase.
- Improved — Active buyer pricing paths in checkout and Phone Offers use COPE’s unified tax calculation, keep authoritative zero-tax outcomes, and fail visibly when tax cannot be calculated safely.
- Fixed — Changing the billing country resets a country-specific billing address.
- Fixed — An invalid tax address gets a validation response instead of an ambiguous tax failure.
Subscriptions & payments
- New — PayPal for recurring subscriptions and trial subscriptions: buyer approval, saved PayPal re-authorization from subscription settings, renewal handling and cancellation.
- Improved — PayPal recurring charges, trials, revoked-consent recovery and renewal declines follow the buyer’s actual PayPal authorization state.
Dashboard
- New — Growth Hub and Promotions are in production, giving creators and promoters affiliate management, promoter earnings and promotion performance views.
- New — Creator payout pages show an estimated arrival date beside when a payout is initiated.
- Improved — Promotions order and transaction views are business-scoped, with clickable promotion order rows, richer promoter order overviews, clearer pending-commission context, and revenue and commission columns for promo-code performance.
- Improved — Creator setup preselects the business country from the visitor’s region when it is supported, and keeps any manual selection.
- Fixed — Unsupported tax codes cannot be saved, and payment-plan numbers stay within supported bounds.
- Fixed — Creators can clear an upsell funnel, and a blank shipping price is treated as zero.
- Fixed — Creators no longer receive false account-paused KYC emails.
Community
- Improved — About and Rules show consistently inside communities, with Rules below About.
Emails
- Improved — Affiliate invite emails have clearer collaboration copy, vendor identity, localized guidance, and per-product affiliate links when product-specific promotion is available.
Account & sign-in
- Fixed — Email and SSO submissions show progress and no longer submit a password alternative twice.
Documentation
- New — Community API documentation, with community OpenAPI references and webhook event pages for memberships, posts, comments, channels, events, invites, gamification and library activity.
Week of July 28, 2026
Checkout
- Improved — An English checkout selection is saved correctly for receipts and withdrawal-rights emails.
- Improved — Embedded checkout retries approved-origin policy checks before failing closed.
- Improved — In in-app browsers, changed totals are handled server-side and card authentication uses a WebView-compatible flow.
- Improved — Tax calculation and filing use COPE’s registered platform origin when a product has no specific origin address.
Dashboard
- New — Promoters can open an order from promotion transactions and review their own commission, vendor, attribution and promoted product details, without buyer details.
- New — Creators can reassign the affiliate on an order; commission terms for future recurring payments are kept after an affiliate is changed or removed.
- New — The second-payment offset is optional in the product and Phone Offer installment editors.
- Improved — Payment Providers settings replace the broader KYC section label and keep internal PayPal tracking references out of seller-facing account details.
- Improved — Reassigned recurring commissions and promoter order views follow the correct earner and attribution context.
- Fixed — Creators can create and load businesses after signing in without refreshing.
- Fixed — Recoverable failures processing Stripe’s verification webhooks can be reprocessed instead of being treated as completed.
- Fixed — Phone Offers follow the selected product or business currency instead of falling back to USD.
Community
- Fixed — Community requests that could fail while the service was starting.
Emails
- Improved — Italian, Dutch, Polish, Portuguese and Japanese subject lines across transactional templates.
Week of July 21, 2026
Checkout
- Improved — PayPal is hidden where recurring, installment or trial billing cannot be supported, and checkout stops offering it when a seller can no longer receive PayPal payments.
- Improved — Subtotal, included-tax, estimated-tax and reverse-charge VAT labels are clearer across product pages, hosted checkout, receipts, invoices and subscription flows.
- Improved — Valid EU VAT IDs resolve inline, unavailable validation falls back to charging VAT, and placeholder company names are no longer shown to buyers.
- Fixed — Buyers can reach COPE’s current Terms, Privacy Policy, Legal Notice and Accessibility pages from checkout and related public pages.
- Fixed — Buyers see a clear unavailable-payment state when no supported method remains for the selected seller and currency.
- Fixed — Recurring tax is based on the buyer’s destination instead of the seller’s origin.
- Fixed — During country-VAT service outages, checkout fails safely instead of completing an EU consumer checkout with missing VAT.
- Fixed — For B2B Phone Offer payments, company names carry into Stripe billing details and vendor transaction details.
Webhooks
- Improved — The dashboard and the docs give webhook signature snippets that verify the timestamped
X-Cope-Signatureformat live deliveries use. - Fixed — Event catalog requests no longer hit transient unavailable states, and queued deliveries keep processing after recoverable delivery errors.
- Fixed — Out-of-order Stripe refund and dispute events retry cleanly, and dispute reporting recovers when payment records arrive later.
Dashboard
- New — Clearer KYC guidance while creating and publishing products, with draft-saving prompts and a direct path to complete verification before launch.
- New — A business-name column in creator and affiliate promotion views, across approved and pending tabs.
- Improved — PayPal-verified creators are recognized across product publishing, verification badges, KYC banners and checkout availability.
- Improved — Payment verification labels show whether a business is verified for Stripe, PayPal or both, and the PayPal button renders more steadily in checkout.
- Improved — Creators who disconnect and reconnect PayPal can complete verification without stale onboarding sessions or unnecessary popup windows.
- Improved — Link, promo-code and Phone Offer sales stay in the right attribution views, promoter share links use stable attribution IDs, and incoming commissions appear in the correct payout currency.
- Improved — Growth Hub and Promotions: invite-decision confirmation, clearer filtered empty states, corrected commission display and cleaner vendor partnership tables.
- Fixed — Repeated saves after a KYC publish gate update the saved draft instead of creating duplicate products.
- Fixed — Terminal Readers no longer fall back to English in supported creator locales.
- Fixed — Support-contact phone validation and formatting in creator settings.
Week of July 14, 2026
Checkout
- Improved — PayPal and Stripe payment-method availability is filtered per currency and refreshed on demand when creator payment settings change.
- Improved — The Stripe Payment Element shows earlier, with fewer iframe remounts in hosted checkout.
- Fixed — Checkout phone hints match the selected country, and collected phone numbers appear on receipts, invoices and refund confirmations.
- Fixed — Subscription checkout for products without trials no longer processes or emails a purchase as a trial subscription.
- Fixed — German reduced-rate VAT uses exact statutory rates in checkout, invoices, receipts and subscription updates.
- Fixed — Long business website URLs no longer break checkout setup during payment onboarding.
Commerce API
- Fixed — Lapsed offers show as expired consistently in creator views and public offer responses.
Dashboard
- New — A refreshed creator onboarding experience, with a guided “Almost there” questionnaire and updated Getting started pages for creator and community setup.
- New — Eligible creators can create products and accept checkout with PayPal verification, without waiting on Stripe KYC.
- New — Notifications when a product is approved or denied.
- Improved — Fewer false “failed to load” states when creating a first product while account data finishes syncing.
- Improved — Clearer subscription cancellation status labels and close-button wording.
- Improved — The support chat follows the active account language.
- Fixed — Stripe onboarding no longer shows outdated KYC status or requests deprecated capabilities.
Community
- Improved — The community calendar has updated layouts, event dialogs, navigation and localized copy.
Emails
- Fixed — Subscription emails use the creator’s business brand instead of generic placeholder sender copy.
Week of July 7, 2026
Checkout
- Improved — Live Stripe dark-theme updates, clearer prefilled billing-address behavior, and card payments for Phone Offer checkouts.
- Improved — Tax calculation for EU B2C purchases, with country-rate fallbacks when the primary tax calculation returns zero.
- Fixed — Blocked or stale buy-now-pay-later payment sessions cannot be reused for checkout.
- Fixed — Sessions are kept when a response sets more than one cookie.
- Fixed — Tax estimates for partial billing addresses in regions where state or province is required.
Dashboard
- New — Creators can delete their account from settings, after payout-balance checks.
- New — KYC action guidance in the creator portal and by email, showing what needs attention before payouts or account capabilities are affected.
- New — Support contact settings for buyer-facing support details.
- New — Self-service VAT liability transfer for eligible Non-ESS products, with a plain-language addendum summary before acceptance.
- New — Product-level promotion performance: per-product affiliate links, sales, revenue and commission context.
- Improved — Separate sales and promotion transaction views, with payment-context details for promotion transactions.
- Improved — Separate sales and promotion order views, with promoter-facing vendor and commission context.
- Fixed — Klarna, Affirm, ACH, SEPA and other payment methods no longer appear as generic card payments in transaction rows.
- Fixed — Repeated saves no longer duplicate uploaded product images.
- Fixed — Product cards show internal names, so creators can tell products apart.
- Fixed — Course lesson paragraph spacing in the editor and the student lesson view.
Community
- Improved — Member directories, admin sorting, clearer filters and complete localized community strings.
Emails
- New — Subscription payment reminder emails for overdue or upcoming subscription payments.
- Fixed — Invoice PDFs give German buyers a labeled, sequential invoice number.
Week of June 30, 2026
Commerce API
- New — Product list and retrieve responses document the
phone_collectionfield.
Checkout
- New — Buyer withdrawal access for eligible EU orders, with receipt email links and Japanese localization.
- Improved — Buyer phone validation no longer blocks checkout, billing intervals over two years show translated guidance, and single product images fit cleanly.
- Improved — Buyer subscription management shows clearer cancelled states, recurring-amount labels, next billing dates and pending cancellations, and supports updating the payment method.
Webhooks
- Changed — Payment dispute and chargeback webhook schemas match the payloads COPE sends.
Dashboard
- New — Complete quiz-builder and course-settings translations across supported course locales.
- Fixed — Affiliate invite delivery, with corrected invite event contracts and absolute invite links.
Community
- Fixed — Re-uploaded community avatars and covers appear immediately.
Emails
- Improved — Subscription emails have localized price-change actions, brand footers, payment-plan labels and Japanese invoice links.
Legal pages
- Removed — The defunct EU ODR platform link from public terms pages.
Week of June 23, 2026
Checkout
- New — Full Phone Offer payment-plan support in checkout: clearer creator editing, buyer-facing payment schedules and total plan price disclosure.
- Improved — The buyer’s selected checkout language is kept through order creation, so order and payment confirmation emails use it.
- Fixed — Phone Offer checkout shows the configured installment or recurring plan instead of a one-time fallback.
Dashboard
- Improved — Buyer accounts that already own a business can reach creator tools.
- Improved — Creator fee messaging keeps progress to the next tier visible and hides the next tier’s fee rate.
- Fixed — Webhook pages for accounts without an active business show a localized, actionable empty state.
Community
- Fixed — Missing community translations added, and unavailable community controls hidden, so public community pages and chat flows stay consistent.
Emails
- Fixed — Receipts and invoices for physical orders show shipping lines correctly.
Account & sign-in
- Improved — COPE branding on the sign-in and sign-up screens, with a crisper logo in Safari.
Week of June 16, 2026
Webhooks
- New — Payload contracts for
payment.dispute.opened,payment.dispute.wonandpayment.dispute.lost, with CloudEvents metadata, schema IDs, payload fields and example events. - Improved — Order, sale and refund webhook pages describe raw attribution signals such as first-click references, Phone Offer IDs and promo codes.
Dashboard
- New — Growth Hub promoter management: a Configure Promoter page, updated affiliate link and promo-code panels, mobile views, and per-product sales and revenue metrics.
- Fixed — Create Affiliate validation messages appear in the seller’s selected language.
Emails
- New — A buyer confirmation page and action-required email for a subscription cancellation requested on the buyer’s behalf, so the buyer confirms before it is scheduled.
- Improved — Subscription price-change and cancellation-confirmation emails have clearer alert styling, branded footers and aligned calls to action.
- Fixed — Subscription management and cancellation links in lifecycle emails land on the correct COPE app.
- Fixed — Order and refund receipts show the correct localized payment-plan label for subscriptions and installments instead of one-time payment copy.
Account & sign-in
- Improved — The COPE logo sits inside the sign-in card.
Documentation
- New — A vendor integration quickstart covering dashboard setup, checkout installation, webhook confirmation and launch checks.
- New — This changelog, with dated weekly sections.
- Improved — Simpler navigation around the live checkout and webhook guides.
Week of June 9, 2026
Checkout SDK
- New — Checkout SDK
@copecart/sdk0.2.0 (the packagecope-sdklater replaced), with the embedded checkout support iframe-based buyer flows need.
Checkout
- Improved — Buy-now-pay-later options are hidden when the seller country or order amount does not support them.
- Improved — Richer product description editing and buyer rendering.
- Fixed — Checkout navigation and reload edge cases that could leave buyers on stale pages.
Subscriptions & payments
- New — Buyer subscription management is easier to reach, with localized subscription pages and clearer recurring-subscription filtering.
- Improved — Subscription cancellation and price-change messages show clearer access dates and localized labels.
Community
- Improved — Community feed rendering and navigation.
Documentation
- New — Ticketing event documentation for scanner and ticket lifecycle events.
- Improved — Refreshed webhook event pages and schema links.
Week of June 2, 2026
Checkout
- New — Terminal checkout and reader management for in-person payments.
- New — Buyers see their refund deadline and can open credit notes in order views.
- Improved — Confirmation screens rely on trustworthy checkout state instead of ambiguous redirects.
- Fixed — Buyer-facing totals with a promo discount stay currency-safe.
- Fixed — Localized order payment-method labels, including fallbacks for missing and unknown methods.
Community
- Improved — Inactive sidebar areas are hidden for members.
- Fixed — Realtime community chat recovers after connection drops or browser wake-ups.
Documentation
- New — Checkout SDK documentation for redirect checkout, embedded hosted checkout, iframe mount behavior, trusted postMessage events, fallback behavior and troubleshooting.
- Improved — docs.cope.com focuses on external, developer-facing guidance.
Week of May 26, 2026
Checkout
- New — The embedded checkout foundation for iframe checkout flows, with SDK support and integration guidance.
- New — Japanese checkout locale, and dashboard controls for checkout locale allowlists.
- Improved — Currency presentation across product pages, buyer-selected currencies and payment-plan labels.
- Improved — Japanese buyer-journey translations and more complete localized checkout and payment-method copy.
- Fixed — Framing headers let approved embedded checkout origins render correctly.
- Fixed — Stale plan currencies and presentment metadata no longer push checkout totals away from server-calculated prices.
Dashboard
- New — A daily payout cadence for creators.
- Improved — Product-specific affiliate links and clearer promotion management.
- Fixed — Support chat identity for signed-in users.
Week of May 19, 2026
Checkout
- New — Groundwork for hosted checkout in an iframe, with iframe stability checks and guarded frame policies.
- Improved — Presentment totals follow server-calculated repricing in the buyer’s selected currency.
- Improved — Trial badges in checkout product summaries.
- Fixed — Embed ordering issues that could affect iframe flows.
Dashboard
- New — Settings improvements for fees and copying business identifiers.
- Improved — Affiliate and promo-code management, with copy actions and product-link updates.
Branding
- New — The COPE brand across public-facing surfaces.