Settlements
A settlement is the payout statement of a marketplace: which sales, fees, refunds and reserves it has offset, and which amount it finally transfers. merchantCENTRAL keeps the settlements of all marketplaces on one page. The connector of a marketplace only delivers the raw data. Classifying the lines, matching them to your posted documents, the account mapping and the posting are done by the hub – the same way for every marketplace.
At present, the Amazon connector and the merchantCENTRAL Connector for eBay deliver settlements.
Amazon: add-on module AMAZON-SETTLE
For Amazon, settlements are an add-on module of the connector: AMAZON-SETTLE, €105 net per 4 weeks per channel, licensed next to the AMAZON module. Without this license the connector reads no settlements, and its job neither matches nor posts any. Import Settlements on the Amazon Dashboard checks the license and offers the demo registration as long as the module is not registered.
eBay: add-on module EBAY-SETTLE
For eBay, too, settlements are an add-on module of the connector: EBAY-SETTLE, licensed next to the EBAY module. Without this license the connector reads no payouts, and its job neither matches nor posts any. Demo, subscription and status are opened by the action Settlements Add-on License of the eBay Setup on the hub card Marketplace Setup; see eBay.
Opening the Page
- Via search: Settlements
- On the marketplace card → Settlements, filtered to this marketplace
- On the Amazon Dashboard → Settlements, filtered to Amazon
- On the eBay Dashboard → Advanced → Settlements, filtered to eBay
- Via the lines Amazon payouts not posted and eBay payouts not posted of the Waiting for you card on the merchantCENTRAL Dashboard (only with AMAZON-SETTLE or EBAY-SETTLE, see Amazon and eBay)
You open the card of a settlement from the list. You reach the Settlement Account Mapping with the Account Mapping action of the list, with the Settlement Account Mapping action of the merchantCENTRAL Setup and of the marketplace card, or via search.
How It Works
- Import – The connector fetches the payout reports of the marketplace and creates one settlement with its lines per report. Every line gets a category.
- Match – Match Lines looks for the posted sales invoice or sales credit memo of the marketplace order behind every revenue line.
- Post – Post posts the payout: payments on the matched documents, fees per G/L account, an unexplained remainder to the clearing account and the transfer to the bank account.
For Amazon, the job can do steps 2 and 3 on its own (see Amazon).
Status
| Status | Meaning |
|---|---|
| New | Imported. The settlement stays New until all its revenue lines are matched to a document. If a settlement that is not posted is imported again, the import replaces its lines and sets it back to New. |
| Reviewed | The value exists; in this version no function sets it. |
| Matched | The settlement has revenue lines, and each of them is matched to a posted document. |
| Posted | The payout is posted. After that, neither a new import nor Match Lines changes the settlement, and it cannot be posted a second time. |
Settlements (List)
The list shows the settlements of all marketplaces, the latest payout first. It is read-only.
| Field | Description |
|---|---|
| Marketplace Code | Marketplace of the settlement, e.g. AMAZON or EBAY. |
| Settlement ID | Identifier the marketplace gave the settlement. |
| Sales Channel | Sub-account the payout belongs to, by its name – for Amazon, the country marketplace (DE, FR …), for eBay, the sales channel of the default marketplace of the eBay account (see eBay). |
| Start Date / End Date | Period the settlement covers. |
| Deposit Date | Day the marketplace transferred the payout. |
| Deposit Amount | Amount transferred. |
| Line Total | Sum of all imported lines. If it equals the deposit amount, the payout is fully explained. |
| Open Lines | Lines that should be matched to a posted document and are not yet. Red as long as there are any. |
| Status | See Status. |
| Currency Code | Currency of the settlement. |
| Posted Document No. | Document number of the posting. |
| Action | Description |
|---|---|
| Match Lines | Looks for the posted document behind every revenue line of the selected settlement (see Matching). |
| Post | Posts the payout (see Posting). Not available for posted settlements. |
| Account Mapping | Opens the Settlement Account Mapping. |
Settlement (Card)
The card shows one settlement with its lines and whether the payout adds up. It is read-only and has the same actions Match Lines and Post as the list.
| FastTab | Fields |
|---|---|
| General | Marketplace Code, Settlement ID, Sales Channel, Status |
| Period and Payout | Start Date, End Date, Deposit Date, Deposit Amount, Currency Code |
| Reconciliation | see below |
| Lines | see Lines |
| Posting | Posted Document No., Posting Date, Posted At, Imported At, Matched At (time of the last matching) |
FastTab Reconciliation:
| Field | Description |
|---|---|
| Line Total | Sum of all lines. |
| Reported Total | Total the marketplace itself reports for the settlement. If the line total differs from it, the import is incomplete; the import records this as an error in the Activity Log. |
| Unexplained Remainder | Line total minus deposit amount: the part of the payout the lines do not explain. Green at 0, highlighted otherwise. When posting, it goes to the clearing account, provided it does not exceed the settlement tolerance. |
| Total Lines | Number of lines. |
| Open Lines | As in the list. |
Lines
| Field | Description |
|---|---|
| Line No. | Sequence in the settlement. |
| Posted Date | Day the marketplace booked the transaction. |
| Category | Classification of the line, see Categories. |
| Transaction Type | Transaction type as reported by the marketplace, e.g. Order or Refund. Hidden by default. |
| Amount Type | Amount type as reported by the marketplace, e.g. ItemPrice or ItemFees. |
| Amount Description | Description as reported by the marketplace, e.g. Principal or Commission. Hidden by default. |
| External Order No. | Order number of the marketplace; matching uses it to find the posted document. |
| External Item No. | SKU as reported by the marketplace. Hidden by default. |
| Quantity | Quantity as reported by the marketplace. Hidden by default. |
| Amount | Amount of the line: sales positive, fees and refunds negative. |
| Match Status | Matched, Unmatched or Not Applicable – the status of lines without a document reference, such as fees and reserves. Matching does not set the value Ambiguous in this version. |
| Matched Invoice No. / Matched Cr. Memo No. | Posted sales invoice or sales credit memo of the line; clicking it opens the document. |
| Matched Customer No. | Bill-to customer of the matched document; the payment is posted to this customer. Hidden by default. |
Categories
On import, every line gets a category. It decides whether the line is matched to a document or goes to a G/L account:
| Category | Treatment |
|---|---|
| Item Price, Shipping, Tax, Refund | Revenue lines. They are matched to a posted document and applied to it. |
| Commission, Fulfillment Fee, Storage Fee, Advertising, Adjustment, Reserve, Other | Costs and corrections. They go to the G/L account of the account mapping. |
| Long-Term Storage Fee, Inbound Placement Fee, Inbound Transport Fee, Removal and Disposal Fee, Prep and Labeling Fee | Fees of the marketplace warehouse, for Amazon of the FBA warehouse. Costs like the other fees: they go to the G/L account of the account mapping. Without a mapping of their own, they post to the account of the Storage Fee (long-term storage fee) or the Fulfillment Fee (all others), see Settlement Account Mapping. The connector assigns these categories; the keyword search of the hub does not know them. |
| Reimbursement | Money the marketplace pays for goods lost or damaged in its warehouse or on the way – for Amazon, the FBA reimbursements. Income, not a customer document: it goes to the G/L account of the account mapping like a fee. |
How the category is determined
The hub searches the amount type, amount description and transaction type of a line for keywords, in this order; the first hit wins:
| Keyword | Category |
|---|---|
| REIMBURSE, WAREHOUSE_LOST, WAREHOUSE_DAMAGE, COMPENSATED | Reimbursement |
| ADVERTIS, SPONSORED | Advertising |
| STORAGE, LAGER | Storage Fee |
| FBA, FULFILL, SHIPPINGCHARGEBACK | Fulfillment Fee |
| COMMISSION, REFERRAL, FINALVALUE, CLOSINGFEE | Commission |
| RESERVE, CARRYOVER, UNAVAILABLE | Reserve |
| REFUND, RETURN, GUTSCHRIFT | Refund |
| TAX, VAT, MWST | Tax |
| SHIPPING, FREIGHT, VERSAND | Shipping |
| PRINCIPAL, ITEMPRICE | Item Price |
| ADJUST | Adjustment |
If nothing matches, a negative line becomes Other, a positive one Item Price.
The Amazon connector classifies first. It starts with the fees of the FBA warehouse; for these it searches transaction type, amount type and amount description together, ignoring spaces, hyphens and underscores:
| Keyword | Category |
|---|---|
| LONGTERMSTORAGE, STORAGERENEWAL, AGEDINVENTORY | Long-Term Storage Fee |
| INBOUNDPLACEMENT, PLACEMENTSERVICE | Inbound Placement Fee |
| INBOUNDTRANSPORT, INBOUNDCONVENIENCE | Inbound Transport Fee |
| REMOVALCOMPLETE, DISPOSALCOMPLETE, REMOVALFEE, DISPOSALFEE | Removal and Disposal Fee |
| LABELINGFEE, LABELLINGFEE, LABELFEE, PREPFEE, PREPSERVICE, BUBBLEWRAP, POLYBAG, TAPINGFEE | Prep and Labeling Fee |
The other storage and fulfillment fees are still classified by the hub according to the table above. After that: if the amount type or amount description contains PROMOTION, COUPON, GUARANTEECLAIM or CHARGEBACK, the line becomes Adjustment. The exception is SHIPPINGCHARGEBACK, which stays Fulfillment Fee according to the table.
The merchantCENTRAL Connector for eBay, too, classifies its lines itself, by eBay's transaction type and fee type; see eBay: lines of a payout. Only transaction types it does not know are classified by the hub according to the table above.
Matching
Match Lines checks every revenue line of the settlement again:
- A line of the category Refund first looks for a posted sales credit memo for its order. If there is none, it is matched to the posted sales invoice like all other revenue lines.
- The hub finds the invoice via the marketplace order and its sales order, for older documents via the marketplace order number on the posted document or via the External Document No. If there are several, matching takes the one with the highest document number.
- A line without an order number or without a posted document stays Unmatched and counts toward the Open Lines.
If all revenue lines are matched afterwards, the settlement gets the status Matched. A message states the matched lines, the lines without a document and the lines without a document reference (fees, reserves); the result is also recorded in the Activity Log. Posted settlements stay unchanged.
Posting
Post asks for confirmation ("Post settlement … with a payout of …?") and checks, before anything is posted:
- whether the setup is complete – otherwise the message names the missing field;
- whether the Unexplained Remainder stays within the Settlement Tolerance. If it exceeds it, posting stops with Payout does not add up; the message states line total, deposit amount, remainder and tolerance and, if there are any, the number of open lines.
Only then does the hub post. The balancing account of every entry is the Settlement Transit Account of the marketplace:
| What | Where to |
|---|---|
| Matched lines, summed per document | One payment to the customer of the document, applied to the invoice – for a credit memo, a refund applied to the credit memo. |
| All other lines: fees, reserves, adjustments, reimbursements and revenue lines without a document | One entry per G/L account of the account mapping; lines without a matching mapping go to the clearing account. |
| Unexplained remainder | Clearing account. |
| Deposit amount | Settlement bank account of the marketplace. |
If the payout is fully explained, the transit account is at zero for this settlement afterwards.
Post does not require complete matching: revenue lines without a document are not posted as a payment on an invoice, but like fees via the account mapping or to the clearing account. So check the Open Lines before posting if every payment is to be applied to its invoice.
Posting details:
- Document number: marketplace code and settlement ID, e.g.
AMAZON-12345678901, cut to 20 characters. The External Document No. is the settlement ID. - Posting date: the deposit date – so the bank entry can be reconciled against the bank statement. If it is missing, the end date, otherwise the work date.
- Currency: that of the settlement, if it is not the local currency.
- Descriptions: Payout <ID> - invoice <No.>, … - credit memo <No.>, … - <G/L account no.>, … - unexplained remainder, … - bank transfer.
- The entries are posted directly; no lines are created in the settlement journal.
- Afterwards the settlement is Posted with Posted Document No., Posting Date and Posted At; the Activity Log gets an entry, and a message states the number of posted lines.
Settlement Account Mapping
Here you define per marketplace which G/L account a category is posted to – so commission, fulfillment, storage and advertising costs can be analyzed separately. Anything without a mapping goes to the clearing account.
| Field | Description |
|---|---|
| Marketplace Code | Marketplace the line applies to. |
| Category | Category that is posted to the G/L account. |
| Amount Type Filter | Empty: the line applies to the whole category. Filled with an amount type – spelled exactly as in the Amount Type column of the settlement lines –, it applies only to lines of this amount type and takes precedence over the line without a filter. This way you split a category further. |
| G/L Account No. | G/L account the amounts are posted to. Only posting accounts that are not blocked. |
| Description | Free text for the line. Posting does not use it in this version; the entry description names the G/L account number. |
Marketplace warehouse fees without a mapping of their own. The categories of the marketplace warehouse were split off two older ones: the Long-Term Storage Fee from the Storage Fee; the Inbound Placement Fee, the Inbound Transport Fee, the Removal and Disposal Fee and the Prep and Labeling Fee from the Fulfillment Fee. If one of them has no G/L account of its own, the hub posts it to the account of the category it came from – by the same rule: first the line with a matching Amount Type Filter, then the one without a filter. Only if nothing is mapped there either does it go to the clearing account. To analyze these fees separately, create lines of their own for them.
Mappings for the revenue categories (Item Price, Shipping, Tax, Refund) only affect lines that were not matched to a document.
Setup
Import and matching need no setup in the hub. For posting, the hub needs six fields in two places.
merchantCENTRAL Setup, FastTab Settlements – applies to all marketplaces:
| Field | Purpose |
|---|---|
| Settlement Journal Template, Settlement Journal Batch | General journal used for posting. If you choose another template, the journal batch is cleared when the new template has no batch of that name; then choose it again. |
| Settlement Clearing Account | G/L account for amounts without a document and without an account mapping, such as reserves and rounding differences, and for the unexplained remainder. |
| Settlement Tolerance | How large the unexplained remainder of a payout may be at most, as an amount. If it is larger, the payout is not posted at all. Default: 0 – then only payouts whose lines add up exactly to the deposit amount are posted. |
The action Settlement Account Mapping of the merchantCENTRAL Setup opens the Settlement Account Mapping of all marketplaces.
Marketplace card, FastTab Settlements – per marketplace:
| Field | Purpose |
|---|---|
| Settlement Bank Account | G/L account the payout is posted to. |
| Settlement Transit Account | G/L account that holds the money between the sale and the payout; balancing account of every entry. If a payout is fully explained, it is at zero for this settlement afterwards. |
The actions Settlement Account Mapping and Settlements of the marketplace card open the account mapping or the settlements, filtered to this marketplace.
If one of the fields is missing, Post stops with a message that names the field and opens the merchantCENTRAL Setup or the marketplaces.
Amazon
Import. The Amazon connector reads the settlement reports Amazon creates on its own (GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2, about every 14 days) for every marketplace the account takes part in – each marketplace on its own: a report that cannot be retrieved or read affects only its marketplace. Every report becomes a settlement; the Sales Channel is the country marketplace, Deposit Amount and Reported Total are the total of the report, the Deposit Date is its deposit date. The first import of a marketplace reads back as far as Settlement Lookback (Days) in the Amazon Settings defines (default and maximum 90 – that is how long Amazon keeps the reports); later imports ask from one day before the start of the last run without failures on that marketplace. The import skips a report of a settlement whose status is no longer New; unlike described under Status, for Amazon it replaces the lines of new settlements only. If a marketplace has a cut-over date from the Amazon data takeover, the connector does not import settlements that begin before the cut-over date – they belong to the previous system.
By hand. Import Settlements on the Amazon Dashboard imports after a confirmation and reports how many settlements were imported, already known or unreadable. You then match and post them on this page.
By job. The job SETTLEMENTS (settlement import, daily) is created by Set Up Automation on the hub card Marketplace Setup of the marketplace AMAZON (see Amazon Jobs) when AMAZON-SETTLE is licensed. After every import, it matches all Amazon settlements with the status New again. If Post Settlements Automatically is turned on in the Amazon Settings, it then posts every Amazon settlement not posted yet whose deposit date has been reached – each on its own, so one that cannot be posted does not hold up the others. It stays open, and the reason is in the Amazon Activity Log (Settlement … was not posted automatically: …).
Automatic posting does not wait for complete matching
For Amazon, the deposit amount is the total the report itself states. If the report is imported completely, the unexplained remainder is therefore 0 – even if revenue lines are not matched to a document yet, for example because the invoice is not posted yet. The job posts such lines as described above via the account mapping or to the clearing account, not as a payment on the invoice.
Monitoring. With AMAZON-SETTLE, the Waiting for you card on the merchantCENTRAL Dashboard shows the line Amazon payouts not posted: Amazon settlements that are still not posted three days after the deposit date. Clicking it opens them in this list.
eBay
License. For eBay, settlements are the add-on module EBAY-SETTLE, licensed next to the EBAY module. Without this license the connector reads no payouts, matches none, posts none and creates no settlement job. The License FactBox of the eBay pages shows the EBAY module only. You reach the add-on via the action Settlements Add-on License of the hub card Marketplace Setup when it shows eBay (see eBay Setup): it opens the license card of EBAY-SETTLE, on which you start the 30-day demo, subscribe to the module or see its status.
One settlement per payout. eBay pays out per seller account, not per country. The connector reads the payouts of every enabled eBay account through the Sell Finances API and creates one settlement per payout:
| Field | Content |
|---|---|
| Settlement ID | Payout ID of eBay. |
| Sales Channel | Sales channel of the default marketplace: the marketplace in Default Marketplace Code of the eBay Setup if the account has it and it is enabled and usable, otherwise the first usable marketplace of the account. A payout therefore belongs to exactly one sales channel, even if it contains sales of several eBay sites. |
| Start Date / End Date | Date of the first and the last transaction of the payout. |
| Deposit Date | Payout date according to eBay. |
| Deposit Amount, Reported Total | Amount transferred. |
Settlements are only created from completed payouts (eBay status Succeeded): as long as eBay is still executing a payout or retrying it after a temporary failure, it may still change. The next import asks for such a payout again – for 60 days at most; after that, the import no longer waits for it and records a warning in the activity log (eBay payout … is still not completed …). A payout that failed for good is not imported; eBay pays the amount out again, and the activity log gets a warning. The import does not read a payout again that already has a settlement – eBay does not change a completed payout. Unlike described under Status, a new import for eBay therefore replaces no lines.
Lines of a payout
eBay reports per transaction the amount after deducting its fees. So that the sale is matched to its invoice with the full amount and every fee goes to its own account, the connector splits the transactions. The Transaction Type of every line is eBay's (SALE, REFUND …), the Amount Type is PRINCIPAL for the gross amount or eBay's fee type, the Amount Description is eBay's memo, the External Order No. is the eBay order number.
| Transaction | Lines | Category |
|---|---|---|
| Sale (SALE) | Gross amount (PRINCIPAL): transaction amount plus fees, positive | Item Price – matched to the sales invoice of the order |
| one line per fee type, summed over all line items of the order, negative. Selling fees (FINAL_VALUE_FEE and fee types starting with it, INSERTION_FEE, INTERNATIONAL_FEE, REGULATORY_OPERATING_FEE) | Commission | |
| Fees for Promoted Listings (AD_FEE and other fee types with AD_FEE or PROMOTED in their name), negative | Advertising | |
| every other fee type and the collective line FEE, negative | Other, with a warning (see Unknown fees and differences) | |
| Refund (REFUND) | Gross refund amount (PRINCIPAL), negative | Refund – matched to the sales credit memo, without a credit memo to the invoice |
| Fees eBay returns with the refund, per fee type, positive | as for a sale: Commission, Advertising or Other | |
| Shipping label (SHIPPING_LABEL) | one line | Fulfillment Fee – not Shipping: you bought the label from eBay; no invoice explains it. |
| Fee eBay charges separately (NON_SALE_CHARGE) | one line, amount type = fee type | Selling fees as for a sale: Commission; AD_FEE: Advertising; STORE_SUBSCRIPTION_FEE: Other; every other fee type and a charge without a fee type: Other, with a warning |
| Payment dispute, credit, adjustment (DISPUTE, CREDIT, ADJUSTMENT) | one line | Adjustment |
| TRANSFER, LOAN_REPAYMENT, PURCHASE, WITHDRAWAL | one line | Other |
| Express payout | Fee for an express payout to a debit card (EXPRESS_PAYOUT_FEE), negative | Other |
Fees eBay counts in the total of a transaction but assigns to no line item, and fees without a fee type, are combined by the connector under the fee type FEE. The signs follow eBay's booking entry. That way the lines of a transaction add up to its amount, and the lines of a payout to the amount transferred.
Analyzing fees separately
With the Amount Type Filter of the Settlement Account Mapping you split a category by fee type – for example Commission with the filter INTERNATIONAL_FEE to an account of its own for the international fee, or Other with the filter STORE_SUBSCRIPTION_FEE to the account for the store subscription.
Unknown fees and differences
Unknown fee type. The connector never posts a fee as commission on a guess. A fee type it does not know goes to Other, and so does the collective line FEE. A transaction type it does not know is classified by the hub according to its table. Either way the import writes one warning per payout to the activity log, naming the type and the category it got, e.g. SALE / BELOW_STANDARD_FEE (Other). Check these lines before posting. With the amount type filter of the account mapping you can direct such a fee type to an account of its own.
Lines do not add up to the payout. If the lines of a payout do not add up to the amount transferred, the reason is in a note on the settlement (FactBox Notes of the settlement card) and in a warning in the activity log. The note states the line total, the amount paid out, the difference, the total of the transactions and the express payout fee. It adds a hint at the likely cause:
- the express payout fee, when the difference equals it exactly,
- the sign of the refunds, when the difference is twice the refunds,
- otherwise missing transactions or an unexpected sign.
Raw data. With Keep Raw Settlement Data in the eBay Account part, the import keeps what eBay sent for every payout: the payout and its transactions as JSON. Buyer data is masked: buyer, shipping address, user names, phone, transaction memo and bank details. Download the file with Download eBay Raw Data on the settlement card and in the settlement list; Raw Settlement Data on the account card lists all payouts kept for the account. The setting applies to the payouts imported from then on. When the settlement is deleted, its raw data is deleted with it.
Checking the first real payouts
Leave Post Settlements Automatically off and Keep Raw Settlement Data on until the first payouts of an account have been checked. Afterwards you can switch the raw data off again.
Fields in the eBay Account part
What the settlement import needs is in the eBay Setup in the eBay Account part, group Settlements – per account, because eBay pays out per account:
| Field | Description |
|---|---|
| Post Settlements Automatically | Every run of the settlement job posts the payouts of this account whose lines are all matched and add up to the amount transferred within the settlement tolerance, once the deposit date has been reached. Others stay for review. Matching always runs, even without this setting. |
| Settlement Lookback (Days) | How far back the first settlement import of the account reads. Default: 90, at most 365. Later imports ask from one day before the start of the last run without failures – never past a payout eBay has not completed yet. |
| Settlement Cut-over Date | First payout date the import takes for this account. Payouts before it stay with the system that has booked them until now – imported here, they would be posted a second time. Leave it blank if no earlier system booked the eBay payouts. |
| Settlement Imported Until | Date and time up to which the payouts of the account are imported; the next import starts here. Not editable. |
| Keep Raw Settlement Data | The import keeps what eBay sent for every payout, with buyer data masked; see Raw data. Default: off. |
Import, matching and posting
By hand. Import Settlements on the eBay Dashboard (group Advanced) first checks the license and offers the demo registration as long as EBAY-SETTLE is not registered. The action then creates the settlement job if it is missing, asks for confirmation and imports the payouts of all enabled accounts – each account on its own: an account for which eBay refuses the request keeps its stand and does not hold up the others. Accounts in Simulation Mode read nothing. The message states how many settlements were imported, already known and failed; the details are in the activity log. You then match and post them on this page.
By job. The job SETTLEMENTS (eBay: Import Settlements, daily) is created by the connector on installation and update if EBAY-SETTLE is licensed, otherwise on the first Import Settlements of a user who may create job queue entries. Like the other eBay jobs, it is created with the status On Hold. After every import, it matches all eBay settlements with the status New again. It then posts, for every account with Post Settlements Automatically, every settlement not posted yet whose deposit date has been reached and which has no open lines – each on its own, so one that cannot be posted does not hold up the others. It stays open, and the reason is in the activity log (Settlement … was not posted automatically: …).
Unlike Amazon: only fully matched payouts are posted automatically
The eBay job posts a payout only when every one of its revenue lines is matched to a posted document. If an invoice is still missing, the payout waits; the next run matches it again. To post it anyway, use Post on this page – revenue lines without a document then go via the account mapping or to the clearing account as described under Posting.
Monitoring. With EBAY-SETTLE, the Waiting for you card on the merchantCENTRAL Dashboard shows the line eBay payouts not posted: eBay settlements that are still not posted three days after the deposit date. Clicking it opens them in this list.
Digital signatures for sellers from the EU and the United Kingdom
For sellers domiciled in the EU or the United Kingdom, eBay requires the calls of the Sell Finances API to be digitally signed. Without a signature, eBay refuses to return the payouts, and the settlement import of this account stops. Set up the signatures once per account: Digital signatures.