-
Notifications
You must be signed in to change notification settings - Fork 13
/
index.html
1113 lines (1111 loc) · 36.8 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta name="generator" content=
"HTML Tidy for HTML5 for Apple macOS version 5.6.0">
<title>
Credit Transfer Payment
</title>
<script src='https://www.w3.org/Tools/respec/respec-w3c-common' async
class='remove'></script>
<script class='remove'>
var respecConfig = {
shortName: "payment-method-credit-transfer",
edDraftURI: "https://w3c.github.io/payment-method-credit-transfer/",
specStatus: "ED",
editors: [
{ name: "Cyril Vignet",
company: "BPCE" },
{ name: "Vincent Kuntz",
company: "SWIFT / ISO 20022" },
{ name: "Matt Saxon",
company: "Worldpay" }
],
useExperimentalStyles: true,
license: "w3c-software-doc",
//previousMaturity: "FPWD",
//previousPublishDate: "1977-03-15",
wg: "Web Payments Working Group",
wgURI: "https://www.w3.org/Payments/WG/",
wgPublicList: "public-payments-wg",
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/83744/status",
issueBase: "https://github.com/w3c/payment-method-credit-transfer/issues",
localBiblio: {
"PAYMENTREQUESTAPI": {
title: "Payment Request API"
, href: "paymentrequest.html"
, authors: [
"Adrian Bateman"
, "Zach Koch"
, "Roy McElmurry"
, "Marcos Caceres"
]
, status: "WD"
},
"METHODIDENTIFIERS": {
title: "Payment Method Identifiers"
, href: "method-identifiers.html"
, authors: [
"Adrian Bateman"
, "Zach Koch"
, "Roy McElmurry"
, "Marcos Caceres"
]
, status: "WD"
},
"WEBIDL": {
title: "WebIDL Level 1"
, href: "https://www.w3.org/TR/WebIDL-1/ "
, authors: [
"Cameron McCormack"
, "Boris Zbarsky"
]
, status: "CR"
},
"CLDR": {
title: "Unicode Common Locale Data Repository"
, href: "http://cldr.unicode.org/"
}
}
};
</script>
<style>
dt { margin-top: 0.75em; }
table { margin-top: 0.75em; border-collapse:collapse; border-style:hidden hidden none hidden }
table thead { border-bottom:solid }
table tbody th:first-child { border-left:solid }
table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
li { margin-top: 0.5em; margin-bottom: 0.5em;}
</style>
</head>
<body>
<section id='abstract'>
<p>
This specification is a Payment Method specification for use with the
PaymentRequest API [[PAYMENTREQUESTAPI]]. With it, merchants and payers
can exchange information required for credit transfers across a variety
of payment systems.
</p>
</section>
<section id='sotd'>
<p>
The working group maintains <a href=
"https://github.com/w3c/payment-method-credit-transfer/issues">a list
of all bug reports that the group has not yet addressed</a>.
</p>
</section>
<section class='informative'>
<h2>
Introduction
</h2>
<p>
This specification is a Payment Method Specification used by the
PaymentRequest API [[!PAYMENTREQUESTAPI]] to support payment by credit
transfer.
</p>
</section>
<section id="dependencies">
<h2>
Dependencies
</h2>
<p>
This specification relies on several other underlying specifications.
</p>
<dl>
<dt>
Payment Request API
</dt>
<dd>
The term <dfn>PaymentRequest constructor</dfn> is defined by the
PaymentRequest API specification [[!PAYMENTREQUESTAPI]].
</dd>
<dt>
Payment Method Identifiers
</dt>
<dd>
The term <dfn data-lt="payment method identifiers">payment method
identifier</dfn> is defined by the Payment Method Identifier
specification [[!METHODIDENTIFIERS]].
</dd>
<dt>
Web IDL
</dt>
<dd>
The IDL in this specification is defined by Web IDL [[!WEBIDL]].
</dd>
<dt>
CLDR
</dt>
<dd>
Country codes used in this specification are only used for filtering;
country information is not part of the payment message. We thus align
with the choice of Payment Request API, which is to use [[!CLDR]].
</dd>
</dl>
</section>
<section id="examples">
<h2>
Examples
</h2>
<section>
<h3>
Faster Payments UK and BACS
</h3>
<pre class="example" title="BACS and Faster Payments Example">
const CreditTransferRequest = {
supportedNetworks: ["BACS", "UKFasterPayments"],
payeeAccountNumber: "12345678", // Bob Ltd.'s 8 digit UK bank account number
payeeName: "Bob Ltd.", // Merchant name
payeeBankCode: "12-34-56", // Bob Ltd.'s 6 digit sort code
payeePaymentIdentificationHumanReadable: "Payment from Alice, account number 87654321", // whilst payment reference is optional for BACS scheme, this text is used for reconciliation so the merchant can check they have been paid
payeePaymentIdentifierMachineReadable: "abcdefgh123456789" // unique transaction reference, not used by BACS scheme, but Payment App can use to dedeplicate
}
</pre>
<p>
This example refers to two credit transfer systems:
</p>
<ul>
<li>
<a href="https://www.bacs.co.uk/Pages/Home.aspx">BACS</a> Direct
Credit Scheme, a non-realtime scheme for UK domestic payments.
Payments typically take between 3 and 5 days to settle to the
destination account and there is no notification, merchants must
check their statements and manually reconcile using the 'reference'
(<code>payeePaymentIdentificationHumanReadable</code>)
</li>
<li>
<a href="http://www.fasterpayments.org.uk/">Faster Payments (UK)
Scheme</a>, which operates similar to BACS, but typically settling
in a few hours.
</li>
</ul>
</section>
<section>
<h3>
SEPA
</h3>
<pre class='example' title="SEPA Example">
const CreditTransferRequest =
{ supportedNetworks: ["SEPA"],
payeeAccountNumber: "FR7617519500040080394739390", // Marcel S.A. 27 digit IBAN bank account number
payeeName: "Marcel S.A.", // Merchant name
payeeBankCode: "CEPAFRPP751", // Marcel S.A. BIC code
payeePaymentIdentificationHumanReadable: "Achat Livre Victor Hugo ", // this information is for Alice to identify quickly her purchase. Alice's
Bank could display this line on the statement
payeePaymentIdentifierMachineReadable: "abcdefgh123456789" // unique transaction reference provided by merchant and used in the endtoEnd field in the SEPA Credit Transfer
}
</pre>
</section>
</section>
<section id="payer-initiated">
<h2>
Payer-Initiated Credit Transfers
</h2>
<section id="method-id-payer">
<h3>
Payment Method Identifier
</h3>
<p>
The <a>payment method identifier</a> string for Payer-Initiated
Credit Transfer Payment is <dfn data-dfn-type="dfn" id=
"dfn-payer-credit-transfer"><code>payer-credit-transfer</code></dfn>.
</p>
<p class="issue" title=
"Should we use a URL as a PMI instead of a short string?" data-number=
"59"></p>
<p class="issue" title=
"Do we need a form filler credit transfer payment method?" data-number=
"61"></p>
</section>
<section data-dfn-for="CreditTransferRequest" data-link-for=
"CreditTransferRequest">
<h3>
Data for the PaymentRequest constructor
</h3>
<p>
This section describes payment method specific data that is supplied
as part of the <code>data</code> argument to the PaymentRequest
constructor.
</p>
<section>
<h3>
<dfn>CreditTransferRequest</dfn> dictionary
</h3>
<pre class="idl">
dictionary CreditTransferRequest {
sequence<DOMString> requiredResponseFields;
sequence<DOMString> supportedNetworks;
sequence<DOMString> supportedCountries;
required DOMString payeeAccountNumber;
DOMString payeeName;
DOMString payeeAddress;
required DOMString payeeBankCode;
DOMString payeeIdentificationCode;
DOMString payeePaymentIdentificationHumanReadable;
required DOMString payeePaymentIdentificationMachineReadable;
DOMString sellerName;
DOMString sellerIdentificationCode;
DOMString purposeCode;
DOMString categoryPurposeCode;
DOMString chargeBearer;
DOMString preferredProcessingDate;
DOMString notificationURL;
};
</pre>
<dl>
<dt>
<dfn>requiredResponseFields</dfn> member
</dt>
<dd>
Contains the list of fields that the Payment App must attempt to
return, if this requirements cannot be met, e.g., the payment
instrument must fail as this is a push payment.
<p class="issue" title=
"Relationship between requiredResponseFields and PR API flow"
data-number="164"></p>
</dd>
<dt>
<dfn>supportedNetworks</dfn> member
</dt>
<dd>
The supportedNetworks field contains a sequence of identifiers
for credit transfer networks that the merchant accepts. This
field is optional. If a value is not provided then the merchant
accepts credit transfers from any credit transfer network.
<span class="note">Note: The Web Payments Working Group is still
discussing whether and how to maintain a database of supported
network identifiers.</span>
</dd>
<dt>
<dfn>supportedCountries</dfn> member
</dt>
<dd>
The supportedCountries field contains a sequence of [[!CLDR]]
identifiers of countries from which the merchant accepts credit
transfers. This field is optional. If a value is not provided
then the merchant accepts credit transfers from any country.
</dd>
<dt>
<dfn>payeeAccountNumber</dfn> member
</dt>
<dd>
This field indicates the account number of the payee (the
merchant) that will be used for the credit transfer. This will
typically be an IBAN number, or a domestic account number for
those countries that do not use IBAN.
</dd>
<dt>
<dfn>payeeBankCode</dfn> member
</dt>
<dd>
The Bank code of the payee that should be used along the
“payeeAccountNumber” in order to send the Credit Transfer.
</dd>
<dt>
<dfn>payeeName</dfn> member
</dt>
<dd>
The name of the payee known to the bank that holds the account
describe by “payeeAccountNumber”.
</dd>
<dt>
<dfn>payeeAddress</dfn> member
</dt>
<dd>
The address of the payee known by the bank that holds the account
describe by “payeeAccountNumber”.
</dd>
<dt>
<dfn>payeeIdentificationCode</dfn> member
</dt>
<dd>
An identification code provided by the payee.
</dd>
<dt>
<dfn>payeePaymentIdentificationHumanReadable</dfn> member
</dt>
<dd>
Human-readable remittance information explaining to the payer
what is being paid for.
</dd>
<dt>
<dfn>payeePaymentIdentificationMachineReadable</dfn> member
</dt>
<dd>
Remittance information used for automatic matching upon receipt
of the credit transfer.
<p class="issue" title=
"payeePaymentIdentificationMachineReadable redundant with PR API id?"
data-number="47"></p>
</dd>
<dt>
<dfn>sellerName</dfn> member
</dt>
<dd>
The name of a person or company in relation to whom a Beneficiary
receives a payment.
</dd>
<dt>
<dfn>sellerIdentificationCode</dfn> member
</dt>
<dd>
A code related to “sellerName”.
</dd>
<dt>
<dfn>purposeCode</dfn> member
</dt>
<dd>
The purpose of the credit transfer is the underlying reason for
the credit transfer transaction, i.e. information on the nature
of such transaction. Values are drawn from <a href=
"https://www.iso20022.org/documents/External_code_lists/ExternalCodeSets_1Q2016_11May2016_v1.xls">
ISO20022 External Code Sets</a>.
</dd>
<dt>
<dfn>categoryPurposeCode</dfn> member
</dt>
<dd>
The category purpose of the credit transfer is information on the
high level nature of transaction. Values are drawn from <a href=
"https://www.iso20022.org/documents/External_code_lists/ExternalCodeSets_1Q2016_11May2016_v1.xls">
ISO20022 External Code Sets</a>.
</dd>
<dt>
<dfn>chargeBearer</dfn> member
</dt>
<dd>
The chargeBearer member indicates how the charge of the credit
transfer will be split between the payee. Legal values are:
<ul>
<li>
<code>OUR</code>: payer pays
</li>
<li>
<code>SHARED</code>: fees are split
</li>
<li>
<code>BENE</code>: payee pays
</li>
</ul>
</dd>
<dt>
<dfn>preferredProcessingDate</dfn> member
</dt>
<dd>
The merchant's preferred processing date expressed as
"YYYY-MM-DD". See also SelectedProcessingDate in the
CreditTransferResponse.
</dd>
<dt>
<dfn>notificationURL</dfn> member
</dt>
<dd>
An end point for payment status updates. This specification does
not define how such endpoints will work.
</dd>
<dd></dd>
</dl>
</section>
</section>
<section data-dfn-for="CreditTransferResponse" data-link-for=
"CreditTransferResponse">
<h3>
Payment Method Response
</h3>
<p>
This section describes the response from the PaymentRequest API when
a user accepts payment with a Credit Transfer payment method.
</p>
<section>
<h3>
<dfn>CreditTransferResponse</dfn> dictionary
</h3>
<p>
The CreditTransferResponse message means that a message has been
submitted to the Payee's Bank, not that funds transfer has
occurred. The merchant should wait for notification from its Bank
that the payment has cleared.
</p>
<pre class="idl">
dictionary CreditTransferResponse {
required DOMString selectedProcessingDate;
required DOMString payerPaymentIdentification;
required DOMString payerBankCode;
required DOMString selectedNetwork;
DOMString payerIdentificationCode;
DOMString payerName;
DOMString buyerIdentificationCode;
DOMString buyerName;
DOMString statusInformation;
};
</pre>
<dl>
<dt>
<dfn>selectedProcessingDate</dfn> member
</dt>
<dd>
The date for commencing the execution of the payment request.
This date may be different from that requested by the Payee,
either because of a business rule (e.g., non business day, or a
preference from the payee to defer payment
</dd>
<dt>
<dfn>payerPaymentIdentification</dfn> member
</dt>
<dd>
A unique identifier for a given payer each Credit Transfer
Transaction presented to the payer Bank. This number will be
transmitted in the entire process of the handling of the credit
transfer transactions from acceptance until the finality of the
transaction. It must be returned in any exception handling
process-step by any party involved. The payer cannot request for
any other referencing information to be returned to him, in order
to identify a credit transfer. The payer must define the internal
structure of this reference; it can only be expected to be
meaningful to the payer.
</dd>
<dt>
<dfn>payerBankCode</dfn> member
</dt>
<dd>
The code of the bank which send the Credit Transfer. It could be
the BIC, like for SEPA, or any other Bank code
</dd>
<dt>
<dfn>selectedNetwork</dfn> member
</dt>
<dd>
The network used by the originator to send the credit transfer
</dd>
<dt>
<dfn>payerIdentificationCode</dfn> member
</dt>
<dd>
A code supplied by the payer.
</dd>
<dt>
<dfn>payerName</dfn> member
</dt>
<dd>
The name of the payer.
</dd>
<dt>
<dfn>buyerIdentificationCode</dfn> member
</dt>
<dd>
The buyer reference. The buyer may be a 3rd party to the payer,
if the payer is paying on behalf of another party.
</dd>
<dt>
<dfn>buyerName</dfn> member
</dt>
<dd>
The buyer name. The buyer may be a 3rd party to the payer. If the
payer is paying on behalf of another party.
</dd>
<dt>
<dfn>statusInformation</dfn> member
</dt>
<dd>
Payment status information (e.g., whether a payment is pending or
has completed).
</dd>
</dl>
</section>
</section>
</section>
<section id="payee-initiated">
<h2>
Payer-Initiated Through Payee Credit Transfers
</h2>
<p>
In this credit transfer method, the payee (or third party) initiates
the credit transfer. In some jurisdictions, credit transfers may be
initiated by a regulated third party such as the the payee's bank or,
under PSD2 in Europe, a Payment Initiation Service Provider (PISP).
</p>
<section id="method-id-payee">
<h3>
Payment Method Identifier
</h3>
<p>
The <a>payment method identifier</a> string for Payer-Initiated
through Payee Credit Transfer Payment is <dfn data-dfn-type="dfn" id=
"dfn-payee-credit-transfer"><code>payee-credit-transfer</code></dfn>.
</p>
</section>
<section data-dfn-for="PayeeCreditTransferRequest" data-link-for=
"PayeeCreditTransferRequest">
<h3>
Data for the PaymentRequest constructor
</h3>
<p>
The data supplied as part of the <code>data</code> argument to the
PaymentRequest constructor is the same as for
<code>payer-credit-transfer</code>.
</p>
</section>
<section data-dfn-for="PayeeCreditTransferResponse" data-link-for=
"PayeeCreditTransferResponse">
<h3>
Payment Method Response
</h3>
<p>
This section describes the response from the PaymentRequest API when
a user accepts payment with a Payee Credit Transfer payment method.
</p>
<section>
<h3>
<dfn>PayeeCreditTransferResponse</dfn> dictionary
</h3>
<pre class="idl">
dictionary PayeeCreditTransferResponse: CreditTransferResponse {
DOMString authorizationToken;
};
</pre>
<dl>
<dt>
<dfn>authorizationToken</dfn> member
</dt>
<dd>
The authorizationToken enables the payee (or third party) to
initiate the credit transfer.
</dd>
</dl>
</section>
</section>
</section>
<section id="security-privacy">
<h2>
Security and Privacy Considerations
</h2>
<p class="issue" title=
"What mechanisms (if any) do we need to provent data tampering?"
data-number="67"></p>
<p>
Owners of web sites SHOULD NOT store the payer's information except
where warranted, such as storage for future and recurring payments.
When information is stored, web site owners SHOULD take measures to
prevent its disclosure.
</p>
</section>
<section id="mapping-sepa">
<h2>
Appendix: Mappings to SEPA
</h2>
<p>
Here we map fields in this specification to Customer to Bank Credit
Transfer Initiation (DS-01) fields defined in <a href=
"http://www.europeanpaymentscouncil.eu/index.cfm/knowledge-bank/epc-documents/sepa-credit-transfer-rulebook-version-81/">
SEPA Credit Transfer Rulebook Version 8.1</a>. The SEPA Rulebook may
impose additional implementation restrictions (e.g., number of
characters) not defined in the current specification.
</p>
<section>
<h3>
CreditTransferRequest Fields and SEPA
</h3>
<table border="1">
<tr>
<th></th>
<th>
SEPA
</th>
</tr>
<tr>
<th>
supportedNetworks
</th>
<td>
AT-40: Identification code of the Scheme
</td>
</tr>
<tr>
<th>
payeeAccountNumber
</th>
<td>
AT-20: The IBAN of the account of the Beneficiary.
</td>
</tr>
<tr>
<th>
payeeBankCode
</th>
<td>
AT-23: the BIC code of the beneficiary. Note: Even if the BIC
could be derived from the IBAN in most of SEPA country, it may be
not the case in others, so this field is important. The merchant
should know the BIC of his account. This field could be also used
with another format of “bank identification code” for countries
not using BIC.
</td>
</tr>
<tr>
<th>
payeeName
</th>
<td>
AT-21: The name of the Beneficiary
</td>
</tr>
<tr>
<th>
payeeAddress
</th>
<td>
AT-22: The address of the Beneficiary
</td>
</tr>
<tr>
<th>
payeeIdentificationCode
</th>
<td>
AT-24: The Beneficiary identification code
</td>
</tr>
<tr>
<th>
payeePaymentIdentificationHumanReadable
</th>
<td>
AT-05: The Remittance Information sent by the Originator to the
Beneficiary in the Credit Transfer Instruction only if the
payeePaymentIdentificationMachineReadable is not provided.
</td>
</tr>
<tr>
<th>
payeePaymentIdentificationMachineReadable
</th>
<td>
AT-05: The Remittance Information sent by the Originator to the
Beneficiary in the Credit Transfer Instruction.
</td>
</tr>
<tr>
<th>
sellerName
</th>
<td>
AT-28: The name of the Beneficiary Reference Party
</td>
</tr>
<tr>
<th>
sellerIdentificationCode
</th>
<td>
AT-29: The identification code of the Beneficiary Reference Party
</td>
</tr>
<tr>
<th>
purposeCode
</th>
<td>
AT-44: The purpose of the credit transfer
</td>
</tr>
<tr>
<th>
categoryPurposeCode
</th>
<td>
AT-45: The category purpose of the credit transfer
</td>
</tr>
<tr>
<th>
preferredProcessingDate
</th>
<td>
...
</td>
</tr>
<tr>
<th>
notificationURL
</th>
<td>
...
</td>
</tr>
</table>
</section>
<section>
<h3>
CreditTransferResponse Fields and SEPA
</h3>
<table border="1">
<tr>
<th></th>
<th>
SEPA
</th>
</tr>
<tr>
<th>
selectedProcessingDate
</th>
<td>
AT-07: The Requested Execution Date of the instruction
</td>
</tr>
<tr>
<th>
payerPaymentIdentification
</th>
<td>
AT-41: The Originator’s reference of the Credit Transfer
Transaction (End to End Identification in ISO20022 definition)
</td>
</tr>
<tr>
<th>
payerBankCode
</th>
<td>
AT-06: The BIC of the Originator
</td>
</tr>
<tr>
<th>
selectedNetwork
</th>
<td>
AT-40: Identification code of the Scheme
</td>
</tr>
<tr>
<th>
payerIdentificationCode
</th>
<td>
AT-10: The Originator identification code
</td>
</tr>
<tr>
<th>
payerName
</th>
<td>
AT-02: The Name of the Originator
</td>
</tr>
<tr>
<th>
buyerIdentificationCode
</th>
<td>
AT-09: The identification code of the Originator Reference Party
</td>
</tr>
<tr>
<th>
buyerName
</th>
<td>
AT-08: Name of the Originator Reference Party of the Originator
Reference Party
</td>
</tr>
<tr>
<th>
statusInformation
</th>
<td>
None?
</td>
</tr>
</table>
</section>
</section>
<section id="mapping-iso20022">
<h2>
Appendix: Mappings to ISO 20022
</h2>
<p>
Here we map fields in this specification to ISO 20022 fields defined in
the <a href="https://www.iso20022.org/payments_dashboard.page">Payments
Dashboard</a>.
</p>
<section>
<h3>
CreditTransferRequest Fields and ISO 20022
</h3>
<table border="1">
<tr>
<th></th>
<th>
ISO 20022
</th>
</tr>
<tr>
<th>
supportedNetworks
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
payeeAccountNumber
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.CreditorAccount.Identification.IBAN
</td>
</tr>
<tr>
<th>
payeeBankCode
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
payeeName
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.Creditor.Name
</td>
</tr>
<tr>
<th>
payeeAddress
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
payeeIdentificationCode
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.Creditor.Identification.*
</td>
</tr>
<tr>
<th>
payeePaymentIdentificationHumanReadable
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
payeePaymentIdentificationMachineReadable
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
sellerName
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.UltimateCreditor.Name
</td>
</tr>
<tr>
<th>
sellerIdentificationCode
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.UltimateCreditor.Identification.*
</td>
</tr>
<tr>
<th>
purposeCode
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.Purpose
</td>
</tr>
<tr>
<th>
categoryPurposeCode
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.PaymentType.CategoryPurpose
</td>
</tr>
<tr>
<th>
preferredProcessingDate
</th>
<td>
pain.001.PaymentInformation.RequestedExecutionDate
</td>
</tr>
<tr>
<th>
notificationURL
</th>
<td>
pain.001.PaymentInformation.CreditTransferTransactionInformation.RelatedRemittanceInformation.RemittanceLocationDetails.ElectronicAddress
</td>
</tr>
</table>
</section>
<section>
<h3>
CreditTransferResponse Fields and ISO 20022
</h3>
<table border="1">
<tr>
<th></th>
<th>
ISO 20022
</th>
</tr>
<tr>
<th>
selectedProcessingDate
</th>
<td>
pain.002.OriginalPaymentInformationAndStatus.TransactionInformationAndStatus.OriginalTransactionReference.RequestedExecutionDate
</td>
</tr>
<tr>
<th>
payerPaymentIdentification
</th>
<td>
pain.002.OriginalPaymentInformationAndStatus.TransactionInformationAndStatus.OriginalEndToEndId
</td>
</tr>
<tr>
<th>
payerBankCode
</th>
<td>
None?
</td>
</tr>
<tr>
<th>
selectedNetwork
</th>