Receipt of payment in national currency against a stated order reference, as distinct from receipt of a digital asset. In a crypto-funded purchase the buyer pays through a payment gateway in digital assets; a licensed digital-asset platform screens the transaction and converts the crypto to fiat under its own licence, and the seller is settled in national currency to a bank account. The seller never receives, holds or transfers the asset the buyer sent. The leg closes only when the funds are credited and posted against the order reference the payment carries — two conditions, not one.
What arrives, and to whom
Settlement names the currency that arrives, not the currency that was paid. The buyer parts with a digital asset; the seller receives a bank credit; the two events are joined by a conversion performed by a third party in between. Every sentence about the payment leg has to specify which side it describes, because the same word covers both.
The beneficiary also distinguishes two structures that share identical conversion mechanics. An off-ramp settles the holder of the assets — proceeds return to the same person’s bank account. A payment gateway settles a seller against a purchase — proceeds move to a third party who is owed money for something. The second carries an evidential requirement the first does not: the receiving party has to be able to show which obligation the money answers.
Which settlement currency — the term now carries two meanings
In crypto merchant settlement the currency the seller receives is a configuration choice, not a property of the payment, and gateways offer both configurations to the same merchant. A gateway may settle in national currency to a bank account, in a stablecoin to a wallet, or split the proceeds between them. “Settlement” on its own therefore no longer identifies what the receiving party ended up holding; the adjective does the work.
| Settlement form | What the receiving party holds afterwards | Where exposure to the paid asset ends |
|---|---|---|
| National currency to a bank account | A bank credit in a named currency | At conversion, on the platform’s side |
| Stablecoin to a wallet | A token, which is a claim on that token’s issuer | It does not end; issuer and token exposure continue |
| Split settlement | Both, in the stated proportion | Partially, in the same proportion |
Golden Ark Reserve receives fiat only. It holds no digital assets, issues no token and no claim on metal, and takes no position in the asset the buyer sold. Conversion is performed by the platform, under the platform’s licence, before anything reaches the seller.
How a fiat settlement runs, and who does each step
- Quote and reference. The seller issues a quote and a pro forma invoice for advance payment, both carrying one order reference. Every record produced downstream repeats it.
- Payment. The buyer pays through the gateway in a supported digital asset, against that reference.
- Screening. The platform screens the wallet and the transaction against sanctions data and blockchain analytics, under its own licence. The seller does not perform this step and does not receive the underlying report.
- Conversion. The platform converts the digital asset to national currency on its own book, at its own rate, at a moment it fixes. From this point the amount is a currency amount and moves on banking rails.
- Outgoing transfer. The platform instructs a transfer to the seller’s account. Crossing borders through correspondent banks, it travels as a customer credit transfer carrying the parties, the amount, the value date, the charge-bearer election and the remittance reference.
- Credit and posting. The receiving bank credits the account and reports the item. The seller matches the credit to the order reference and posts it against that instruction. Details of the receiving arrangements sit with banking and payments.
- Application. The amount posts as an advance applied to one gold purchase instruction. Allocation follows on the terms of that instruction, and the commercial invoice is issued afterwards, on the bars actually allocated.
What the money becomes when it lands
A settled amount does not become a balance. It is an advance received under one gold purchase instruction, bound to that instruction by the order reference and by a stated validity period. There is no account balance, no wallet, no top-up and no transfer of money between counterparties. An unused remainder is returned to the account the settlement came from — which, on this route, is the platform’s account rather than the buyer’s wallet, because a return follows the path the payment took.
The pro forma invoice covers the advance. The commercial invoice comes later and describes the actual bars: serial numbers, weights, fineness and producer. Between those two documents sits the allocation, not a credit to anything.
What it costs, and what fixes the timing
The components are separable even where the figures are not published:
- Conversion spread, applied by the platform when it converts. It is a price, not a fee, and it does not appear as a line item.
- Gateway fee, charged on the payment.
- Charge-bearer election on the transfer itself, which decides who absorbs correspondent charges. The instruction carries one of three codes — debtor bears all, creditor bears all, or shared — and the election is made when the payment is instructed, not afterwards.
- Deductions in the chain, where intermediary banks take charges from the amount in transit.
- Value date and cut-offs, which govern when a credit is usable rather than merely visible, and which currency-holiday calendars can move.
Timing is a commercial parameter here, not an administrative one. Where a quote is fixed for a stated period, whether the settlement lands inside that period is what decides whether the quoted price still applies. Every element above — conversion moment, transfer instruction, correspondent hops, value date — sits inside that window or outside it.
What evidence a settlement produces
The digital-asset funding leg contributes two records that a bank-funded purchase does not have: the screening outcome and the conversion record. The full set attaching to a settled advance is the conversion record from the platform, stating what was converted, at what rate, when, and against which reference; the screening outcome, which reaches the counterparty as a verification status with a date and an internal reference, the underlying report remaining internal; the payment confirmation and its end-to-end identifier; the receiving bank’s credit advice; and the pro forma invoice the advance answers.
These join the contract, the AML/KYC record, the Allocation Record and the instruction log in the counterparty’s Evidence Set. The provenance question the whole set exists to answer is source of funds — the origin of the money in this transaction, as opposed to evidence that the payer holds it. Where transfers move between regulated service providers, originator and beneficiary information accompanies them under the Travel Rule, which is a requirement on the providers, not on the buyer. The controls framework sits under compliance and legal.
Where a fiat settlement fails
Name mismatch. The account is held in the legal name; a payment addressed to a trade name may not match it. Since 9 October 2025, payment service providers in the euro area must run Verification of Payee on SEPA credit transfers, standard and instant, returning match, close match, no match or other before the payer authorises; providers outside the euro area follow by 9 July 2027. A close match does not block the payment, but it turns a routine instruction into a decision the payer has to take, on screen, at the moment of paying.
Reference lost. A reference typed into the wrong field, truncated to the field length, or replaced by the gateway’s own internal identifier produces an unattributed credit: money in the account that cannot be matched to an instruction until someone reconciles it by hand. Nothing downstream starts, because there is no instruction to attach it to.
Short amount. Charges deducted in transit mean the credited figure is below the invoiced figure. The shortfall is settled separately or the instruction is re-scoped; it is not absorbed silently, because the advance is measured against one instruction.
Double conversion. An amount that reaches a bank in a currency the account does not hold is converted again, at the receiving bank’s rate, outside the price the platform fixed.
Rejection. A payment the receiving chain will not accept returns along the path it came, to the platform, not to the wallet the assets left.
What fiat settlement is not
- Not conversion. Conversion changes the asset. Settlement moves the resulting currency to the receiving party. Either can happen without the other completing.
- Not finality. Finality is the point at which a transfer can no longer be reversed by the sender. A payment can be final and still unattributed — irreversible and unusable at the same time.
- Not crypto settlement. The distinction is which asset the receiving party holds when the leg closes.
- Not allocation. Settlement closes the payment leg. Allocation identifies specific bars by serial number, weight, fineness and producer. Money received is not metal owned, and the interval between the two is a documented state, not a gap.
Two records, one field: what the November 2025 message change did to this leg
Every crypto-funded settlement generates two records in systems that do not speak to each other. The platform’s record knows the digital asset, the wallet, the rate and the moment of conversion, and knows nothing about bars. The bank’s record knows the amount, the ordering party and the value date, and knows nothing about what was converted. Nothing joins them except the reference carried in the payment instruction — which is why the order reference, and not the rail, is the load-bearing element of the payment leg.
For decades that reference travelled as free text in a remittance field on an MT103: one short line, hand-keyed, routinely truncated or overwritten. That ended on 22 November 2025, when the coexistence period for Swift’s cross-border programme closed and the MT families used for cross-border payments and cash reporting were retired in favour of their ISO 20022 equivalents — pacs.008 in place of MT103, camt reporting messages in place of MT940 and MT942. Two consequences bear directly on a settlement leg. Remittance information now has a structured form, carrying a document reference with a type code, number and date rather than a line of prose, so an order reference can travel as data rather than as a note a human reads. And each payment carries a unique end-to-end transaction reference that stays unchanged at every institution in the chain, so the credit that lands can be tied to the instruction that was sent without inference from amount and date. A second deadline follows on 14 November 2026, when fully unstructured postal addresses stop being accepted in those messages and non-compliant instructions are rejected at the network rather than repaired downstream.
What changes for a counterparty’s work is the standard of proof available on the payment leg. The join between “the platform converted this” and “the seller received that” is now capable of being evidenced from the payment record itself, rather than asserted in correspondence and accepted on trust. It also means the leg fails earlier and louder: a reference in the wrong field or address data the network will not carry stops the instruction, instead of producing a credit that arrives clean and sits unattributed while someone reconstructs it. The two data points that decide which outcome a counterparty gets are the form of the reference given to the payer and the identifier returned on confirmation.
The route this settlement leg belongs to, end to end, is set out on Buy Gold with Crypto.