Recommended path
Connect to the DeveloperApi gRPC service from a partner backend once transport is activated. The reviewed contract exposes rpc CreatePayment as paired and rpc CreateRefund as registered but not production-activated.
Developer preview API v1
Sandbox only. No real funds moved. No production access is granted here. Access requirements
gRPC backend
Plan against the DeveloperApi gRPC contract
A partner backend can plan against the published DeveloperApi service, including CreatePayment and CreateRefund, before transport is activated.
Fully-qualified routes
Use /pap.developer.v1.DeveloperApi/CreatePayment and /pap.developer.v1.DeveloperApi/CreateRefund over the gRPC service. Messages are compiled into prost types from the versioned protobuf artifact.
Not production-activated
The DeveloperApi service contract is published, but a public gRPC transport is not production-activated until a later activation decision. Plan against the contract and keep REST parity checks in your pipeline.