Barbara,
Thank you for reviewing the EPP balance mapping and helping with what is needed
to support your model whereby registrars may have more than one balance. We
can break the balance attributes under a new <balance:balance> element that can
have an optional “name” attribute to identify the name of the balance
attributes, which could be registry operator customers or even TLD, but is up
to server policy. The following is an example of the balance info response for
3 possible balance models, which can be supported in the -03 balance draft:
A Balance per Registrar and per Registry Operator Customer (“Acme Inc.” and
“Example Inc.”):
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<balance:infData
xmlns:balance="urn:ietf:params:xml:ns:epp:balance-0.3">
<balance:balance name=”Acme Inc.”>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
<balance:balance name=”Example Inc.”>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
</balance:infData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID>
</response>
</epp>
A Balance per Registrar and per TLD (“FOO”, “BAR”, and “BAZ”):
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<balance:infData
xmlns:balance="urn:ietf:params:xml:ns:epp:balance-0.3">
<balance:balance name=”FOO”>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
<balance:balance name=”BAR”>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
<balance:balance name=”BAZ”>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
</balance:infData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID>
</response>
</epp>
A Balance per Registrar (no “name” is needed):
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result>
<resData>
<balance:infData
xmlns:balance="urn:ietf:params:xml:ns:epp:balance-0.3">
<balance:balance>
<balance:currency>USD</balance:currency>
<balance:balanceAvailable>800.00
</balance:balanceAvailable>
<balance:creditLine>1000.00
</balance:creditLine>
<balance:cashBalance>-200.00
</balance:cashBalance>
<balance:executionLimit>-500.00
</balance:executionLimit>
<balance:notificationThreshold>500.00
</balance:notificationThreshold>
</balance:balance>
</balance:infData>
</resData>
<trID>
<clTRID>ABC-12345</clTRID>
<svTRID>54322-XYZ</svTRID>
</trID>
</response>
</epp>
Thanks,
--
JG
[cid87442*[email protected]]
James Gould
Fellow Engineer
[email protected]<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]>
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com<http://verisigninc.com/>
From: Barbara Bellis <[email protected]>
Date: Thursday, August 27, 2026 at 10:01 AM
To: "[email protected]" <[email protected]>
Subject: [EXTERNAL] [regext] Balance Mapping
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
Hi,
I’ve reviewed the EPP balance mapping and have discussed some feedback off list
with Jim Gould and Werner Staub.
The balance mapping works well for single accounts for registrars, with
multiple currencies. We have a model whereby registrars may have more than one
balance - in our case it’s based on registry operator customers. It would be
good for us if the infData object could have the option to support a list of
balances per registrar.
We also discussed inclusion of an optional “name” attribute for balances so
that balances can be easily identified. Setting of the name would be by server
policy and could have the TLD or Registry Operator Customer or some other
identifier. The server can return the full list of balances to the registrar
in the info response, or poll notification.
Thanks
Barbara Bellis,
Nominet.
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
