The ID of the account to create a scheduled transfer for.
SEPA transfers (1.0)
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/sepa-transfers/
Request
Creates a scheduled transfer for the account specified in the request URL. Note: This call triggers the change request process.
The content of the request.
The type of transfer to be scheduled.
The ID of the person who should authorize the scheduled transfer.
A reference provided by the transaction initiator. It needs to be unique for the initiator.
The amount of the scheduled transfer transaction (in Euro cents).
The date on which the scheduled transfer will become active. The first transfer will be executed on this date.
The frequency at which to execute the scheduled transfer.
End-to-end ID to use in the scheduled transfer transactions.
The date by which the scheduled transfer will be concluded. The last transfer will be executed before or on this date. For one-time transfers, this field is not required and will default to the active_from date.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/sepa-transfers/v1/accounts/{account_id}/scheduled_transfers
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "transfer_type": "SCT", "initiator_reference": "12f7ec0b-6762-4578-b49f-c0b1647d0e2d", "creditor_name": "Hans Mustermann", "creditor_iban": "DE32110101001000000029", "creditor_bic": "COBADEFFXXX", "amount": { "value": 1000, "currency": "EUR" }, "description": "Example scheduled transfer", "end_to_end_id": "unique-end-to-end-id", "execution_schedule": "MONTHLY", "active_from": "2018-03-01", "active_to": "2018-04-01", "authorizer_id": "cf67beb032b2abbfc444f1641fa669bccper", "verification_of_payee_id": "f874b3102718a4d757a6b6e4d5996078veop" }
The change request was successfully confirmed, and the scheduled transfer successful.
The account ID of the account that the scheduled transfer is associated with.
The status of the scheduled transfer.
Reference provided by the transaction initiator. It needs to be unique for the initiator.
Optional description for the transaction, which will be visible to the recipient. Limited to 140 characters.
The date on which the scheduled transfer will become active. The first transfer will be executed on this date.
The date by which the scheduled transfer will become concluded. The last transfer will be executed before or on this date. For one-time transfers this field will default to the active_from date.
The frequency at which to execute the scheduled transfer.
SEPA identifier provided by the transaction initiator, which will be routed throughout the whole payment process.
Next execution_schedule for this scheduled transfer
The ID of the person who authorized the scheduled transfer.
The ID of the verification of payee process that was used to verify the recipient's name and IBAN.
UTC timestamp from the time the scheduled transfer was created.
{ "id": "f874b3102718a4d757a6b6e4d599607csctr", "account_id": "236f9042a19b65c0867e10c922b93502cacc", "status": "ACTIVE", "transfer_type": "SCT", "creditor_iban": "DE87110101001000057123", "creditor_name": "Hans Mustermann", "creditor_bic": "COBADEFFXXX", "initiator_reference": "dsf2r3raedfs3fsf342fctrx", "amount": { "value": 1000, "currency": "EUR" }, "description": "string", "active_from": "2025-09-01", "active_to": "2026-09-01", "execution_schedule": "MONTHLY", "end_to_end_id": "END2ENDREJ", "next_execution_date": "2025-10-01", "authorizer_id": "cf67beb032b2abbfc444f1641fa669bccper", "verification_of_payee_id": "f874b3102718a4d757a6b6e4d599607cvope", "created_at": "2022-04-21T13:59:52+00:00", "updated_at": "2022-04-21T13:59:52+00:00" }
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/sepa-transfers/v1/accounts/{account_id}/scheduled_transfers
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Successful result of the operation
The account ID of the account that the scheduled transfer is associated with.
The status of the scheduled transfer.
Reference provided by the transaction initiator. It needs to be unique for the initiator.
Optional description for the transaction, which will be visible to the recipient. Limited to 140 characters.
The date on which the scheduled transfer will become active. The first transfer will be executed on this date.
The date by which the scheduled transfer will become concluded. The last transfer will be executed before or on this date. For one-time transfers this field will default to the active_from date.
The frequency at which to execute the scheduled transfer.
SEPA identifier provided by the transaction initiator, which will be routed throughout the whole payment process.
Next execution_schedule for this scheduled transfer
The ID of the person who authorized the scheduled transfer.
The ID of the verification of payee process that was used to verify the recipient's name and IBAN.
UTC timestamp from the time the scheduled transfer was created.
UTC timestamp from the last time the scheduled transfer was updated.
[ { "id": "f874b3102718a4d757a6b6e4d599607csctr", "account_id": "236f9042a19b65c0867e10c922b93502cacc", "status": "ACTIVE", "transfer_type": "SCT", "creditor_iban": "DE87110101001000057123", "creditor_name": "Hans Mustermann", "creditor_bic": "COBADEFFXXX", "initiator_reference": "dsf2r3raedfs3fsf342fctrx", "amount": { … }, "description": "string", "active_from": "2025-09-01", "active_to": "2026-09-01", "execution_schedule": "MONTHLY", "end_to_end_id": "END2ENDREJ", "next_execution_date": "2025-10-01", "authorizer_id": "cf67beb032b2abbfc444f1641fa669bccper", "verification_of_payee_id": "f874b3102718a4d757a6b6e4d599607cvope", "created_at": "2022-04-21T13:59:52+00:00", "updated_at": "2022-04-21T13:59:52+00:00" } ]
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/sepa-transfers/v1/accounts/{account_id}/scheduled_transfers/{id}
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
No request payload
Scheduled transfer successfully retrieved.
The account ID of the account that the scheduled transfer is associated with.
The status of the scheduled transfer.
Reference provided by the transaction initiator. It needs to be unique for the initiator.
Optional description for the transaction, which will be visible to the recipient. Limited to 140 characters.
The date on which the scheduled transfer will become active. The first transfer will be executed on this date.
The date by which the scheduled transfer will become concluded. The last transfer will be executed before or on this date. For one-time transfers this field will default to the active_from date.
The frequency at which to execute the scheduled transfer.
SEPA identifier provided by the transaction initiator, which will be routed throughout the whole payment process.
Next execution_schedule for this scheduled transfer
The ID of the person who authorized the scheduled transfer.
The ID of the verification of payee process that was used to verify the recipient's name and IBAN.
UTC timestamp from the time the scheduled transfer was created.
{ "id": "f874b3102718a4d757a6b6e4d599607csctr", "account_id": "236f9042a19b65c0867e10c922b93502cacc", "status": "ACTIVE", "transfer_type": "SCT", "creditor_iban": "DE87110101001000057123", "creditor_name": "Hans Mustermann", "creditor_bic": "COBADEFFXXX", "initiator_reference": "dsf2r3raedfs3fsf342fctrx", "amount": { "value": 1000, "currency": "EUR" }, "description": "string", "active_from": "2025-09-01", "active_to": "2026-09-01", "execution_schedule": "MONTHLY", "end_to_end_id": "END2ENDREJ", "next_execution_date": "2025-10-01", "authorizer_id": "cf67beb032b2abbfc444f1641fa669bccper", "verification_of_payee_id": "f874b3102718a4d757a6b6e4d599607cvope", "created_at": "2022-04-21T13:59:52+00:00", "updated_at": "2022-04-21T13:59:52+00:00" }
Request
Cancels the scheduled transfer specified in the request URL. Note that the customer must already have authorized and confirmed scheduled transfer. Note: This call triggers the change request process.
The content of the request.
- Mock Server
https://docs.solarisgroup.com/_mock/api-reference/digital-banking/sepa-transfers/v1/accounts/{account_id}/scheduled_transfers/{id}/cancel
- Payload
- cURL
- Java
- Python
- Node.js
- Go
- Ruby
- PHP
{ "authorizer_id": "cf67beb032b2abbfc444f1641fa679bccper" }
The request is accepted, and the customer must confirm the change request.
The current status of the change request.
UTC timestamp from the last time the change request was updated.
{ "id": "d6c778822b2d7bd3b778935bcfd0d1d3csc", "status": "CONFIRMATION_REQUIRED", "updated_at": "2022-04-21T13:59:52+00:00", "url": "https://example.com/authorize" }