| Test Name | automatic-payments_api_timezone_test-module_v2 |
|---|---|
| Variant | client_auth_type=private_key_jwt, fapi_auth_request_method=pushed, fapi_profile=openbanking_brazil, fapi_response_mode=plain_response |
| Test ID | mKxnjkbQ1IxXwk4 https://web.conformance.directory.openbankingbrasil.org.br/log-detail.html?public=true&log=mKxnjkbQ1IxXwk4 |
| Created | 2025-03-11T01:09:23.777079960Z |
| Description | Semear Testes Funcionais |
| Test Version | 5.1.17 build: 0c36b0e931310d78f1e1d40dc3600671d1308707 |
| Test Owner | cristian.vieira@semeartech.com.br https://auth.sandbox.directory.openbankingbrasil.org.br |
| Plan ID | 3flyAGRXyhTbz https://web.conformance.directory.openbankingbrasil.org.br/plan-detail.html?public=true&plan=3flyAGRXyhTbz |
| Exported From | https://web.conformance.directory.openbankingbrasil.org.br |
| Exported By | cristian.vieira@semeartech.com.br https://auth.sandbox.directory.openbankingbrasil.org.br |
| Suite Version | 5.1.17 build: 5b98ab733f7260233f69078b044cb3749b73bdf4 |
| Exported | 2025-04-16 18:15:15 (UTC) |
| Status: FINISHED Result: PASSED |
| SUCCESS 715 FAILURE 0 WARNING 0 REVIEW 0 INFO 9 |
| 2025-03-11 01:09:23 |
INFO
|
TEST-RUNNER
Test instance mKxnjkbQ1IxXwk4 created
|
||||||||||||||
|
||||||||||||||||
| 2025-03-11 01:09:23 |
SUCCESS
|
CreateRedirectUri
Created redirect URI
|
||
|
||||
| 2025-03-11 01:09:23 |
|
GetDynamicServerConfiguration
HTTP request
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
RESPONSE
|
GetDynamicServerConfiguration
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetDynamicServerConfiguration
Successfully parsed server configuration
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2025-03-11 01:09:24 | SUCCESS |
AddMTLSEndpointAliasesToEnvironment
Added mtls_endpoint_aliases to environment
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
CheckServerConfiguration
Found required server configuration keys
|
||
|
||||
| 2025-03-11 01:09:24 |
|
FetchServerKeys
Fetching server key
|
||
|
||||
| 2025-03-11 01:09:24 |
|
FetchServerKeys
HTTP request
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
RESPONSE
|
FetchServerKeys
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
|
FetchServerKeys
Found JWK set string
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
FetchServerKeys
Found server JWK set
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
CheckServerKeysIsValid
Server JWKs is valid
|
||
|
||||
| 2025-03-11 01:09:24 | SUCCESS |
ValidateServerJWKs
Valid server JWKs: keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-03-11 01:09:24 | SUCCESS |
CheckForKeyIdInServerJWKs
All keys contain kids
|
|
|
||
| 2025-03-11 01:09:24 | SUCCESS |
EnsureServerJwksDoesNotContainPrivateOrSymmetricKeys
Jwks does not contain any private or symmetric keys
|
|
|
||
| 2025-03-11 01:09:24 | SUCCESS |
FAPIEnsureMinimumServerKeyLength
Validated minimum key lengths for server_jwks
|
||
|
||||
| Validating Well-Known URI |
| 2025-03-11 01:09:24 |
SUCCESS
|
CheckDiscEndpointDiscoveryUrl
discoveryUrl
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
EnsureWellKnownUriIsRegistered
Found Authorisation Server with provided Well-Known URL in the Directory Participants List
|
||||
|
||||||
| Validating Authorisation Server has supported Endpoint |
| 2025-03-11 01:09:24 |
SUCCESS
|
GetAuthServerFromParticipantsEndpoint
Found organisation
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetAuthServerFromParticipantsEndpoint
Found auth server from participants endpoint
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetAutomaticPaymentRecurringConsentV2Endpoint
Inserted consent endpoint into config
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetAutomaticPaymentPixRecurringV2Endpoint
Inserted resource endpoint into config
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetStaticClientConfiguration
Found a static client object
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
AddOpenIdScope
Added scope of 'payments openid' to client's scope
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
|
ValidateMTLSCertificatesHeader
No certificate authority found for MTLS
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
ValidateMTLSCertificatesHeader
MTLS certificates header is valid
|
|
|
||
| 2025-03-11 01:09:24 |
|
ExtractMTLSCertificatesFromConfiguration
No certificate authority found for MTLS
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
ExtractMTLSCertificatesFromConfiguration
Mutual TLS authentication credentials loaded
|
||||
|
||||||
| 2025-03-11 01:09:24 |
|
Scopes and Permissions Builder
ScopesAndPermissionsBuilder was correctly instantiated
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
Scopes and Permissions Builder:
Providing Permissions/Scopes:
|
||||
|
||||||
| 2025-03-11 01:09:24 | SUCCESS |
ValidateClientJWKsPrivatePart
Valid client JWKs: keys are valid JSON, contain the required fields, the private/public exponents match and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
ExtractJWKsFromStaticClientConfiguration
Extracted client JWK
|
||||
|
||||||
| 2025-03-11 01:09:24 | SUCCESS |
CheckForKeyIdInClientJWKs
All keys contain kids
|
|
|
||
| 2025-03-11 01:09:24 | SUCCESS |
CheckDistinctKeyIdValueInClientJWKs
Distinct 'kid' value in all keys of client_jwks
|
||
|
||||
| 2025-03-11 01:09:24 | SUCCESS |
FAPIBrazilCheckKeyAlgInClientJWKs
Keys in client JWKS all have permitted 'alg'
|
||
|
||||
| 2025-03-11 01:09:24 | SUCCESS |
FAPIEnsureMinimumClientKeyLength
Validated minimum key lengths for client_jwks
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
ValidateMTLSCertificatesAsX509
Mutual TLS authentication cert validated as X.509
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
AddRecurringPaymentResourceUrlToConfig
resourceUrl was added to the config
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
CreateSweepingRecurringConfigurationObjectWithAllFields
The recurringConfiguration object has been created
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
AddRecurringPaymentConsentRequestBodyToConfig
Consent request body was added to the config
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
GetResourceEndpointConfiguration
Found a resource endpoint object
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
SetProtectedResourceUrlToSingleResourceEndpoint
Set protected resource URL
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
ExtractTLSTestValuesFromResourceConfiguration
Extracted TLS information from resource endpoint
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
ExtractTLSTestValuesFromOBResourceConfiguration
Extracted TLS information from resource endpoint
|
||||
|
||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
EditRecurringPaymentsConsentBodyToSetSweepingStartDateTimeToOneHourInTheFuture
The startDateTime field has been set
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
EditRecurringPaymentsConsentBodyToRemoveStartDateTime
The startDateTime field has been removed from the payload
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
AddManuLocalInstrument
Added localInstrument to environment
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
AddAutomaticPaymentToTheResource
Hardcoded brazilPixPayment object was added to the resource
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
SetAutomaticPaymentAmountTo300
The amount for the next automatic payment has been set
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
PrepareToPostConsentRequest
Call to consent API will be an HTTP POST
|
|
|
||
| 2025-03-11 01:09:24 |
SUCCESS
|
SetProtectedResourceUrlToRecurringPaymentsEndpoint
Endpoint added
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
EditRecurringPaymentBodyToSetUserDefinedCreditorAccount
The creditorAccount field has been added to the recurring payment request body
|
||
|
||||
| 2025-03-11 01:09:24 |
SUCCESS
|
EditRecurringPaymentsBodyToRemoveProxy
The proxy field has been removed from the payload
|
||
|
||||
| 2025-03-11 01:09:24 |
|
automatic-payments_api_timezone_test-module_v2
Setup Done
|
|
|
||
| Use client_credentials grant to obtain Brazil consent |
| 2025-03-11 01:09:24 |
SUCCESS
|
CreateTokenEndpointRequestForClientCredentialsGrant
Created token endpoint request
|
||||
|
||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
SetRecurringPaymentsScopeOnTokenEndpointRequest
Set scope parameter to 'recurring-payments'
|
||||
|
||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
CreateClientAuthenticationAssertionClaims
Created client assertion claims
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:09:24 |
SUCCESS
|
SignClientAuthenticationAssertion
Signed the client assertion
|
||
|
||||
| 2025-03-11 01:09:24 |
|
AddClientAssertionToTokenEndpointRequest
Added client assertion
|
||||||||
|
||||||||||
| 2025-03-11 01:09:24 |
|
CallTokenEndpoint
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:25 |
RESPONSE
|
CallTokenEndpoint
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:25 |
SUCCESS
|
CallTokenEndpoint
Parsed token endpoint response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:25 |
SUCCESS
|
CheckIfTokenEndpointResponseError
No error from token endpoint
|
|
|
||
| 2025-03-11 01:09:25 |
SUCCESS
|
CheckForAccessTokenValue
Found an access token
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
ExtractAccessTokenFromTokenResponse
Extracted the access token
|
||||
|
||||||
| 2025-03-11 01:09:25 | SUCCESS |
ExtractExpiresInFromTokenEndpointResponse
Extracted 'expires_in'
|
||
|
||||
| 2025-03-11 01:09:25 | SUCCESS |
ValidateExpiresIn
expires_in passed all validation checks
|
||
|
||||
| 2025-03-11 01:09:25 |
|
CreateEmptyResourceEndpointRequestHeaders
Created empty headers
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
AddFAPIAuthDateToResourceEndpointRequest
Added x-fapi-auth-date to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:25 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
CreateIdempotencyKey
Created idempotency key
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
AddIdempotencyKeyHeader
Added x-idempotency-key to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
CreatePaymentConsentRequest
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
FAPIBrazilExtractClientMTLSCertificateSubject
Extracted subject from MTLS certificate
|
||||||||
|
||||||||||
| 2025-03-11 01:09:25 | SUCCESS |
AddAudAsPaymentConsentUriToRequestObject
Added aud to request object claims
|
||
|
||||
| 2025-03-11 01:09:25 |
|
AddIssAsCertificateOuToRequestObject
Added iss value based on TLS certificate organizational unit to request object claims
|
||
|
||||
| 2025-03-11 01:09:25 | SUCCESS |
AddJtiAsUuidToRequestObject
Added jti to request object claims
|
||
|
||||
| 2025-03-11 01:09:25 | SUCCESS |
AddIatToRequestObject
Added iat to request object claims
|
||
|
||||
| 2025-03-11 01:09:25 |
SUCCESS
|
ValidateOrganizationJWKsPrivatePart
Valid organization JWKs: keys are valid JSON, contain the required fields, the private/public exponents match and are correctly encoded using unpadded base64url
|
|
|
||
| 2025-03-11 01:09:25 |
SUCCESS
|
FAPIBrazilSignPaymentConsentRequest
Signed the request
|
||||||||
|
||||||||||
| 2025-03-11 01:09:25 |
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:26 |
RESPONSE
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 |
SUCCESS
|
FAPIBrazilCallPaymentConsentEndpointWithBearerToken
Payment consent endpoint response
|
||||||||
|
||||||||||
| Validate Consent Self link |
| 2025-03-11 01:09:26 |
SUCCESS
|
ValidateSelfLinkRegex
Self Link matches the regex
|
||
|
||||
| 2025-03-11 01:09:26 |
|
SaveOldValues
Saving old environment values
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:09:26 |
|
SetProtectedResourceUrlToConsentSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/recurring-consents/urn:semear:8e024e5b-a09d-4035-b8d7-4fe965f7b305
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:09:26 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:26 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:26 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:26 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:09:26 |
|
LoadOldValues
Loading old environment values
|
|
|
||
| 2025-03-11 01:09:26 |
|
EnsureContentTypeApplicationJwt
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 | SUCCESS |
EnsureContentTypeApplicationJwt
endpoint_response Content-Type: header is application/jwt
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
EnsureHttpStatusCodeIs201
resource endpoint returned the expected http status
|
||||
|
||||||
| 2025-03-11 01:09:26 | SUCCESS |
ExtractSignedJwtFromResourceResponse
Found and parsed the JWT from payment consent endpoint
|
||||||
|
||||||||
| 2025-03-11 01:09:26 | SUCCESS |
FAPIBrazilValidateResourceResponseSigningAlg
Response was signed with PS256
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
FAPIBrazilValidateResourceResponseTyp
'typ' is the header of the JWT returned in the API response is 'JWT'
|
||
|
||||
| 2025-03-11 01:09:26 |
SUCCESS
|
FAPIBrazilGetKeystoreJwksUri
Determined organisation jwks uri
|
||
|
||||
| 2025-03-11 01:09:26 |
|
FetchServerKeys
Fetching server key
|
||
|
||||
| 2025-03-11 01:09:26 |
|
FetchServerKeys
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:26 |
RESPONSE
|
FetchServerKeys
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 |
|
FetchServerKeys
Found JWK set string
|
||
|
||||
| 2025-03-11 01:09:26 |
SUCCESS
|
FetchServerKeys
Found server JWK set
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
ValidateResourceResponseSignature
endpoint_response_jwt signature validated
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
ValidateResourceResponseJwtClaims
Resource endpoint response JWS iss, aud, exp, iat, auth_time, acr & nbf claims passed validation checks
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
ExtractRecurringConsentIdFromConsentEndpointResponse
Extracted the recurring consent id
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
CheckForFAPIInteractionIdInResourceResponse
Found x-fapi-interaction-id
|
||
|
||||
| 2025-03-11 01:09:26 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:09:26 |
SUCCESS
|
FAPIBrazilAddRecurringConsentIdToClientScope
Added scope of 'recurring-payments openid recurring-consent:urn:semear:8e024e5b-a09d-4035-b8d7-4fe965f7b305' to client's scope
|
||||||||
|
||||||||||
| 2025-03-11 01:09:26 |
|
SaveAccessToken
Condition ran but did not log anything
|
|
|
||
| Validate consents response |
| 2025-03-11 01:09:26 |
|
PostRecurringConsentOASValidatorV2
Looking up data on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The data element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
|
PostRecurringConsentOASValidatorV2
Looking up data on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The data element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConsentId on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConsentId element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConsentId on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:26 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConsentId element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up loggedUser on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The loggedUser element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up loggedUser on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The loggedUser element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up document on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The document element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up document on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The document element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up identification on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The identification element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up identification on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The identification element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up rel on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The rel element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up rel on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The rel element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up businessEntity on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The businessEntity element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up businessEntity on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The businessEntity element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up document on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The document element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up document on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The document element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up identification on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The identification element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up identification on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The identification element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up rel on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The rel element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up rel on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The rel element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up creditors on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The creditors element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up personType on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The personType element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up personType on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The personType element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up cpfCnpj on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The cpfCnpj element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up cpfCnpj on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The cpfCnpj element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up name on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The name element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up name on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The name element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up creationDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The creationDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up creationDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The creationDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up expirationDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The expirationDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up expirationDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The expirationDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up debtorAccount on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The debtorAccount element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up debtorAccount on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The debtorAccount element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up ispb on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The ispb element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up ispb on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The ispb element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up issuer on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The issuer element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up issuer on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The issuer element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up number on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The number element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up number on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The number element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up accountType on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The accountType element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up accountType on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The accountType element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
INFO
|
PostRecurringConsentOASValidatorV2
Unable to find element automatic on the PostRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up sweeping on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The sweeping element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up sweeping on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The sweeping element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up periodicLimits on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The periodicLimits element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up periodicLimits on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The periodicLimits element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up day on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The day element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up day on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The day element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up week on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The week element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up week on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The week element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up month on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The month element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up month on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The month element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up year on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The year element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up year on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The year element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up quantityLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The quantityLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up transactionLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The transactionLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up startDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The startDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up startDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The startDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
INFO
|
PostRecurringConsentOASValidatorV2
Unable to find element vrp on the PostRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up links on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The links element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up links on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The links element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up self on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The self element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up self on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The self element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up meta on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The meta element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up meta on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The meta element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up requestDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The requestDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up requestDateTime on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The requestDateTime element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up accountType on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The accountType element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PostRecurringConsentOASValidatorV2
Looking up status on the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
PostRecurringConsentOASValidatorV2
The status element is present in the PostRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
ValidateVersionHeader2d0d0
Successfully validated the "x-v" header
|
|
|
||
| 2025-03-11 01:09:27 |
SUCCESS
|
EnsurePaymentConsentStatusWasAwaitingAuthorisation
Consent was in the expected state after redirect
|
||||
|
||||||
| Checking the created consent - Expecting AWAITING_AUTHORISATION status |
| 2025-03-11 01:09:27 |
|
AddJWTAcceptHeader
Adding jwt to accept header
|
|
|
||
| 2025-03-11 01:09:27 |
|
ExpectJWTResponse
Expecting jwt from endpoint response
|
|
|
||
| 2025-03-11 01:09:27 |
|
PrepareToFetchConsentRequest
Fetching consent from consent API
|
||||
|
||||||
| 2025-03-11 01:09:27 |
|
Load client_credential access token
|
||||
|
||||||
| 2025-03-11 01:09:27 |
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:28 |
RESPONSE
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:28 |
SUCCESS
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
Payment consent endpoint response
|
||||||||
|
||||||||||
| Validate Consent Self link |
| 2025-03-11 01:09:28 |
SUCCESS
|
ValidateSelfLinkRegex
Self Link matches the regex
|
||
|
||||
| 2025-03-11 01:09:28 |
|
SaveOldValues
Saving old environment values
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:09:28 |
|
SetProtectedResourceUrlToConsentSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/recurring-consents/urn:semear:8e024e5b-a09d-4035-b8d7-4fe965f7b305
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:09:28 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:09:28 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:28 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:09:28 |
|
Load client_credential access token
|
||||
|
||||||
| 2025-03-11 01:09:28 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:28 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:28 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:09:28 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:09:28 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:09:28 |
|
LoadOldValues
Loading old environment values
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
EnsurePaymentConsentStatusWasAwaitingAuthorisation
Consent was in the expected state after redirect
|
||||
|
||||||
| Validate GET Consent Response |
| 2025-03-11 01:09:28 |
SUCCESS
|
ExtractSignedJwtFromResourceResponse
Found and parsed the JWT from payment consent endpoint
|
||||||
|
||||||||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up data on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The data element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up data on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The data element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConsentId on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConsentId element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConsentId on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConsentId element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up loggedUser on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The loggedUser element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up loggedUser on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The loggedUser element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up businessEntity on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The businessEntity element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up businessEntity on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The businessEntity element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up creditors on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creditors element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up personType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The personType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up personType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The personType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up cpfCnpj on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The cpfCnpj element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up cpfCnpj on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The cpfCnpj element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up name on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The name element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up name on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The name element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up creationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:28 |
|
GetRecurringConsentOASValidatorV2
Looking up creationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up expirationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The expirationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up expirationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The expirationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up debtorAccount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The debtorAccount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up debtorAccount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The debtorAccount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up ispb on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ispb element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up ispb on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ispb element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up issuer on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The issuer element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up issuer on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The issuer element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up number on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The number element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up number on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The number element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
INFO
|
GetRecurringConsentOASValidatorV2
Unable to find element automatic on the GetRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up sweeping on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The sweeping element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up sweeping on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The sweeping element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up periodicLimits on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The periodicLimits element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up periodicLimits on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The periodicLimits element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up day on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The day element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up day on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The day element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up week on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The week element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up week on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The week element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up month on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The month element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up month on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The month element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up year on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The year element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up year on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The year element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up startDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The startDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up startDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The startDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
INFO
|
GetRecurringConsentOASValidatorV2
Unable to find element vrp on the GetRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up links on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The links element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up links on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The links element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up self on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The self element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up self on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The self element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up meta on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The meta element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up meta on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The meta element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up requestDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The requestDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up requestDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The requestDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
ValidateVersionHeader2d0d0
Successfully validated the "x-v" header
|
|
|
||
| 2025-03-11 01:09:29 |
SUCCESS
|
AddRecurringConsentIdToPaymentBody
The recurringConsentId has been added to the payments request payload
|
||
|
||||
| Make request to authorization endpoint |
| 2025-03-11 01:09:29 |
SUCCESS
|
CreateAuthorizationEndpointRequestFromClientInformation
Created authorization endpoint request
|
||||||
|
||||||||
| 2025-03-11 01:09:29 | SUCCESS |
AddEssentialAcrClaimWithNoValuesToAuthorizationEndpointRequest
Added acr claim to authorization_endpoint_request
|
||
|
||||
| 2025-03-11 01:09:29 |
|
CreateRandomStateValue
Created state value
|
||||
|
||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
AddStateToAuthorizationEndpointRequest
Added state parameter to request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:29 |
|
CreateRandomNonceValue
Created nonce value
|
||||
|
||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
AddNonceToAuthorizationEndpointRequest
Added nonce parameter to request
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
SetAuthorizationEndpointRequestResponseTypeToCodeIdtoken
Added response_type parameter to request
|
||||||||||||||
|
||||||||||||||||
| 2025-03-11 01:09:29 |
|
CreateRandomCodeVerifier
Created code_verifier value
|
||
|
||||
| 2025-03-11 01:09:29 |
|
CreateS256CodeChallenge
Created code_challenge value
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddCodeChallengeToAuthorizationEndpointRequest
Added code_challenge and code_challenge_method parameters to request
|
||||||||||||||||||
|
||||||||||||||||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
ConvertAuthorizationEndpointRequestToRequestObject
Created request object claims
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddNbfToRequestObject
Added nbf to request object claims
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddExpToRequestObject
Added exp to request object claims
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddAudToRequestObject
Added aud to request object claims
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddIssToRequestObject
Added iss to request object claims
|
||
|
||||
| 2025-03-11 01:09:29 | SUCCESS |
AddClientIdToRequestObject
Added client_id to request object claims
|
||
|
||||
| 2025-03-11 01:09:29 |
SUCCESS
|
SignRequestObject
Signed the request object
|
||||||||
|
||||||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
BuildRequestObjectPostToPAREndpoint
|
||
|
||||
| 2025-03-11 01:09:29 |
SUCCESS
|
CreateClientAuthenticationAssertionClaims
Created client assertion claims
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:09:29 | SUCCESS |
UpdateClientAuthenticationAssertionClaimsWithISSAud
Updated audience in client assertion claims
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:09:29 |
SUCCESS
|
SignClientAuthenticationAssertion
Signed the client assertion
|
||
|
||||
| 2025-03-11 01:09:29 |
SUCCESS
|
AddClientAssertionToPAREndpointParameters
Added client assertion to request
|
||
|
||||
| 2025-03-11 01:09:29 |
|
CallPAREndpoint
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:09:30 |
RESPONSE
|
CallPAREndpoint
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:09:30 | SUCCESS |
CallPAREndpoint
Parsed pushed authorization request endpoint response
|
||||
|
||||||
| 2025-03-11 01:09:30 | SUCCESS |
CheckPAREndpointResponse201WithNoError
pushed authorization request endpoint correct response.
|
|
|
||
| 2025-03-11 01:09:30 | SUCCESS |
CheckForRequestUriValue
Found valid request_uri
|
||
|
||||
| 2025-03-11 01:09:30 | SUCCESS |
CheckForPARResponseExpiresIn
Found expires_in
|
||
|
||||
| 2025-03-11 01:09:30 | SUCCESS |
FAPIBrazilOBCheckPARResponseExpiresIn
expires_in is more than or equal to 60 seconds
|
||
|
||||
| 2025-03-11 01:09:30 |
SUCCESS
|
ExtractRequestUriFromPARResponse
Extracted the request_uri: urn:ietf:params:oauth:request_uri:bdf24565-b778-41ae-9598-c50bf66c94ac
|
|
|
||
| 2025-03-11 01:09:30 | SUCCESS |
EnsureMinimumRequestUriEntropy
Calculated shannon entropy seems sufficient
|
||||||
|
||||||||
| 2025-03-11 01:09:30 | SUCCESS |
BuildRequestObjectByReferenceRedirectToAuthorizationEndpoint
Sending to authorization endpoint
|
||
|
||||
| 2025-03-11 01:09:30 |
REDIRECT
|
automatic-payments_api_timezone_test-module_v2
Redirecting to authorization endpoint
|
||
|
||||
| 2025-03-11 01:10:28 |
INCOMING
|
automatic-payments_api_timezone_test-module_v2
Incoming HTTP request to /test/a/Semear-Funcional/callback
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||||
| 2025-03-11 01:10:28 |
SUCCESS
|
CreateRandomImplicitSubmitUrl
Created random implicit submission URL
|
||
|
||||
| 2025-03-11 01:10:28 |
OUTGOING
|
automatic-payments_api_timezone_test-module_v2
Response to HTTP request to test instance mKxnjkbQ1IxXwk4
|
||||
|
||||||
| 2025-03-11 01:10:28 |
INCOMING
|
automatic-payments_api_timezone_test-module_v2
Incoming HTTP request to /test/a/Semear-Funcional/implicit/5sL5dKZTh5HQOsShD8b4
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||||
| 2025-03-11 01:10:28 |
OUTGOING
|
automatic-payments_api_timezone_test-module_v2
Response to HTTP request to test instance mKxnjkbQ1IxXwk4
|
||||||||
|
||||||||||
| 2025-03-11 01:10:28 |
|
ExtractImplicitHashToCallbackResponse
Extracted response from URL fragment
|
||
|
||||
| 2025-03-11 01:10:28 |
SUCCESS
|
ExtractImplicitHashToCallbackResponse
Extracted the hash values
|
||||||
|
||||||||
| 2025-03-11 01:10:28 |
REDIRECT-IN
|
automatic-payments_api_timezone_test-module_v2
Authorization endpoint response captured
|
||||||||||
|
||||||||||||
| Verify authorization endpoint response |
| 2025-03-11 01:10:28 | SUCCESS |
RejectErrorInUrlQuery
'error' is not present in URL query returned from authorization endpoint
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
RejectAuthCodeInUrlQuery
Authorization code is not present in URL query returned from authorization endpoint
|
|
|
||
| 2025-03-11 01:10:28 |
SUCCESS
|
CheckMatchingCallbackParameters
Callback parameters successfully verified
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
RejectStateInUrlQueryForHybridFlow
state is correctly not present in URL query returned from authorization endpoint (as in the hybrid flow it must be returned in the URL fragment/hash only)
|
|
|
||
| 2025-03-11 01:10:28 |
SUCCESS
|
CheckIfAuthorizationEndpointError
No error from authorization endpoint
|
|
|
||
| 2025-03-11 01:10:28 |
SUCCESS
|
ValidateSuccessfulHybridResponseFromAuthorizationEndpoint
authorization endpoint response does not include unexpected parameters
|
||||||
|
||||||||
| 2025-03-11 01:10:28 | SUCCESS |
CheckStateInAuthorizationResponse
State in response correctly returned
|
||
|
||||
| 2025-03-11 01:10:28 |
|
ValidateIssIfPresentInAuthorizationResponse
No 'iss' value in authorization response.
|
|
|
||
| 2025-03-11 01:10:28 |
SUCCESS
|
ExtractAuthorizationCodeFromAuthorizationResponse
Found authorization code
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
EnsureMinimumAuthorizationCodeLength
Authorization code is of sufficient length
|
||||
|
||||||
| 2025-03-11 01:10:28 | SUCCESS |
EnsureMinimumAuthorizationCodeEntropy
Calculated shannon entropy seems sufficient
|
||||||
|
||||||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdTokenFromAuthorizationResponseEncryption
The client has a valid asymmetric key to decrypt the id_token
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
ExtractIdTokenFromAuthorizationResponse
Found and parsed the id_token from authorization_endpoint_response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdToken
ID token iss, aud, exp, iat, auth_time, acr & nbf claims passed validation checks
|
|
|
||
| 2025-03-11 01:10:28 |
|
ValidateIdTokenStandardClaims
sub is a string with content
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdTokenStandardClaims
id_token claims are valid
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdTokenNonce
Nonce values match
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdTokenACRClaimAgainstRequest
Nothing to check; the conformance suite did not request an acr claim in request object
|
|
|
||
| 2025-03-11 01:10:28 |
SUCCESS
|
ValidateIdTokenSignature
id_token signature validated
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
CheckForSubjectInIdToken
Found 'sub' in id_token
|
||
|
||||
| 2025-03-11 01:10:28 |
|
EnsureIdTokenUpdatedAtValid
id_token response does not contain 'updated_at'
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateEncryptedIdTokenHasKid
kid was found in the encrypted ID token header
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
EnsureIdTokenContainsKid
kid was found in the ID token header
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
FAPIValidateIdTokenSigningAlg
id_token was signed with a permitted algorithm
|
||||
|
||||||
| 2025-03-11 01:10:28 | SUCCESS |
FAPIValidateIdTokenEncryptionAlg
id_token was encrypted with a permitted algorithm
|
||
|
||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateIdTokenEncrypted
id_token was encrypted
|
|
|
||
| 2025-03-11 01:10:28 | SUCCESS |
FAPIBrazilValidateIdTokenACRClaim
acr value in id_token is one of the permitted values
|
||||
|
||||||
| 2025-03-11 01:10:28 | SUCCESS |
ExtractSHash
Extracted s_hash from ID Token
|
||||
|
||||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateSHash
s_hash validated successfully
|
||||||
|
||||||||
| 2025-03-11 01:10:28 | SUCCESS |
ExtractCHash
Extracted c_hash from ID Token
|
||||
|
||||||
| 2025-03-11 01:10:28 | SUCCESS |
ValidateCHash
c_hash validated successfully
|
||||||
|
||||||||
| Checking the created consent - Expecting AUTHORISED status |
| 2025-03-11 01:10:28 |
|
AddJWTAcceptHeader
Adding jwt to accept header
|
|
|
||
| 2025-03-11 01:10:28 |
|
ExpectJWTResponse
Expecting jwt from endpoint response
|
|
|
||
| 2025-03-11 01:10:28 |
|
PrepareToFetchConsentRequest
Fetching consent from consent API
|
||||
|
||||||
| 2025-03-11 01:10:28 |
|
Load client_credential access token
|
||||
|
||||||
| 2025-03-11 01:10:28 |
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:29 |
RESPONSE
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:29 |
SUCCESS
|
FAPIBrazilCallPaymentConsentEndpointWithBearerTokenAnyMethod
Payment consent endpoint response
|
||||||||
|
||||||||||
| Validate Consent Self link |
| 2025-03-11 01:10:29 |
SUCCESS
|
ValidateSelfLinkRegex
Self Link matches the regex
|
||
|
||||
| 2025-03-11 01:10:29 |
|
SaveOldValues
Saving old environment values
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:10:29 |
|
SetProtectedResourceUrlToConsentSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/recurring-consents/urn:semear:8e024e5b-a09d-4035-b8d7-4fe965f7b305
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:10:29 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:10:29 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:29 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:29 |
|
Load client_credential access token
|
||||
|
||||||
| 2025-03-11 01:10:29 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:29 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:29 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:10:29 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:10:29 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:10:29 |
|
LoadOldValues
Loading old environment values
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
EnsurePaymentConsentStatusWasAuthorised
Consent was in the expected state after redirect
|
||||
|
||||||
| Validate GET Consent Response |
| 2025-03-11 01:10:29 |
SUCCESS
|
ExtractSignedJwtFromResourceResponse
Found and parsed the JWT from payment consent endpoint
|
||||||
|
||||||||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up data on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The data element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up data on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The data element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConsentId on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConsentId element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConsentId on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConsentId element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up loggedUser on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The loggedUser element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up loggedUser on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The loggedUser element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up businessEntity on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The businessEntity element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up businessEntity on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The businessEntity element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up document on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The document element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up identification on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The identification element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up rel on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The rel element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up creditors on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creditors element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up personType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The personType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:29 |
|
GetRecurringConsentOASValidatorV2
Looking up personType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The personType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up cpfCnpj on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The cpfCnpj element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up cpfCnpj on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The cpfCnpj element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up name on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The name element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up name on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The name element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up creationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up creationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The creationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up expirationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The expirationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up expirationDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The expirationDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up debtorAccount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The debtorAccount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up debtorAccount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The debtorAccount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up ispb on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ispb element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up ispb on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ispb element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up issuer on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The issuer element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up issuer on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The issuer element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up number on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The number element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up number on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The number element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up ibgeTownCode on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ibgeTownCode element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up ibgeTownCode on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The ibgeTownCode element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
INFO
|
GetRecurringConsentOASValidatorV2
Unable to find element automatic on the GetRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up sweeping on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The sweeping element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up sweeping on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The sweeping element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up totalAllowedAmount on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The totalAllowedAmount element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up periodicLimits on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The periodicLimits element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up periodicLimits on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The periodicLimits element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up day on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The day element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up day on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The day element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up week on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The week element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up week on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The week element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up month on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The month element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up month on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The month element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up year on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The year element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up year on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The year element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up quantityLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The quantityLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up transactionLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The transactionLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up useOverdraftLimit on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The useOverdraftLimit element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up startDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The startDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up startDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The startDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up recurringConfiguration on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The recurringConfiguration element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
INFO
|
GetRecurringConsentOASValidatorV2
Unable to find element vrp on the GetRecurringConsentOASValidatorV2 API response
|
||
|
||||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up authorisedAtDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The authorisedAtDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up authorisedAtDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The authorisedAtDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up links on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The links element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up links on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The links element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up self on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The self element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up self on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The self element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up meta on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The meta element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up meta on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The meta element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up requestDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The requestDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up requestDateTime on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The requestDateTime element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up accountType on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The accountType element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
|
GetRecurringConsentOASValidatorV2
Looking up status on the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
GetRecurringConsentOASValidatorV2
The status element is present in the GetRecurringConsentOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:30 |
SUCCESS
|
ValidateVersionHeader2d0d0
Successfully validated the "x-v" header
|
|
|
||
| Call token endpoint |
| 2025-03-11 01:10:30 |
SUCCESS
|
CreateTokenEndpointRequestForAuthorizationCodeGrant
Created token endpoint request
|
||||||
|
||||||||
| 2025-03-11 01:10:30 |
SUCCESS
|
CreateClientAuthenticationAssertionClaims
Created client assertion claims
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:10:30 |
SUCCESS
|
SignClientAuthenticationAssertion
Signed the client assertion
|
||
|
||||
| 2025-03-11 01:10:30 |
|
AddClientAssertionToTokenEndpointRequest
Added client assertion
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:30 |
|
AddCodeVerifierToTokenEndpointRequest
|
||||||||||||
|
||||||||||||||
| 2025-03-11 01:10:30 |
|
CallTokenEndpoint
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:31 |
RESPONSE
|
CallTokenEndpoint
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:31 |
SUCCESS
|
CallTokenEndpoint
Parsed token endpoint response
|
||||||||||||
|
||||||||||||||
| Verify token endpoint response |
| 2025-03-11 01:10:31 |
SUCCESS
|
CheckIfTokenEndpointResponseError
No error from token endpoint
|
|
|
||
| 2025-03-11 01:10:31 | SUCCESS |
CheckForAccessTokenValue
Found an access token
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
ExtractAccessTokenFromTokenResponse
Extracted the access token
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
ExtractExpiresInFromTokenEndpointResponse
Extracted 'expires_in'
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateExpiresIn
expires_in passed all validation checks
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
FAPIBrazilValidateExpiresIn
expires_in no greater than 900 seconds and no less than 300 seconds
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
CheckForRefreshTokenValue
Found a refresh token
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
EnsureMinimumRefreshTokenLength
Refresh token is of sufficient length
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
EnsureMinimumRefreshTokenEntropy
Calculated shannon entropy seems sufficient
|
||||||
|
||||||||
| 2025-03-11 01:10:31 | SUCCESS |
EnsureMinimumAccessTokenLength
Access token is of sufficient length
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
EnsureMinimumAccessTokenEntropy
Calculated shannon entropy seems sufficient
|
||||||
|
||||||||
| 2025-03-11 01:10:31 | SUCCESS |
ExtractIdTokenFromTokenResponse
Found and parsed the id_token from token_endpoint_response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateIdToken
ID token iss, aud, exp, iat, auth_time, acr & nbf claims passed validation checks
|
|
|
||
| 2025-03-11 01:10:31 |
|
ValidateIdTokenStandardClaims
sub is a string with content
|
|
|
||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateIdTokenStandardClaims
id_token claims are valid
|
|
|
||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateIdTokenNonce
Nonce values match
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateIdTokenACRClaimAgainstRequest
Nothing to check; the conformance suite did not request an acr claim in request object
|
|
|
||
| 2025-03-11 01:10:31 |
SUCCESS
|
ValidateIdTokenSignature
id_token signature validated
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
CheckForSubjectInIdToken
Found 'sub' in id_token
|
||
|
||||
| 2025-03-11 01:10:31 |
|
EnsureIdTokenUpdatedAtValid
id_token response does not contain 'updated_at'
|
|
|
||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateEncryptedIdTokenHasKid
kid was found in the encrypted ID token header
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
EnsureIdTokenContainsKid
kid was found in the ID token header
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
FAPIBrazilValidateIdTokenSigningAlg
id_token was signed with a permitted algorithm
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
FAPIValidateIdTokenEncryptionAlg
id_token was encrypted with a permitted algorithm
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
ExtractCHash
Extracted c_hash from ID Token
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
ExtractSHash
Extracted s_hash from ID Token
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
ExtractAtHash
Extracted at_hash from ID Token
|
||||
|
||||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateCHash
c_hash validated successfully
|
||||||
|
||||||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateSHash
s_hash validated successfully
|
||||||
|
||||||||
| 2025-03-11 01:10:31 | SUCCESS |
ValidateAtHash
at_hash validated successfully
|
||||||
|
||||||||
| Verify at_hash in the authorization endpoint id_token |
| 2025-03-11 01:10:31 | INFO |
ExtractAtHash
Couldn't find at_hash in ID token
|
|
|
||
| 2025-03-11 01:10:31 | INFO |
ValidateAtHash
Skipped evaluation due to missing required object: at_hash
|
||||
|
||||||
| 2025-03-11 01:10:31 |
SUCCESS
|
AddRiskSignalsManualObjectToPixPaymentBody
The risk signals object has been added to the payment request body.
|
||
|
||||
| Call pix/payments endpoint |
| 2025-03-11 01:10:31 |
SUCCESS
|
EditRecurringPaymentsBodyToSetDateToTodayUtcMinus3
The date field has been set in the recurring payments request body
|
||
|
||||
| 2025-03-11 01:10:31 |
|
CreateEmptyResourceEndpointRequestHeaders
Created empty headers
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
AddFAPIAuthDateToResourceEndpointRequest
Added x-fapi-auth-date to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:31 |
|
AddIpV4FapiCustomerIpAddressToResourceEndpointRequest
Added x-fapi-customer-ip-address containing IPv4 address to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:31 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
CreateIdempotencyKey
Created idempotency key
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
AddIdempotencyKeyHeader
Added x-idempotency-key to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
SetApplicationJwtContentTypeHeaderForResourceEndpointRequest
Set Content-Type header
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
SetApplicationJwtAcceptHeaderForResourceEndpointRequest
Set Accept header
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
SetResourceMethodToPost
Set protected resource access method to POST
|
|
|
||
| 2025-03-11 01:10:31 |
SUCCESS
|
CreatePaymentRequestEntityClaims
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
SetProtectedResourceUrlToRecurringPaymentsEndpoint
Endpoint added
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
AddAudAsPaymentInitiationUriToRequestObject
Added aud to request object claims
|
||
|
||||
| 2025-03-11 01:10:31 |
|
AddIssAsCertificateOuToRequestObject
Added iss value based on TLS certificate organizational unit to request object claims
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
AddJtiAsUuidToRequestObject
Added jti to request object claims
|
||
|
||||
| 2025-03-11 01:10:31 | SUCCESS |
AddIatToRequestObject
Added iat to request object claims
|
||
|
||||
| 2025-03-11 01:10:31 |
SUCCESS
|
FAPIBrazilSignPaymentInitiationRequest
Signed the request
|
||||||||
|
||||||||||
| 2025-03-11 01:10:31 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:33 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:33 | SUCCESS |
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| Validate Self link |
| 2025-03-11 01:10:33 |
SUCCESS
|
ValidateSelfLinkRegex
Self Link matches the regex
|
||
|
||||
| 2025-03-11 01:10:33 |
|
SaveOldValues
Saving old environment values
|
|
|
||
| 2025-03-11 01:10:33 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:10:33 |
|
SetProtectedResourceUrlToSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/pix/recurring-payments/PY20250310221003344F24BCC105E4
|
|
|
||
| 2025-03-11 01:10:33 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:10:33 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:10:33 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:10:33 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:33 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:33 |
|
Load client_credential access token
|
||||
|
||||||
| 2025-03-11 01:10:33 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:34 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:34 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:10:34 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:10:34 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:10:34 |
|
LoadOldValues
Loading old environment values
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
EnsureResourceResponseCodeWas201
Correct status obtained
|
||
|
||||
| 2025-03-11 01:10:34 | SUCCESS |
CheckForDateHeaderInResourceResponse
Date header present and validated
|
||||
|
||||||
| 2025-03-11 01:10:34 | SUCCESS |
CheckForFAPIInteractionIdInResourceResponse
Found x-fapi-interaction-id
|
||
|
||||
| 2025-03-11 01:10:34 |
SUCCESS
|
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:10:34 |
|
EnsureContentTypeApplicationJwt
|
||||||||
|
||||||||||
| 2025-03-11 01:10:34 |
SUCCESS
|
EnsureContentTypeApplicationJwt
endpoint_response Content-Type: header is application/jwt
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
ExtractSignedJwtFromResourceResponse
Found and parsed the JWT from payment consent endpoint
|
||||||
|
||||||||
| 2025-03-11 01:10:34 |
SUCCESS
|
FAPIBrazilValidateResourceResponseSigningAlg
Response was signed with PS256
|
||
|
||||
| 2025-03-11 01:10:34 |
SUCCESS
|
FAPIBrazilValidateResourceResponseTyp
'typ' is the header of the JWT returned in the API response is 'JWT'
|
||
|
||||
| 2025-03-11 01:10:34 |
|
FetchServerKeys
Fetching server key
|
||
|
||||
| 2025-03-11 01:10:34 |
|
FetchServerKeys
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:34 |
RESPONSE
|
FetchServerKeys
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:34 |
|
FetchServerKeys
Found JWK set string
|
||
|
||||
| 2025-03-11 01:10:34 |
SUCCESS
|
FetchServerKeys
Found server JWK set
|
||
|
||||
| 2025-03-11 01:10:34 | SUCCESS |
ValidateResourceResponseSignature
endpoint_response_jwt signature validated
|
||
|
||||
| 2025-03-11 01:10:34 | SUCCESS |
ValidateResourceResponseJwtClaims
Resource endpoint response JWS iss, aud, exp, iat, auth_time, acr & nbf claims passed validation checks
|
|
|
||
| Validate response |
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up data on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The data element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up data on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The data element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up recurringPaymentId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The recurringPaymentId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up recurringPaymentId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The recurringPaymentId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up recurringConsentId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The recurringConsentId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up recurringConsentId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The recurringConsentId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up endToEndId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The endToEndId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up endToEndId on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The endToEndId element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up date on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The date element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up date on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The date element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up creationDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The creationDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up creationDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The creationDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up statusUpdateDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The statusUpdateDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up statusUpdateDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The statusUpdateDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up status on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The status element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up status on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The status element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up cnpjInitiator on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The cnpjInitiator element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up cnpjInitiator on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The cnpjInitiator element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up payment on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The payment element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up payment on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The payment element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up amount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The amount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up amount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The amount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up currency on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The currency element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up currency on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The currency element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up remittanceInformation on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The remittanceInformation element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up remittanceInformation on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The remittanceInformation element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up creditorAccount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The creditorAccount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up creditorAccount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The creditorAccount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up ispb on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The ispb element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up ispb on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The ispb element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up issuer on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The issuer element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up issuer on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The issuer element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up number on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The number element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up number on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The number element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up accountType on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The accountType element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up accountType on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The accountType element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up debtorAccount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The debtorAccount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up debtorAccount on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The debtorAccount element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up ispb on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The ispb element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up ispb on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The ispb element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up issuer on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The issuer element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up issuer on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The issuer element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up number on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The number element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up number on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The number element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up accountType on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The accountType element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up accountType on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The accountType element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up document on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The document element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up document on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The document element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up identification on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The identification element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up identification on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The identification element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up rel on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The rel element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up rel on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The rel element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up links on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The links element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up links on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The links element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up self on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The self element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up self on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The self element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up meta on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The meta element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up meta on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The meta element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up requestDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The requestDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up requestDateTime on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The requestDateTime element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up status on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The status element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up status on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The status element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:34 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
PostRecurringPaymentPixOASValidatorV2
Looking up accountType on the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
PostRecurringPaymentPixOASValidatorV2
The accountType element is present in the PostRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
ValidateVersionHeader2d0d0
Successfully validated the "x-v" header
|
|
|
||
| Polling sequence [1] |
| 2025-03-11 01:10:35 |
|
SaveOldValues
Not saving old values
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:10:35 |
|
SetProtectedResourceUrlToSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/pix/recurring-payments/PY20250310221003344F24BCC105E4
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:10:35 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:10:35 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:35 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:10:35 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:10:35 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:10:35 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:10:35 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:10:35 |
SUCCESS
|
CheckPaymentPollStatusRcvdOrAccpOrAcpdV2
Status still in the expected state
|
||||
|
||||||
| 2025-03-11 01:10:35 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:10:35 |
|
LoadOldValues
Not loading old values
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up data on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The data element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up data on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The data element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up recurringPaymentId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The recurringPaymentId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up recurringPaymentId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The recurringPaymentId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up recurringConsentId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The recurringConsentId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up recurringConsentId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The recurringConsentId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up endToEndId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The endToEndId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up endToEndId on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The endToEndId element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up date on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The date element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up date on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The date element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up creationDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The creationDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up creationDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The creationDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up statusUpdateDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The statusUpdateDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up status on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The status element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up status on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The status element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up cnpjInitiator on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The cnpjInitiator element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up cnpjInitiator on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The cnpjInitiator element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:35 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up payment on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The payment element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up payment on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The payment element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up amount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The amount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up amount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The amount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up currency on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The currency element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up currency on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The currency element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up remittanceInformation on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The remittanceInformation element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up remittanceInformation on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The remittanceInformation element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up creditorAccount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The creditorAccount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up creditorAccount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The creditorAccount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up ispb on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The ispb element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up ispb on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The ispb element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up issuer on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The issuer element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up issuer on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The issuer element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up number on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The number element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up number on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The number element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up accountType on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The accountType element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up accountType on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The accountType element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up debtorAccount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The debtorAccount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up debtorAccount on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The debtorAccount element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up ispb on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The ispb element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up ispb on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The ispb element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up issuer on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The issuer element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up issuer on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The issuer element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up number on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The number element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up number on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The number element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up accountType on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The accountType element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up accountType on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The accountType element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up document on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The document element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up document on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The document element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up identification on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The identification element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up identification on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The identification element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up rel on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The rel element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up rel on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The rel element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up links on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The links element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up links on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The links element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up self on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The self element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up self on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The self element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up meta on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The meta element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up meta on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The meta element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up requestDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The requestDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up requestDateTime on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The requestDateTime element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up status on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The status element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up status on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The status element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up localInstrument on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The localInstrument element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
|
GetRecurringPaymentPixOASValidatorV2
Looking up accountType on the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
GetRecurringPaymentPixOASValidatorV2
The accountType element is present in the GetRecurringPaymentPixOASValidatorV2 API response
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
ValidateVersionHeader2d0d0
Successfully validated the "x-v" header
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
WaitForConfiguredSeconds
Loop sequence configured to pause for 30 seconds
|
|
|
||
| 2025-03-11 01:10:36 |
SUCCESS
|
WaitForConfiguredSeconds
Pausing for 30 seconds
|
|
|
||
| 2025-03-11 01:11:06 |
SUCCESS
|
WaitForConfiguredSeconds
Woke up after 30 seconds sleep
|
|
|
||
| Polling sequence [2] |
| 2025-03-11 01:11:06 |
|
SaveOldValues
Not saving old values
|
|
|
||
| 2025-03-11 01:11:06 |
SUCCESS
|
ClearRequestObjectFromEnvironment
Cleared out request entity for future calls
|
|
|
||
| 2025-03-11 01:11:06 |
|
SetProtectedResourceUrlToSelfEndpoint
Hitting the endpoint: https://mtls.semear.hml.linaob.com.br/open-banking/automatic-payments/v2/pix/recurring-payments/PY20250310221003344F24BCC105E4
|
|
|
||
| 2025-03-11 01:11:06 |
SUCCESS
|
SetResourceMethodToGet
Set protected resource access method to GET
|
|
|
||
| 2025-03-11 01:11:06 |
SUCCESS
|
ClearContentTypeHeaderForResourceEndpointRequest
Cleared custom Accept header
|
|
|
||
| 2025-03-11 01:11:06 |
|
CreateRandomFAPIInteractionId
Created interaction ID
|
||
|
||||
| 2025-03-11 01:11:06 | SUCCESS |
AddFAPIInteractionIdToResourceEndpointRequest
Added x-fapi-interaction-id to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:11:06 |
SUCCESS
|
AddJWTAcceptHeaderRequest
Added accept jwt to resource endpoint request headers
|
||
|
||||
| 2025-03-11 01:11:06 |
|
CallProtectedResource
HTTP request
|
||||||||||
|
||||||||||||
| 2025-03-11 01:11:07 |
RESPONSE
|
CallProtectedResource
HTTP response
|
||||||||
|
||||||||||
| 2025-03-11 01:11:07 |
SUCCESS
|
CallProtectedResource
Got a response from the resource endpoint
|
||||||||
|
||||||||||
| 2025-03-11 01:11:07 |
SUCCESS
|
EnsureResourceResponseCodeWas200
Correct status obtained
|
||
|
||||
| 2025-03-11 01:11:07 |
SUCCESS
|
CheckPaymentPollStatusRcvdOrAccpOrAcpdV2
Status no longer in the expected state
|
||||
|
||||||
| 2025-03-11 01:11:07 | SUCCESS |
EnsureMatchingFAPIInteractionId
Interaction ID matches, ignoring case
|
||
|
||||
| 2025-03-11 01:11:07 |
|
LoadOldValues
Not loading old values
|
|
|
||
| 2025-03-11 01:11:07 |
SUCCESS
|
WaitForConfiguredSeconds
Loop sequence configured to pause for 30 seconds
|
|
|
||
| 2025-03-11 01:11:07 |
SUCCESS
|
WaitForConfiguredSeconds
Pausing for 30 seconds
|
|
|
||
| 2025-03-11 01:11:37 |
SUCCESS
|
WaitForConfiguredSeconds
Woke up after 30 seconds sleep
|
|
|
||
| 2025-03-11 01:11:37 |
SUCCESS
|
EnsurePaymentStatusWasAcsc
Payment status is what was expected
|
||||
|
||||||
| 2025-03-11 01:11:37 |
|
CheckCurrentTime
Validating current time is between 9 PM and 11:59 PM in UTC-3
|
|
|
||
| 2025-03-11 01:11:37 |
SUCCESS
|
CheckCurrentTime
Current time is between 9 PM and 11:59 PM in UTC-3
|
||
|
||||
| 2025-03-11 01:11:37 |
FINISHED
|
automatic-payments_api_timezone_test-module_v2
Test has run to completion
|
||
|
||||