How it fits together

1. Build the order from your server: one API call creates the cart (one line per item, each with its seller), the order that wraps it and a signed payment link.
2. Send the buyer to the hosted page with the link you received, or with a link you sign yourself that carries the cart identifier.
3. The page charges the whole cart once on your processing merchant and marks the cart as paid.
4. We stamp every cart line with the transaction, the paid date and the fee snapshot, and the order moves to Paid. Your notification URL is called as usual.
5. Sellers are settled from their lines, and refunds are recorded per line.

Before you start: your program must be set up as a marketplace on the Platform model with a processing merchant, your sellers must be linked to the program, and a cart with lines of several sellers needs the program's mixed-cart rule switched on. Your account manager does this for you.

Call CreateMarketplaceOrder on the OMS.svc V2 service, logged in as your processing merchant (application token, credentials token and request signature as on every V2 call). The call creates the cart, the order and the payment link together and returns them.

Each line

Response

Building the cart step by step instead: the Shop.svc SetCart operation accepts SellerMerchantNumber on every item and returns the cart cookie; GetCartByIdentifier reads the cart back with the seller, the paid date and the settlement of every line. You then wrap the cart in an order with CreateFullOrder and build the link yourself as in step 2.

{
  "request": {
    "CurrencyIso": "EUR",
    "OrderName": "Order 1001",
    "Reference": "1001",
    "RedirectUrl": "https://shop.example.com/thank-you/1001",
    "Installments": 1,
    "Lines": [
      { "SellerMerchantNumber": "7001234", "Name": "Blue mug", "Price": 12.50, "Quantity": 2, "VatPercent": 17 },
      { "SellerMerchantNumber": "7005678", "ProductId": 4411, "Quantity": 1 },
      { "Name": "Gift wrap", "Price": 3.00, "Quantity": 1 }
    ]
  }
}

{
  "IsSuccess": true,
  "Code": 0,
  "Message": "OK",
  "OrderId": "3f2b7c1e-9a4d-4e2b-8c6f-1d2e3f4a5b6c",
  "OrderNumber": 5120,
  "CartIdentifier": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
  "CartId": 88341,
  "Total": 55.90,
  "CurrencyIso": "EUR",
  "CheckoutUrl": "https://uiservices.coriunder.cloud/Hosted/?merchantID=...&shop_cartId=a1b2c3d4-...&signature=...",
  "LineCount": 3
}

The third line has no seller: it is your own line and carries no marketplace commission.

The simplest way is to redirect the buyer to CheckoutUrl as returned. If you build the link yourself (to add display fields, a template or the buyer's details), these are the fields that matter for a cart payment. Every other field of the SALE request is available as well.

// values from the CreateMarketplaceOrder response
var orderId = order.OrderId, cartId = order.CartIdentifier;
var amount = order.Total.toFixed(2), currency = order.CurrencyIso;

var signature = CryptoJS.SHA256(MerchantNumber + amount + currency + 0 + 1 + orderId + orderId +
		cartId + 11 + payFor + notification_url + url_redirect + PersonalHashKey);
var hash = encodeURIComponent(signature.toString(CryptoJS.enc.Base64));

var src = "https://uiservices.coriunder.cloud/hosted/default.aspx?merchantID=" + MerchantNumber +
	"&trans_amount=" + amount + "&trans_currency=" + currency + "&trans_type=0" + "&trans_installments=1" +
	"&trans_refNum=" + orderId + "&trans_order=" + orderId + "&shop_cartId=" + cartId + "&ui_version=11" +
	"&disp_payFor=" + encodeURIComponent(payFor) + "&notification_url=" + encodeURIComponent(notification_url) +
	"&url_redirect=" + encodeURIComponent(url_redirect) + "&signature=" + hash;

Keep the field order of the link and of the signature the same. The values go into the signature as sent, before URL encoding.

• One transaction for the cart total is recorded on your processing merchant, and the cart is marked paid with it.
• The order moves to Paid when the captured amount covers the order. The notification is posted to the order's notification URL with the usual result fields; trans_order carries the OrderId.
• Every cart line is stamped with the transaction, the paid date, the marketplace commission on that line (the program default or the seller's own rate, taken at that moment) and the line's share of the processing fees. Lines of your own carry no commission. Read them back with GetCartByIdentifier: each item shows SellerMerchantNumber, PaidDate and, once paid out, SettlementId.
• Sellers are settled from their lines on the schedule agreed for the marketplace. A line is settleable once paid, or once marked shipped when the program settles on fulfilment.
• Refunds are recorded per cart line: the refund is a partial refund of the cart transaction for the lines and quantities chosen, and a line refunded after it was settled is taken back from the seller's next settlement.
• Partial payments do not mark the lines. The lines are stamped only when the order is fully paid.

If the lines of a paid cart are not marked within half an hour, the charged amount or currency did not match the cart. Check the order and contact support.

If you collect the card yourself, or charge a stored card, send the same cart to the processing endpoint: call remote_charge.asp with your processing merchant (CompanyNum), the amount and currency of the cart, Order = the OrderId and CartId = the CartIdentifier. The cart is marked paid the same way, and the lines are stamped by our sweep within half an hour even when no order notification is sent.

Wallet buyers signed in to your app pay the cart through the Transactions.svc Process operation with the cart cookie from SetCart.