IBAN Status Webhook

Dispatched when the verification lifecycle of a user's dedicated IBAN is updated. This is a critical part of the First-Party Payment verification flow: after a user makes an initial verification deposit, the system automatically validates if the sender's name matches the P100 account holder. This webhook notifies you of the outcome, marking the IBAN status as approved (successful match) or rejected (mismatch).

Verification Logic

When a SEPA deposit is initiated, the system follows this automated workflow:

Detection (PENDING): A deposit is detected from a specific IBAN. The transaction enters a pending state while the system performs a name-matching check (comparing the sender's bank data with the registered user's KYC data).

Approval (APPROVED): If the names match, the deposit is accepted.

Funds are automatically credited to the user's fiat balance.

The IBAN is automatically added to the user's whitelisted contact list, allowing for future withdrawals to this account.

Rejection (REJECTED): If a significant name mismatch or compliance issue is detected:

The deposit is declined.

The system automatically initiates a refund to the original sender's IBAN.

Implementation Notes

Whitelisting: Once a webhook with APPROVED status is received for a specific IBAN, you can consider that IBAN "verified" for that user.

Refunds: Note that REJECTED status means the funds are gone from our system and are back in transit to the user's bank.

curl --location --request POST 'https://your-api-server.com' \ --header 'Content-Type: application/json' \ --data-raw '{ "externalUserId": "exampleuserid123", "status": "APPROVED", "iban": "DK1084758300566382" }'

Verification Logic

Implementation Notes

Request

Responses

IBAN Status Webhook

Verification Logic#

Implementation Notes#

Request

Responses

Verification Logic

Implementation Notes