Payment Details Visibility

When your business sends payouts through Nium, recipients expect two things:

1. To recognize who sent the money.
2. To understand what the payment is for.

If recipients cannot identify payments on their bank statements, it creates confusion, and delays in reconciliation.

This guide explains how Nium helps ensure payments are identifiable, what visibility looks like across different corridors, and how you can configure payouts for a better customer experience.

Transaction visibility

Bank statement formats vary by country and clearing system. Some display the sender’s name and reference text, while others enforce fixed values or show only technical identifiers.

To maximize visibility, Nium follows this process:

1. If sender name is supported: Nium sends your customer’s name in remitter.name.
2. If sender name is not supported: Nium checks if you provided customerComments.
   • If yes, we send the comments to the clearing system (shown if supported by the bank).
   • If no, Nium auto-populates with the remitter’s name and the Nium transaction ID (systemReferenceNumber).
3. Neither supported: Recipients identify the payment using system-generated references such as UTRs, bank reference numbers, or Nium transaction IDs.

This ensures recipients always have some identifying information.

Corridor categories

Corridors fall into three categories:

1. Full visibility: Both sender name and comments appear.

   • Example: EUR, AUD, SGD
   • Statement:

     CREDIT: ACME Ltd
     REF: Invoice 1234

2. Partial visibility: Sender name is fixed (e.g., NIUM Fintech, Instarem), but comments are visible.

   • Example: GBP, HKD, MYR
   • Statement:

     CREDIT: NIUM FINTECH
     REF: ACME Ltd / Invoice 1234

3. Limited visibility: Only system references and transaction details are shown.

   • Example: INR, VND, MXN
   • Statement:

     CREDIT: ACME Corp
     REF: UTR 20250928012345

Configuring payouts

When creating a payout, you control two fields:

Field	Purpose	Notes
remitter.name	Sends your customer’s name as the sender.	Some corridors override with fixed names (e.g., GBP, HKD, MYR).
customerComments	Free field to include reference details (customer name, invoice ID, order ID).	Length and characters vary by corridor. May be shortened or removed by banks.

Corridor visibility

Currency	Country	Customer Name as Remitter	Remitter Name Visibility	Narrative / Comments Visibility	Other Information
AUD	Australia	✅ Yes	✅ Visible	✅ Visible
BDT	Bangladesh	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible
BRL	Brazil	⚠️ Limited (proxy only)	⚠️ Visible for proxy transactions only	❌ Not visible
CAD	Canada	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	⚠️ Sent to beneficiary bank
COP	Colombia	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible
EUR	Eurozone (multiple countries)	✅ Yes	✅ Visible	✅ Visible
GBP	United Kingdom	❌ No (fixed as NIUM Fintech)	⚠️ Visible as NIUM Fintech	✅ Visible
HKD	Hong Kong	❌ No (fixed as INSTAREM)	⚠️ Visible as INSTAREM	⚠️ Sent to beneficiary bank	Transaction Reference Number
IDR	Indonesia	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible	Transaction Reference Number
INR	India	⚠️ Limited (proxy only)	⚠️ Visible for proxy transactions only	❌ Not visible	Bank Reference Number
JPY	Japan	✅ Yes	✅ Visible	❌ Not visible
KRW	South Korea	✅ Yes	✅ Visible	❌ Not visible
LKR	Sri Lanka	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible
MXN	Mexico	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible
MYR	Malaysia	❌ No (fixed as NIUM SDN. BHD.)	⚠️ Visible as NIUM SDN. BHD. (FKA Instarem)	✅ Visible
NPR	Nepal	✅ Yes	✅ Visible	❌ Not visible	Bank Transaction Reference Number
PHP	Philippines	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	⚠️ Sent to beneficiary bank
PKR	Pakistan	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	❌ Not visible
PLN	Poland	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	⚠️ Sent to beneficiary bank	Transaction Reference Number
SGD	Singapore	✅ Yes	✅ Visible	❌ Not visible	Transaction Reference Number
THB	Thailand	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible
TRY	Turkey	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	❌ Not visible
USD	United States	⚠️ Bank dependent	⚠️ Sent to beneficiary bank	⚠️ Sent to beneficiary bank	Nium transaction ID
VND	Vietnam	⚠️ Limited (clearing restrictions)	⚠️ Limited by clearing system	❌ Not visible	Bank Transaction Reference Number

Legend

• ✅ Yes: Customer’s name can be sent as the remitter.
• ⚠️ Limited: Restricted (proxy, clearing limits, or bank dependent).
• ❌ No: Corridor enforces a fixed remitter (e.g., NIUM / Instarem).

Example scenarios

Corridor supports remitter (EUR)

"remitter": { "name": "John Smith" },
"customerComments": "Invoice #1234"

Bank Statement

CREDIT: JOHN SMITH
REF: Invoice #1234

Fixed remitter, customer comments used (GBP)

"remitter": { "name": "John Smith" },
"customerComments": "Invoice #1234"

Bank Statement

CREDIT: NIUM FINTECH
REF: John Smith / Invoice #1234

Fixed remitter, no comments provided (GBP)

"remitter": { "name": "John Smith" }

Bank Statement

CREDIT: NIUM FINTECH
REF: John Smith - Nium Txn 987654321

Clearing system reference only (INR)

"remitter": { "name": "John Smith" }

Bank Statement

CREDIT: ABC CORP
REF: UTR 20250928012345

Transaction identification and visibility

Recipients can identify payments through:

1. Sender Name
   • Passed in remitter.name when supported.
2. Reference Text
   • Customer details in customerComments (e.g., customer name, invoice ID, order reference).
3. System Identifiers
   • Used when neither sender name nor comments are supported. Examples include:
     • UTR (Unique Transaction Reference) (INR)
     • Bank Reference Numbers(NPR, VND)
     • Transaction Reference Numbers (HKD, SGD, PLN)
     • Nium Transaction ID (USD)

Best practices

• Always provide the sender’s name in remitter.name when allowed.
• In corridors with fixed names, populate customerComments with:
  • Customer name
  • Invoice or order ID
• Keep values short (≤ 30 characters) and alphanumeric.
• Test payouts in your key corridors to confirm what recipients see.
• See Payouts for details on how to create payments.

Limitations

• Corridor restrictions — Some corridors enforce fixed remitters or block comments.
• Bank dependency — Banks may truncate, strip, or reformat details.
• Formatting not guaranteed — Final display depends on the beneficiary bank’s system.

FAQ

Q: How do I make sure my customer’s name appears?**
A: Send it in remitter.name. If not supported, use customerComments.

Q: What happens if I don’t pass customerComments in fixed-remitter corridors?**
A: Nium auto-populates remitter.name with <Remitter Name> + Nium Transaction ID.

Q: How will recipients recognize the transaction?**
A: Through a combination of:

• Sender name (if supported)
• Your Reference text (e.g., invoice/order IDs)
• System identifiers (UTR, Bank Ref, Nium Txn ID)

Q: Why does visibility differ across corridors?**
A: Each local clearing system and bank enforces different rules.

Q: What if text exceeds corridor limits?**
A: It may be truncated or rejected.