Validate Payment Eligibility Test Data using Account Numbers rather than Enterprise ID's

[Schoenbaum]

Can Visa provide test data for the Payment Eligibility Test API that uses debtor and creditor account numbers rather than enterprise ID's?  For our use case we will be passing account numbers, not enterprise ID's, and need data that will work in the sandbox for our testing purposes.

Alternatively, can the account number be parsed out of the debtor and creditor enterprise ID's provided in the test data?

[DianaTranYee]

Hey @Schoenbaum,

I'll take a look and get back to you soon.

[Schoenbaum]

Thank you. Looking forward to what you find out.

[Schoenbaum]

I am assuming that this would be a relatively simple issue to address.  I am hoping for an answer soon so that I can continue testing our interface.  A timely reply would be much appreciated.

[ricardo_visa]

Hi @Schoenbaum - very sorry about the delay. I am escalating this. Will make sure we get you a response shortly.

[DianaTranYee]

Hey @Schoenbaum,

Thanks for the follow ups and apologies for the delay. All are APIs working on PAN/Token and Alias ID. There is no provision of extracting the account number from enterprise id.

[Schoenbaum]

Ok.  I understand that the account number cannot be derived from the Visa Enterprise ID.  In that case what I am looking for are the corresponding account number to use with the Visa B2B Validate Payment Eligibility API.  For example, the sample data provided for a successful call is:

{
"debtorBankBic": "CITIGB2L",
"creditorBankBic": "CITIGB3L",
"debtorEnterpriseId": "V-USA-USD-52358698-100669974-001",
"creditorEnterpriseId": "V-GBR-EUR-17062019-100669769-001",
"settlementCurrency": "JPY",
"settlementAmount": 100
}

However, based on our use case, we will be passing debtorAccountNumber and creditorAccountNumber instead of debtorEnterpriseId and creditorEnterpriseId.  Can you provide the account numbers in the sandbox data that correspond to the debtorEnterpriseId and creditorEnterpriseId values in the sample?

{
"debtorBankBic": "CITIGB2L",
"creditorBankBic": "CITIGB3L",
"debtorAccountNumber": "???",                                         <<<<<<<<<
"creditorAccountNumber": "???",                                       <<<<<<<<<
"settlementCurrency": "JPY",
"settlementAmount": 100
}

[mcshola]

Hello,

The debtorEnterpriseID and creditorEnterpriseID - represent the enterprise on behalf of who the Issuer/bank is making the call or originating the payment.

Please let me understand your use case, where the debtorAccountNumber and creditorAccountNumber is an equivalent? From the API reference, debtorEnterpriseID and creditorEnterpriseID are optional, while debtorAccountNumber and creditorAccountNumber is required. 

Are you getting and error? what kind of error are you getting?

https://developer.visa.com/capabilities/vba/reference#vba__payments__v1__validate_payments

[Schoenbaum]

My issue is entirely related to the sample test data provided by Visa for the Validate Payment Eligibility API. This API must be called with either a Visa Enterprise ID, an account number, or an IBAN value for both the debtor and the creditor. The sample test data provided only specifies Visa Enterprise IDs for both the debtor and creditor. In our use case we do not have Visa Enterprise ID values for the debtor and creditor, we intend to make the calls with debtor and creditor account numbers. Because the sample test data provided corresponds to values in the Visa Developer Sandbox I need to know the account numbers I can use for the Success scenario so that I can test our interface against the sandbox.

[ricardo_visa · Accepted solution]

Gotcha - You can actually add any random account number, in the sandbox environment. We have limited validations in sandbox. For example, if you hit the below request, you should get a success response:

{
"debtorBankBic": "CITIGB2L",
"creditorBankBic": "CITIGB3L",
"debtorAccountNumber": "1",
"creditorAccountNumber": "1",
"settlementCurrency": "JPY",
"settlementAmount": 100
}

Lets try that and let me know what you're getting or if you need any more information.